--------------------
>From: "Joupin TAM" <(E-Mail Removed)>
>Subject: << windows 2003 Lost network connection after few days of working >
>Date: Tue, 6 Apr 2004 12:16:18 +0430
>Lines: 25
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>Message-ID: <#(E-Mail Removed)>
>Newsgroups: microsoft.public.windows.server.networking
>NNTP-Posting-Host: 62.145.59.15
>Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP11.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.networking:11275
>X-Tomcat-NG: microsoft.public.windows.server.networking
>
>This happend to me 3 times in two different server .
>
>I installed windows 2003 Enterprise Edition as a file server without any
>problem. servers were working fine but after some days they stop responding
>and lose conection to the network , its not a NIC itself problem or any
>hardware issues and they are workig fine with windows 2000 and xp and there
>is no Virus problem cuz I installed updated version of Mcafee antivirus.
>
>I can ping itself from the commend prompt but none of the other machines in
>the network , and also no one can ping the server
>also there is no Event
>the only sign I have is server`s NIC activilty : that the server is only
>sending the packets and recieved packets remain to 0 .
>
>
>So any help or comment are highly appreciated
>
>Regards
>Joupin
>(E-Mail Removed)
>
>
>
>
>
>
Joupin,
What type of NICs are you using in these systems? I have seen some strange behavior with some GB NICs that do not have the latest drivers. Often forcing both the switch and the NIC to a
common speed and duplex setting has resolved the issue many times. The most important piece of information in a case like this is to collect Network Monitor traces from both sides to see if the
client ICMP Echo Request that leaves the client ever arrives at the server. This will let you know if there is a hardware issue for sure.
Have you tried a different NIC in this system? That would be the next course of action at this point. Swap the current NIC out with a completely different manufacturer and model. Load the latest
drivers and see if the issue persists. If Ping is failing between clients on a LAN, (i.e. not router involved) then the first though is Sub net mask. You stated that this works and then after a few days
begins to fail with no even being logged in the Event Viewer so SNM is probably not this issue. This has the feel of a hardware issue (more specifically a NIC Driver issue) and I am betting that
swapping out the NIC will resolve this issue.
Also, when the NIC appears to not be responding to requests, what do you do to resolve the issue? Do you simply disable and re-enable the NIC or do you reboot the system?
Also if this is a NIC Team, break the team and use only one dedicated NIC for testing.
T.J. Campana [MSFT]
Microsoft EPS Networking
--
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.