Results 1 to 2 of 2
  1. #1
    Star Lounger
    Join Date
    Sep 2001
    Posts
    58
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Networking performance

    One of the PCs on my small network is suddenly having trouble browsing the network, e.g..

    1. when trying to click a shortcut to a folder on a mapped network drive, we will get errors such as this:
    "Error occurred while reconnecting E to //Server//Winword Microsoft Windows Network:Local device name is already in use.
    This connection has not been restored."
    "cannot find folder windows/clients" etc.
    2. accessing programs whose data resides on the server will also occasionally lead to network issues, such as this
    "The installation file TIMESLIPS.CFG needs to be located before continuing. this folder will be on your network.
    It is possible that your network drive is not accessible at this time" (and so on)
    3. we use Realpopup (a hopped-up version of winpopup) as an IM/chat client, messages to and from this PC are at least 3 or 4 times slower to get thru than anyone else on the network.
    4. If you view mapped drives on this PC's My computer, red x's will appear off and on, suggesting the network connections are balky.

    PC is running Win2k pro SP2, server is WinNT 4 SP3, all other PC's on network are either Win2k pro SP2 or XP Pro, the problem PC has trouble/slowness accessing anything on any of the other PC's on the network.

    I tried the most obvious things I could think of, checked that network cable was secure, replaced with a new cat-5 cable, checked the NIC in device manager, etc. Everything checks out and the problem remains.

    What are the next steps in trying to troubleshoot this?

    Many TIA

  2. #2
    3 Star Lounger
    Join Date
    Mar 2001
    Location
    Nixa, Missouri, USA
    Posts
    314
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Networking performance

    I may get jumped all over for this, but hey, it's how I do it.
    First I would try removing all network connection information from your protocol (TCP/IP?) to the Network card. after this is complete reboot and reinstall the NIC (the drivers should still be on the PC). Finally resetup all of the protocol information. This is a little time consuming but has resolved this issue about 75% of the time for me. Of course I mean after I had done what you are suggesting that your have, new cables, tight plugs, newest NIC driver...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •