1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

WAN MiniPort problem

Discussion in 'Windows XP' started by billibob, 2005/12/29.

  1. 2005/12/29
    billibob

    billibob Inactive Thread Starter

    Joined:
    2005/04/23
    Messages:
    31
    Likes Received:
    0
    I keep getting a yellow exclamation mark next to my WAN MINIPORT(Network Adapter)! Here is the info

    Driver Date: 7/1/2001
    Driver Version: 5.1.2535.0

    And signed and published by Microsoft

    ----------------------------

    I went to update automatically, doesn't work; I went and choose from a list of compatible which comes up the the Wan Miniport driver and it says will work after reboot but it doesn't!!!! Please help with getting it fixed:confused: :confused: :confused:
     
  2. 2005/12/30
    rsinfo

    rsinfo SuperGeek Alumni

    Joined:
    2005/12/25
    Messages:
    4,076
    Likes Received:
    178
    WAN Miniport is normally hidden & is internal device, set & detected by Windows automatically without any input from user.

    A yellow exclaimation marks points to some network component problem and NOT to WAN Miniport itself. Windows is not able to find all networking components (like TCP/IP) and thus is showing the exclaimation mark.
    Check you networking configuration - uninstall and reinstall TCP/IP, Networking for Windows and then see what happens.
     

  3. to hide this advert.

  4. 2005/12/30
    billibob

    billibob Inactive Thread Starter

    Joined:
    2005/04/23
    Messages:
    31
    Likes Received:
    0
    Yep when I try to repair my 1394 connection I get a error message saying

    "Windows could not finish repairing the problem because the following action cannot be completed:
    TCP/IP is not enabled for this connection. Cannot proceed "

    I check properties of 1394 and the Tcp/ip protcol looks fine all set to auto detect.

    How do I fix it.
     
  5. 2005/12/30
    rsinfo

    rsinfo SuperGeek Alumni

    Joined:
    2005/12/25
    Messages:
    4,076
    Likes Received:
    178
    Are you using 1394? try to disable it and see what happens.
     
  6. 2005/12/30
    billibob

    billibob Inactive Thread Starter

    Joined:
    2005/04/23
    Messages:
    31
    Likes Received:
    0
    I believe I'm using my Nvidia nForce motherboard network ethernet adapter, I'll try to disable the 1394 and see what happens

    OK> All it did was put a red X over where the yellow marker was.

    I have the following under my Network Adapters on the device manager

    1394 Network Adapter
    NIVDIA nForce Networking Controller
    WAN Miniport (Network Monitor)
     
    Last edited: 2005/12/30
  7. 2005/12/30
    rsinfo

    rsinfo SuperGeek Alumni

    Joined:
    2005/12/25
    Messages:
    4,076
    Likes Received:
    178
    billibob,

    Can you use you NVidia LAN controller ? If you can, just forget about 1394 if you are not going to use it.
     
  8. 2006/01/03
    billibob

    billibob Inactive Thread Starter

    Joined:
    2005/04/23
    Messages:
    31
    Likes Received:
    0
    I can use it I think, but I'm having trouble connecting to my home network it's timing out or something
     
  9. 2006/01/03
    rsinfo

    rsinfo SuperGeek Alumni

    Joined:
    2005/12/25
    Messages:
    4,076
    Likes Received:
    178
    How are you conected to your network? Are you using switch or cross cable? How is the IP being assigned?
     
  10. 2006/01/03
    billibob

    billibob Inactive Thread Starter

    Joined:
    2005/04/23
    Messages:
    31
    Likes Received:
    0
    My roommate and I are connected through a router (hardwired), we have different ip's. They change so they are dynamic?
     
  11. 2006/01/04
    skeet6961

    skeet6961 Inactive

    Joined:
    2005/09/03
    Messages:
    522
    Likes Received:
    0
    u can probably just delete all the non-functioning devices in devman and reboot. win should redetect them and re-install the drivers.

    another option is PnP bios setup. most machines come setup to 'do' pnp via OS but ... i opt to let the bios configure devices and then the OS must use the resources as they assigned thru the bios.

    most of the time, such problems are solved by changing the bios' PnP setting to whatever it ISN'T on currently ... just change it and reboot. there is often another bios setting that sez akin to 'reset config data' which may help if the bios pnp setting switch doesn't solve outright. that'll force a re-read of the HW resources and reassign io/irq assignments.

    if the problem IS an io/irq issue - meaning that some device is not getting a proper io/irq address - then another option i've used often is to disable stuff u'r not using. most common here is COM ports since there may be 1 or 2 of them and, if they're not used, then u can get the io/irq resources back by diabling them in bios.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.