Network connections does not show "network device" though device manager shows it

Discussion in 'Windows Vista Drivers' started by Praveen Kumar Amritaluru, Dec 5, 2006.

  1. Hi,

    When I install the driver, the installation goes through fine.
    The device manager shows the network card and "properties" display device
    to be working fine.
    But when I open "network connections" it does not display my ethernet
    device. Infact "network connections" window hangs.
    ipconfig also hangs.
    "netsh int ip show address" works. But even that does not show any IP
    So when I configure static IP it accepts it and "netsh int ip show address"
    displays it. But ipconfig still hangs.

    Moreover setupapi.log file does not show the information about "tcp/ip"
    bindings that follow after a network driver installation?
    setupapi.log does not display any error about device installation.
    It does not show even after editing "

    HKLM\Software \Microsoft\ Windows\ CurrentVersion\ Setup

    to 0000FFFF.

    Any idea what could the problem/reasons for such a behaviour?

    Praveen Kumar Amritaluru, Dec 5, 2006
    1. Advertisements

  2. Praveen Kumar Amritaluru

    soviet_bloke Guest

    It looks like there is some problem in binding between your adapter
    and TCPIP.SYS.....

    Are you sure your driver is properly written???

    Anton Bassov
    soviet_bloke, Dec 5, 2006
    1. Advertisements

  3. Have you used a debugger to see whether your driver is actually laoded? Does
    DriverEntry get called?

    If yes, then have you used debugger to what is going on in your
    MiniportQueryInformation handler? Is it being called?

    Thomas F. Divine
    Thomas F. Divine, Dec 5, 2006
  4. This is what i wanted to check. The h/w is present in remote site and yet to
    get debugger to check this out.
    So how does miniportqueryinformationhandler return value affect tcp/ip
    Its my understanding that there will be many OIDs sent to be processed by

    Do you have any particular OID in mind?
    Praveen Kumar Amritaluru, Dec 5, 2006
  5. No specific OID in mind.

    If DriverEntry and MiniportQueryInformation are never called, then it is a
    setup problem. Otherwise, it is a problem in the driver.

    Thomas F. Divine
    Thomas F. Divine, Dec 5, 2006
  6. Praveen Kumar Amritaluru

    soviet_bloke Guest


    Probably, it also makes sense to check what is going on under
    particularly under 'Linkage' subkey for his miniport

    Although the OP says the driver got installed properly, I am still not
    fully convinced - probably, there is some mistake in .INF file that he
    used for installation....

    Anton Bassov
    soviet_bloke, Dec 5, 2006
  7. Stephan Wolf [MVP], Dec 7, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.