Some can't see network, others can

  • Thread starter Thread starter JGillam
  • Start date Start date
J

JGillam

I recently experienced a somewhat odd situation where two
laptop machines with identical hardware, OS patch levels
and network configurations (win2k sp4) showed different
behaviors from the same physical ethernet connection to a
LAN. The first one, upon startup, connected successfully,
obtained an IP address from the DHCP server, and could see
the network normally. The second machine, on the other
hand, did not obtain an IP address automatically and could
therefore not see the network since it ultimately
autoconfigured itself. This struck me as particularly odd
since this second machine is able to connect to the
network from a different location (i.e. a different
building wired into the same LAN, likely different
infrastructure but that "shouldn't" make a difference,
especially since the first machine was able to connect
without any fuss...).

The following was attempted:
1 - specifially set the speed of the ethernet card instead
of autoconfigure: no effect.
2 - pretty much everything you can do with the ipconfig
command: no effect.
3 - reboot: no effect.
4 - hardcode/copy the IP, DNS, WINS, and Gateway
information that was autoconfigured on the first machine
onto the second machine, unplug first machine and plug in
second machine: this actually worked.
5 - reset to autoconfigure and restart second machine: did
not work.

I found a search of the knowledge base futile since I
don't know specifically where the problem is. Has anyone
out there experienced this sort of behavior before? Any
ideas?
 
JGillam,

First thing I would do is:
1. Make sure the second machine does not have the same name as the first
2. Make sure the second machine doe snot have firewall sotware installed.
3. Run an Ipconfig /all on both machines and make sure all is the same except for the obvious,
computer name, MAC, etc.
4. In the Ipconfig /all, pay particular attention to the Node Type and be sure those are the
same - should be Hybrid.
5. On the second machine, do an ipconfig /release and then reboot. Without running the
ipconfig /release, the computer will not relase it's IP even on a reboot.
6. Plug the second machine into the cable for the first and visa-versa to rule out any issues
with the cable or ports.

Hope this helps,
Gary

--------------------
'--'Content-Class: urn:content-classes:message
'--'From: "JGillam" <[email protected]>
'--'Sender: "JGillam" <[email protected]>
'--'Subject: Some can't see network, others can
'--'Date: Sat, 24 Jan 2004 19:37:10 -0800
'--'Lines: 34
'--'Message-ID: <[email protected]>
'--'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: AcPi9IOu4hL8ZSv9Sceerf0TuZKXrA==
'--'X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
'--'Newsgroups: microsoft.public.win2000.networking
'--'NNTP-Posting-Host: tk2msftngxs01.phx.gbl 10.40.2.125
'--'Path: cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!
TK2MSFTNGXS01.phx.gbl
'--'Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.networking:52565
'--'X-Tomcat-NG: microsoft.public.win2000.networking
'--'
'--'I recently experienced a somewhat odd situation where two
'--'laptop machines with identical hardware, OS patch levels
'--'and network configurations (win2k sp4) showed different
'--'behaviors from the same physical ethernet connection to a
'--'LAN. The first one, upon startup, connected successfully,
'--'obtained an IP address from the DHCP server, and could see
'--'the network normally. The second machine, on the other
'--'hand, did not obtain an IP address automatically and could
'--'therefore not see the network since it ultimately
'--'autoconfigured itself. This struck me as particularly odd
'--'since this second machine is able to connect to the
'--'network from a different location (i.e. a different
'--'building wired into the same LAN, likely different
'--'infrastructure but that "shouldn't" make a difference,
'--'especially since the first machine was able to connect
'--'without any fuss...).
'--'
'--'The following was attempted:
'--'1 - specifially set the speed of the ethernet card instead
'--'of autoconfigure: no effect.
'--'2 - pretty much everything you can do with the ipconfig
'--'command: no effect.
'--'3 - reboot: no effect.
'--'4 - hardcode/copy the IP, DNS, WINS, and Gateway
'--'information that was autoconfigured on the first machine
'--'onto the second machine, unplug first machine and plug in
'--'second machine: this actually worked.
'--'5 - reset to autoconfigure and restart second machine: did
'--'not work.
'--'
'--'I found a search of the knowledge base futile since I
'--'don't know specifically where the problem is. Has anyone
'--'out there experienced this sort of behavior before? Any
'--'ideas?
'--'


--

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.
 
Back
Top