PDA

View Full Version : Intermittent network functionality

Justin Wilson
I have what can only be described as an 'interesting'
problem. I'm setting up 2 Windows 2000 servers for 2 small
networks. Each server has two NICs.

Two days ago, I connected a 2000 Professional machine to
one of the servers via a crossover cable, and copied some
stuff over (service pack install file, etc.), no problems.

After service packing the machine, and setting up DNS and
Active Directory, I can no longer connect to the server
from 2000 Pro. The network cards are all installed and
working properly on both machines, and if I use a
crossover cable to loopback, I can get both machines to
ping themselves through the other interface. As soon as I
connect the cable to link the machines (and even though
Windows says they are connected), I can't.

The other machine (second server) has been unable to see
the client at all. Is there some ridiculously simple step
I have forgotten somewhere here?


Gary Fose [MSFT]
Hi Justin,

First thing you want to check is to make sure there are NOT two gateways configured on the
network adapters. You mentioned that both servers have two network adapters. Assuming
that one adapter is connected to an internet path, that adapter should have a static configured
gateway. The other adapter is on the local network and that should NOT have a static IP for a
gateway.

The issue you are seeing is most likely that there is a static gateway configured on both
network adapters. Only the one going to the outside should have a gateway. The internal one
should not.

Hope this helps,
Gary

--------------------
'--'Content-Class: urn:content-classes:message
'--'From: "Justin Wilson"
'--'Sender: "Justin Wilson"
'--'Subject: Intermittent network functionality
'--'Date: Thu, 29 Jan 2004 18:45:44 -0800
'--'Lines: 22
'--'Message-ID: <6a2701c3e6db$28630470$a101280a@phx.gbl>
'--'MIME-Version: 1.0
'--'Content-Type: text/plain;
'--' charset="iso-8859-1"
'--'Content-Transfer-Encoding: 7bit
'--'X-Newsreader: Microsoft CDO for Windows 2000
'--'Thread-Index: AcPm2yhjRT0MU5WKQ6W7YXpiEGnliQ==
'--'X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
'--'Newsgroups: microsoft.public.win2000.networking
'--'Path: cpmsftngxa07.phx.gbl
'--'Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.networking:53180
'--'NNTP-Posting-Host: tk2msftngxa09.phx.gbl 10.40.1.161
'--'X-Tomcat-NG: microsoft.public.win2000.networking
'--'
'--'I have what can only be described as an 'interesting'
'--'problem. I'm setting up 2 Windows 2000 servers for 2 small
'--'networks. Each server has two NICs.
'--'
'--'Two days ago, I connected a 2000 Professional machine to
'--'one of the servers via a crossover cable, and copied some
'--'stuff over (service pack install file, etc.), no problems.
'--'
'--'After service packing the machine, and setting up DNS and
'--'Active Directory, I can no longer connect to the server
'--'from 2000 Pro. The network cards are all installed and
'--'working properly on both machines, and if I use a
'--'crossover cable to loopback, I can get both machines to
'--'ping themselves through the other interface. As soon as I
'--'connect the cable to link the machines (and even though
'--'Windows says they are connected), I can't.
'--'
'--'The other machine (second server) has been unable to see
'--'the client at all. Is there some ridiculously simple step
'--'I have forgotten somewhere here?
'--'
'--'
'--'


--

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.

Thanks for the suggestion, but no NICs in either machine
have a gateway set up. Here's another interesting twist -
one machine will give out an IP address and can be pinged
by the client, but can't ping the client in return.
Nothing else has changed on the other machine (still won't
ping or be pinged).
Gary Fose [MSFT]
Hi Justin,

Ping is very basic and if a machine cannot be pinged, then it is normally a hardware issue (if
there there is no firewalls installed/ICF activated, etc.). So you may want to invesitgate the path
the machines take. Place two machines on a hub and then test. My guess there is something
that is blocking such as the switch or some type of "protective" service on the server. Some
antivirus programs now come with programs called something like (server protect) which acts
like a firewall. Make sure the cables being used to connect the machines ot the switch or hub
are not crossover cables. This will give the same results. They should be straight ethernet
cables.

Thanks,
Gary
--------------------
'--'Content-Class: urn:content-classes:message
'--'From:
'--'Sender:
'--'References: <6a2701c3e6db$28630470$a101280a@phx.gbl> @cpmsftngxa07.phx.gbl>
'--'Subject: RE: Intermittent network functionality
'--'Date: Sat, 31 Jan 2004 19:45:07 -0800
'--'Lines: 6
'--'Message-ID: <7ea001c3e875$c8a48a30$a501280a@phx.gbl>
'--'MIME-Version: 1.0
'--'Content-Type: text/plain;
'--' charset="iso-8859-1"
'--'Content-Transfer-Encoding: 7bit
'--'X-Newsreader: Microsoft CDO for Windows 2000
'--'X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
'--'Thread-Index: AcPodcik6Je3TsWSQciWq4RwJrfQKw==
'--'Newsgroups: microsoft.public.win2000.networking
'--'Path: cpmsftngxa07.phx.gbl
'--'Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.networking:53338
'--'NNTP-Posting-Host: tk2msftngxa13.phx.gbl 10.40.1.165
'--'X-Tomcat-NG: microsoft.public.win2000.networking
'--'
'--'Thanks for the suggestion, but no NICs in either machine
'--'have a gateway set up. Here's another interesting twist -
'--'one machine will give out an IP address and can be pinged
'--'by the client, but can't ping the client in return.
'--'Nothing else has changed on the other machine (still won't
'--'ping or be pinged).
'--'


--

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.