Network connection problem

Hi Experts, my server as a DC run with Windows 2000 SP2 on IBM netfinity 5100 series, serve as DNS, DHCP. occasionally it loss network connection. I cant reach any host within same segment, by ping them. Get respond by ping its loopback and IP address. If I disable & enable the network connection then no problem to ping any host. Any idea what can be the cause of this problem, which TCPIP layer and ways to trouble-shoot and solve this problem. many thanks.
Who is Participating?
Steve McCarthy, MCSE, MCSA, MCP x8, Network+, i-Net+, A+, CIWA, CCNA, FDLE FCIC, HIPAA Security OfficerConnect With a Mentor IT Consultant, Network Engineer, Windows Network Administrator, VMware AdministratorCommented:
Sounds like it could be a flakey NIC.  First I would change my switch port to rule that out.  If you are getting responses from the loopback address and IP, that says TCP/IP is working properly.    I would put in another NIC, Disable the first and see how that one works.  It seems to me to be a physical layer issue.
I would try what sam says above and also what is the setting on the NIC, full duplex, auto, etc.?  Have you tried forcing it to 100 full on both the server and switch?
Also, try swapping the cable, that is an easy thing to try.
anything in the event logs?
cleungsgAuthor Commented:
Hi samccarthy, what could be the cause of the flakey NIC ?
Never miss a deadline with

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

cleungsgAuthor Commented:
Hi thepunish3r, can you explain more usage of the NIC setting, I need some background understanding before turning them, thanks.
Steve McCarthy, MCSE, MCSA, MCP x8, Network+, i-Net+, A+, CIWA, CCNA, FDLE FCIC, HIPAA Security OfficerIT Consultant, Network Engineer, Windows Network Administrator, VMware AdministratorCommented:
A flakey NIC or Switch port could be caused by heat, cold solder joints, cheap components, power surge or a surge over the Ethernet cabling.  To isolate, you will either have to prove, or disprove what could be the cause.  What Punish is talking about is the actual connection settings of the Nic itself.  Some Switches can be picky about the Auto Setting which is the default on most everything now a days.  Cisco switches seem to be particularly tempermental about this.  If you do this, then you must make the same setting changes on each end.  So if you statically set your NIC to 100 and Full duplex, then you must do the same to the particular port on the switch it is attached to.  It's a good check.  Depending on your switch though, you may not be able to set it there.

I suggest that you try what they have suggested, if in any case, the problem still persists, then try updating your NIC driver. Also, I notice that you're in SP2, it is possible that this is the cause. Some machines in your network might have been affected by a worm/virus that are broadcasting packets and is affecfting your DC. I suggest that you update your DC to SP4 and install the latest critical updates.

Hope this helps

thepunish3rConnect With a Mentor Commented:
It is just that sometimes you will get better performance or if you have issues like you describe that you can force the speed settings for the switches and the server to communicate.

Basically if your NIC is 100mg and the switch is 10/100 and you force the specific Port on the switch that connects to this specific server to both the same speed you can rule out that there is some packet loss between the 2 devices.

Normally auto is OK but I personally have learned from switch techs and this has varied a bit that if you have any trouble just force the server NIC to 100 Full Duplex and the swithc port to the same.
If you don't want to try to force them to this, at least confirm that the switch port and the server NIC is auto detect.

Here is some info.
i have a link from one of the switch manufacturers I am trying to find, will send soon.
Gary GordonConnect With a Mentor Solution IntegratorCommented:
I concur with the above and would switch out the nic.  You could mess with the speed of the card in the advanced properties but if all the nics in your net are running at 100mbps and your servers nic is at 10mbps or spotty in the Auto setting then you really have to scrap that nic and replace.  The nic on the server should be in pristine condition because it's failure potentially affects network performance all over the network.

Do experiment with a different port on the switch because an individual port can burn up and it's gone for good.  What's worse than a flakey port are ports that are intermittently flaky.  It takes some work to find those often.  It's not a bad idea to keep a log of all the good and bad ports on your switches and routers.  
All Courses

From novice to tech pro — start learning today.