Intermittent Network Connection problem- ping timeout - TechRepublic
Question
January 11, 2009 at 01:53 PM
jbronk

Intermittent Network Connection problem- ping timeout

by jbronk . Updated 16 years, 1 month ago

I’m having a problem with my Microsoft Server 2003 R2 and was hoping someone could give me some advice on locating the problem.

Our facility has 4 servers, 1 MS Server 2003 R2, 1-MS Exchange Server, 1-AS400 server and 1-Dell server.
I?m having problems keeping connected to the MS Server 2003, I?m having intermittent connection problems. I?ve tried many solutions and here are the symptoms. When I ping the MS Server 2003 from a known good device connected to a good switch. Here are my results.

ping 192.168.9.20 -t
Pinging 192.168.9.20 with 32 bytes of data:
Reply from 192.168.9.20: bytes=32 time<1ms TTL=128 Reply from 192.168.9.20: bytes=32 time<1ms TTL=128 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.9.20: bytes=32 time<1ms TTL=128 Reply from 192.168.9.20: bytes=32 time<1ms TTL=128 Reply from 192.168.9.20: bytes=32 time<1ms TTL=128 Reply from 192.168.9.20: bytes=32 time<1ms TTL=128 Reply from 192.168.9.20: bytes=32 time<1ms TTL=128 Request timed out. Reply from 192.168.9.20: bytes=32 time<1ms TTL=128 Reply from 192.168.9.20: bytes=32 time<1ms TTL=128 Reply from 192.168.9.20: bytes=32 time<1ms TTL=128 Reply from 192.168.9.20: bytes=32 time<1ms TTL=128 Request timed out. When I ping the other servers in my network, the reply is perfect every time. I?m receiving this response from all 49 PC?s within my network. I?m not that good at server configuration but this is what I have done so far: Checked all switches in the network, replaced CAT5 cables leading to my server room, replaced the NIC card in the server and went as far as removing the hard drives in the MS Server 2003 and placed it into another backup server to see if the problem was related to my server?s hardware. I?ve ruled out all hardware in my network and now it looks like there?s something in the Server 2003 configuration that is causing this problem. I must say that I'm not very good at Microsoft Server 2003 software. Any suggestions as to what I can check? It seems simple but it's been beating me up for about 4 day's now

This discussion is locked

All Comments