Discussion Locked

Intermittant Connectivity Loss

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are running Windows 2000 with service pack 1 on our servers. Occasionally, our network will "hiccup" and we lose connectivity for several seconds. All of our mapped drives of course end up with red X's through them which indicates that we have gone offline. We have checked the obvious things: tcp/ip config, hardware connections, cabling, etc. Any suggestions as to some things that I can try to resolve the problem?

5 replies

by ntoz

From what I have gathered, you did a visual inspection of your cables ect. This is a great start. You make no mention of what your hub or switch is, if its a higher end switch though, you should be able to look at error logs on the switch. These days the switchs can either be accesed via console or via a firmware HTTP site. The error logs might be able to help if your having a problem with the switch its self. If your using a hub, they are passive most of the time and this wont help. I dont seemention of the event logs and anything recorded in them so I will say anyway, check your error logs on Windows 2000. If these dont give you any clues as to whats going on, I would switch out the cable from your server to the hub. I would also try pluggin the server into a different port in case the port is bad. Last, if none of these issues resolved your consern, you should put a Sniffer or Protocol Capture program, such as Network Associates Sniffer on your network. Frankly, from what you describe, If your system logs check out on the server, I would put money on it being a problem with cabling, your cable plant, a bad port on the hub/switch or your switch is going bad. Hope I helped, if you would like, I can send you a remote probe to put on your network to capture data and I can then look at it for you after sending me the captures.

Pete

by ntoz

From what I have gathered, you did a visual inspection of your cables ect. This is a great start. You make no mention of what your hub or switch is, if its a higher end switch though, you should be able to look at error logs on the switch. These days the switchs can either be accesed via console or via a firmware HTTP site. The error logs might be able to help if your having a problem with the switch its self. If your using a hub, they are passive most of the time and this wont help. I dont seemention of the event logs and anything recorded in them so I will say anyway, check your error logs on Windows 2000. If these dont give you any clues as to whats going on, I would switch out the cable from your server to the hub. I would also try pluggin the server into a different port in case the port is bad. Last, if none of these issues resolved your consern, you should put a Sniffer or Protocol Capture program, such as Network Associates Sniffer on your network. Frankly, from what you describe, If your system logs check out on the server, I would put money on it being a problem with cabling, your cable plant, a bad port on the hub/switch or your switch is going bad. Hope I helped, if you would like, I can send you a remote probe to put on your network to capture data and I can then look at it for you after sending me the captures.

Pete

This discussion is closed to new replies.