Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows 2000 won't ping anything on local subnet

Status
Not open for further replies.

msdonb

IS-IT--Management
Dec 20, 2007
61
I've got a laptop running Windows 2000 with an integrated NIC and a Netgear Wireless PC Card. The laptop gets internet, but won't see anything but itself on the LAN. I can't ping any other device on my LAN, nor will it resolve any windows workgroup computer names. Nothing else will ping via IP except itself & loopback. But it's GETTING its IP from a dedicated DHCP server? Yet it can't ping the DHCP server!??!? WTF!?!? Any ideas?
 
Pull the wireless card and see what you get.


"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 
Tried that... still nothing. I've also tried uninstalling/reinstalling all the drivers/hardware. I just took the thing to jack in the box to use their wifi and VPN'd into my network. From an outside IP everything works fine. However, when I plug into my physical LAN, i get nothing. The DHCP server is assigning it an IP address, and there's a gateway allowing it to get outbound to the internet. Internet works, but nothing on the LAN side functions. I can't even get other machines to ping it once it's connected. Strange, I'm having the exact same problems on both laptops. (Identical DELL Latitude configurations, aside from processor speed)
 
Typically you can't run a wireless and a wired at the same time. When you plug in at home, are you sure the connectivity you see is not coming from the wireless?

What do you get with
Code:
ipconfig /all
?


"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 
As you can see, each NIC gets its own IP address from 192.168.43.15, yet it can't even ping that address. Frustrating! Same problem on TWO different laptops... both were reformatted recently with new OS/patches/neccessary apps. Dialup & VPN both work on the LAN, but then again, they are outside/external IP addresses pinging inbound. DNS is working fine, as you can see I can ping outside IPs and the internet works flawlessly.



C:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : mslaptop001
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR 108 Mbps Wireless PC Card WG
511T
Physical Address. . . . . . . . . : 00-09-5B-C6-0A-18
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.43.67
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.43.254
DHCP Server . . . . . . . . . . . : 192.168.43.15
DNS Servers . . . . . . . . . . . : 199.2.252.10
204.97.212.10
Lease Obtained. . . . . . . . . . : Thursday, February 07, 2008 11:04:51
AM
Lease Expires . . . . . . . . . . : Thursday, February 07, 2008 5:04:51
PM

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast Ethernet
Controller (3C905C-TX Compatible)
Physical Address. . . . . . . . . : 00-08-74-4A-E8-40
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.43.236
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.43.254
DHCP Server . . . . . . . . . . . : 192.168.43.15
DNS Servers . . . . . . . . . . . : 199.2.252.10
204.97.212.10
Lease Obtained. . . . . . . . . . : Thursday, February 07, 2008 11:06:06
AM
Lease Expires . . . . . . . . . . : Thursday, February 07, 2008 5:06:06


C:\>netstat -a

Active Connections

Proto Local Address Foreign Address State
TCP mslaptop001:epmap mslaptop001:0 LISTENING
TCP mslaptop001:microsoft-ds mslaptop001:0 LISTENING
TCP mslaptop001:1025 mslaptop001:0 LISTENING
TCP mslaptop001:64924 mslaptop001:0 LISTENING
TCP mslaptop001:netbios-ssn mslaptop001:0 LISTENING
TCP mslaptop001:1103 AS-20144-has-not-REGISTERED-the-use-of-this-pref
ix:domain TIME_WAIT
TCP mslaptop001:1131 k.root-servers.net:domain TIME_WAIT
TCP mslaptop001:1134 AS-20144-has-not-REGISTERED-the-use-of-this-pref
ix:domain TIME_WAIT
TCP mslaptop001:1136 old-j-root-servers-net.verisign-grs.net:domain
TIME_WAIT
TCP mslaptop001:netbios-ssn mslaptop001:0 LISTENING
UDP mslaptop001:microsoft-ds *:*
UDP mslaptop001:isakmp *:*
UDP mslaptop001:1030 *:*
UDP mslaptop001:4500 *:*
UDP mslaptop001:62514 *:*
UDP mslaptop001:1032 *:*
UDP mslaptop001:netbios-ns *:*
UDP mslaptop001:netbios-dgm *:*
UDP mslaptop001:netbios-ns *:*
UDP mslaptop001:netbios-dgm *:*

C:\>



C:\>netstat -a

Active Connections

Proto Local Address Foreign Address State
TCP mslaptop001:epmap mslaptop001:0 LISTENING
TCP mslaptop001:microsoft-ds mslaptop001:0 LISTENING
TCP mslaptop001:1025 mslaptop001:0 LISTENING
TCP mslaptop001:64924 mslaptop001:0 LISTENING
TCP mslaptop001:netbios-ssn mslaptop001:0 LISTENING
TCP mslaptop001:1103 AS-20144-has-not-REGISTERED-the-use-of-this-pref
ix:domain TIME_WAIT
TCP mslaptop001:1131 k.root-servers.net:domain TIME_WAIT
TCP mslaptop001:1134 AS-20144-has-not-REGISTERED-the-use-of-this-pref
ix:domain TIME_WAIT
TCP mslaptop001:1136 old-j-root-servers-net.verisign-grs.net:domain
TIME_WAIT
TCP mslaptop001:netbios-ssn mslaptop001:0 LISTENING
UDP mslaptop001:microsoft-ds *:*
UDP mslaptop001:isakmp *:*
UDP mslaptop001:1030 *:*
UDP mslaptop001:4500 *:*
UDP mslaptop001:62514 *:*
UDP mslaptop001:1032 *:*
UDP mslaptop001:netbios-ns *:*
UDP mslaptop001:netbios-dgm *:*
UDP mslaptop001:netbios-ns *:*
UDP mslaptop001:netbios-dgm *:*

C:\>




C:\>ping 192.168.43.67

Pinging 192.168.43.67 with 32 bytes of data:

Reply from 192.168.43.67: bytes=32 time<10ms TTL=128
Reply from 192.168.43.67: bytes=32 time<10ms TTL=128
Reply from 192.168.43.67: bytes=32 time<10ms TTL=128
Reply from 192.168.43.67: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.43.67:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>


C:\>ping 192.168.43.236

Pinging 192.168.43.236 with 32 bytes of data:

Reply from 192.168.43.236: bytes=32 time<10ms TTL=128
Reply from 192.168.43.236: bytes=32 time<10ms TTL=128
Reply from 192.168.43.236: bytes=32 time<10ms TTL=128
Reply from 192.168.43.236: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.43.236:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>


C:\>ping 192.168.43.254

Pinging 192.168.43.254 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.43.254:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>ping 192.168.43.15

Pinging 192.168.43.15 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.43.15:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>


C:\>ping
Pinging [209.131.36.158] with 32 bytes of data:

Reply from 209.131.36.158: bytes=32 time=28ms TTL=58
Reply from 209.131.36.158: bytes=32 time=40ms TTL=59
Reply from 209.131.36.158: bytes=32 time=27ms TTL=58
Reply from 209.131.36.158: bytes=32 time=27ms TTL=59

Ping statistics for 209.131.36.158:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 40ms, Average = 30ms

C:\>
 
Sorry for the repeat on the netstat -a... I meant to show you the arp settings. Here they are.


C:\Documents and Settings\derekg>arp -a

Interface: 192.168.43.236 on Interface 0x1000004
Internet Address Physical Address Type
192.168.43.15 00-60-08-a4-a3-2d dynamic
192.168.43.93 00-14-51-11-57-78 dynamic
192.168.43.233 00-a0-c8-20-89-07 dynamic
192.168.43.254 00-12-01-1e-03-be dynamic

C:\Documents and Settings\derekg>ping 192.168.43.15

Pinging 192.168.43.15 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.43.15:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\derekg>



 
I'm not sure what the problem is, but I would pull the wireless and get the wired connection working first.


"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 
They both do the exact same thing. Whether it's ONLY the wireless or ONLY the wired ethernet. Exact same response. :\
 
What have you got set up for security? Something is blocking this, and I'm guessing it's software. Give the laptop a fixed IP and see how the software likes it. I'm guessing someone on the server is going to have a hissy fit. Good luck.

Glen A. Johnson
Johnson Computer Consulting
[americanflag]
Support our Troops!

 
Can you ping your own adress or 127.0.0.1?

y1pzZTEUdok1vrI5cLb3FdPX4PgTPlSONkb5WPjz0x50etSujaMSmhdRCbOx9vASnrRNzzXv0IxNQA

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
 
If it ARPs, then he should be able to ping the loopback, showing the IP stack is all there. This really sounds like the server and gateway are blocking ICPM echoes, but only if it does this on other workstations as well... Have you tried pinging the laptops FROM the server and gateway? Do other workstations have this problem? Is Norton running on the laptops? Even Worm Protection? I had to shut worm protection off on mine to be able to FTP to my FTP server at home!
One other thing to consider if the two laptops are the only two doing it---System Restore to before the patches were installed then try it. You did backup/create a restore point before installing the patches, right???

Burt
 
Could it be that you used the same IPadress on your laptop/PC as the one in the Switch?

y1pzZTEUdok1vrI5cLb3FdPX4PgTPlSONkb5WPjz0x50etSujaMSmhdRCbOx9vASnrRNzzXv0IxNQA

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
 
First, you would get a Windows Duplicate IP warning. Second, one of them would do nothing. Both work.

Burt
 
They are NOT duplicate IP addresses on the network. The DHCP server is assigning these addresses and all adapters are being assigned unique IP addresses. It's so wierd that I can see an ARP table with various devices/IPs listed, but can't being anything but the host itself. Yet I can ping anything OUTSIDE the subnet. There is no security setup on the laptops, this issue presented itself long before I installed any virus software/firewall stuff as I thought that would be to blame. I'm wondering if it's the VPN client that's causing the issues, we're using an Adtran Netvanta VPN client and it's almost impossible to uninstall though. I guess it's fine for now since the laptops are primarily being used outside of the building and everything seems to work fine when it's using an IP other than the one on my LANs subnet. :\
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top