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.

Intermitent network problem

Discussion in 'Networking (Hardware & Software)' started by Tom Lau-Wiffin, 2004/03/04.

Thread Status:
Not open for further replies.
  1. 2004/03/04
    Tom Lau-Wiffin Contributing Member

    Tom Lau-Wiffin Well-Known Member Thread Starter

    Joined:
    2002/02/05
    Messages:
    16
    Likes Received:
    0
    I have several PC's in a peer-to-peer network, centred on a Linksys router (handling DHCP) and a 3-Com 16 port switch. The OS's in use are Win95, Win98, XP Pro. Several of the computers are left on over night, but I usually turn my own desktop system off.

    Twice in the past 3 days, when I have booted up in the morning, this computer has not been able to see the rest of the network. I have run ipconfig and it reports that the usual configuration is in place. After a re-boot, the rest of the network has become visible, and there have been no other problems throughout the day. Running ipconfig again has shown the same address as before the re-boot. I then tried a full shutdown and re-start, and everything started properly again.

    This machine has 2 network adapters; One on the system board,which the manufacturer (IBM) decided not to use, and the second in an expansion slot. I wondered if the on-board adadpter was perhaps being used by the system instead of the one that is actually connected to the network, but I'm not sure how to check that. Ipconfig shows an address of 0.0.0.0 on sub-net 0.0.0.0 for the on-board adapter.

    Any suggestions for where to look if this happens again?
     
  2. 2004/03/04
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Set the onboard NIC to disabled. I think that will cure the problem for you. If not, enable it again and unbind it from TCP/IP.
     
    Newt,
    #2

  3. to hide this advert.

  4. 2004/03/07
    Tom Lau-Wiffin Contributing Member

    Tom Lau-Wiffin Well-Known Member Thread Starter

    Joined:
    2002/02/05
    Messages:
    16
    Likes Received:
    0
    Getting worse

    Today when I booted up the system I was again without network access. But this time ipconfig reported:

    "IP configuration error. Cannot read IP configuration. "

    This does not look promising. Again, after a re-start, everything seems normal.
    :confused:
     
  5. 2004/03/08
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400
    See Newt's post above:

    1. Open Device Manager
    2. Expand Network Adapters
    3. Open the Properties of the inboard nic.
    4. Disable the onboard nic. (select "Do not use this device, disable ")

    OR

    1. Right click the unwanted adapter in Device Manager and select "Disable ".
     
    Last edited: 2004/03/08
  6. 2004/03/08
    Tom Lau-Wiffin Contributing Member

    Tom Lau-Wiffin Well-Known Member Thread Starter

    Joined:
    2002/02/05
    Messages:
    16
    Likes Received:
    0
    Thank you Newt and Tony T. I went looking for the on-board network adapter in the system devices list and it isn't there. Then I remembered that it is disabled in the BIOS, so I suppose Windows doesn't even know it's present.

    Another thing I noticed this morning was that although I can't see any of the other computers on our network, I can see the 3 network printers, which have permanent IP addresses (not assigned by the router). I also had Internet access (via the router).
     
  7. 2004/03/08
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Ipconfig shows an address of 0.0.0.0 on sub-net 0.0.0.0 for the on-board adapter

    If Ipconfig sees it with address/netmask values (even all zeros), then it is not flagged as disabled.

    Also, the last post where your systems can see the fixed addresses but not the auto-assigned devices sounds like you have some browsing problems. Set one of the 'always on' PCs to do browsing and disable it on all the others.

    Or else set static IP addresses on all devices and put a hosts file on each PC with the information. That's usually by far the best option on a small network. Faster than any sort of browsing/name resolution.
     
    Newt,
    #6
Thread Status:
Not open for further replies.

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.