ryanlui
asked on
A computer gets its IP address but cannot ping local gateway and other computer devices within the same network
Symptoms:
1. Connect to network ( obtained IP address from DHCP)
2. Can ping localhost 127.0.0.1
3. Can ping its own IP address 10.0.0.103
4. Cannot ping gateway 10.0.0.1
Details
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Ryan>route print
========================== ========== ========== ========== ========== =========
Interface List
0x1 .......................... . MS TCP Loopback interface
0x20002 ...00 0a cd 1a 7f 9f ...... Realtek RTL8169/8110 Family Gigabit Ethernet
NIC - Packet Scheduler Miniport
========================== ========== ========== ========== ========== =========
========================== ========== ========== ========== ========== =========
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.103 20
10.0.0.0 255.255.255.0 10.0.0.103 10.0.0.103 20
10.0.0.103 255.255.255.255 127.0.0.1 127.0.0.1 20
10.255.255.255 255.255.255.255 10.0.0.103 10.0.0.103 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
169.254.0.0 255.255.0.0 10.0.0.103 10.0.0.103 20
224.0.0.0 240.0.0.0 10.0.0.103 10.0.0.103 20
255.255.255.255 255.255.255.255 10.0.0.103 10.0.0.103 1
Default Gateway: 10.0.0.1
========================== ========== ========== ========== ========== =========
Persistent Routes:
None
C:\Documents and Settings\Ryan>ping 10.0.0.103
Pinging 10.0.0.103 with 32 bytes of data:
Reply from 10.0.0.103: bytes=32 time<1ms TTL=128
Reply from 10.0.0.103: bytes=32 time<1ms TTL=128
Reply from 10.0.0.103: bytes=32 time<1ms TTL=128
Reply from 10.0.0.103: bytes=32 time<1ms TTL=128
Ping statistics for 10.0.0.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\Ryan>ping 10.0.0.1
Pinging 10.0.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.0.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
thanks,
Ryan
1. Connect to network ( obtained IP address from DHCP)
2. Can ping localhost 127.0.0.1
3. Can ping its own IP address 10.0.0.103
4. Cannot ping gateway 10.0.0.1
Details
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Ryan>route print
==========================
Interface List
0x1 ..........................
0x20002 ...00 0a cd 1a 7f 9f ...... Realtek RTL8169/8110 Family Gigabit Ethernet
NIC - Packet Scheduler Miniport
==========================
==========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.103 20
10.0.0.0 255.255.255.0 10.0.0.103 10.0.0.103 20
10.0.0.103 255.255.255.255 127.0.0.1 127.0.0.1 20
10.255.255.255 255.255.255.255 10.0.0.103 10.0.0.103 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
169.254.0.0 255.255.0.0 10.0.0.103 10.0.0.103 20
224.0.0.0 240.0.0.0 10.0.0.103 10.0.0.103 20
255.255.255.255 255.255.255.255 10.0.0.103 10.0.0.103 1
Default Gateway: 10.0.0.1
==========================
Persistent Routes:
None
C:\Documents and Settings\Ryan>ping 10.0.0.103
Pinging 10.0.0.103 with 32 bytes of data:
Reply from 10.0.0.103: bytes=32 time<1ms TTL=128
Reply from 10.0.0.103: bytes=32 time<1ms TTL=128
Reply from 10.0.0.103: bytes=32 time<1ms TTL=128
Reply from 10.0.0.103: bytes=32 time<1ms TTL=128
Ping statistics for 10.0.0.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\Ryan>ping 10.0.0.1
Pinging 10.0.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.0.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
thanks,
Ryan
Try a static IP address and see if you can ping.
Is this your home or work? If work, do you know if your networking group allows you to ping the routers?
Pulling a DHCP address from a DHCP server on the same subnet doesn't require the gateway so that isn't strange. I agree with Shadowless127 that the gateway for all you traffic seems to be .103 even though it states the default gateway at the bottom is .1
If other devices can ping the gateway then it is possible your NIC is faulty. In this case, if onboard NIC, disable and install a PCI NIC to see if same problem.
If other devices cannot ping gateway, most likely it is firewall settings on the gateway router.
Other possibility is this device has somehow been put into a different VLAN from the gateway (although I would have expected to see network device bUnreachable on the ping if this were the case).
If other devices cannot ping gateway, most likely it is firewall settings on the gateway router.
Other possibility is this device has somehow been put into a different VLAN from the gateway (although I would have expected to see network device bUnreachable on the ping if this were the case).
ipconfig /all just post the active adapter information.
The routing table looks OK to me except for this entry:
10.255.255.255 255.255.255.255 10.0.0.103 10.0.0.103 20
The subnet is 10.0.0.0 / 255.255.255.0
So, the broadcast address is 10.0.0.255
Why would you need to reach 10.255.255.255 at all?
And, how do you reach 10.0.0.255 then? I believe it would be common to see:
10.0.0.255 255.255.255.255 10.0.0.103
But then, this doesn't explain to me how you can't ping an address in the subnet.
Firewalls, firewalls, firewalls......
10.255.255.255 255.255.255.255 10.0.0.103 10.0.0.103 20
The subnet is 10.0.0.0 / 255.255.255.0
So, the broadcast address is 10.0.0.255
Why would you need to reach 10.255.255.255 at all?
And, how do you reach 10.0.0.255 then? I believe it would be common to see:
10.0.0.255 255.255.255.255 10.0.0.103
But then, this doesn't explain to me how you can't ping an address in the subnet.
Firewalls, firewalls, firewalls......
ASKER
I tried things but they did not work
1. used static ip, 10.0.0.99
2. disable firewall on system
3. Add new PCI Gigabit netcard and disable the onboard one
This is a netgear wireless router.
Any more idea?
1. used static ip, 10.0.0.99
2. disable firewall on system
3. Add new PCI Gigabit netcard and disable the onboard one
This is a netgear wireless router.
Any more idea?
Can you ping the netgear router from another machine on the subnet?
Can you get on the router to ping from it to .103?
What is the IP of the DHCP server?
Can you get on the router to ping from it to .103?
What is the IP of the DHCP server?
Can you maybe try to do a ping to the DG and then check the arp cache via:
ping 10.0.0.1
arp -a
Please check if you have a dynamic arp entry (it should not be static) for 10.0.0.1 and post the output of the arp command here.
ASKER
Referred to qbakies:
Can you ping the netgear router from another machine on the subnet?
>> Yes, I can pick the netgear router from another machine.
Can you get on the router to ping from it to .103?
>> On the router, I cannot ping the .103 (//firewall is disable)
What is the IP of the DHCP server?
>> 10.0.0.1
Can you ping the netgear router from another machine on the subnet?
>> Yes, I can pick the netgear router from another machine.
Can you get on the router to ping from it to .103?
>> On the router, I cannot ping the .103 (//firewall is disable)
What is the IP of the DHCP server?
>> 10.0.0.1
cable died
Hi
Run a protocol analyzer on your computer (Wireshark ). Check if ARP request packet is going to the intended destination (gateway) from the computer and your are receiving an ARP response ??
Check if the ping request packet is going out of the computer or is it the response from the gateway which is not being received using the analyzer ?
Run a protocol analyzer on your computer (Wireshark ). Check if ARP request packet is going to the intended destination (gateway) from the computer and your are receiving an ARP response ??
Check if the ping request packet is going out of the computer or is it the response from the gateway which is not being received using the analyzer ?
What if you manually enter all the information?
I'm still wondering about the broadcast address in the routing table - as I mentioned earlier.
I'm still wondering about the broadcast address in the routing table - as I mentioned earlier.
@fmarshall About the broadcast address. This happens to be normal behavior. Since the 10 network is subnetted here with /24 the subnet broadcast address is indeed 10.0.0.255. However the routing table does not need an entry for this.
The entry you mentioned is the all-subnet directed broadcast address. As 10 is part of the Class A address range an entry with 10.255.255.255 will be created which points to the IP-address of the computer. This entry depends on the Class of the IP-address used (classful).
See also http://technet.microsoft.com/en-us/library/cc958823.aspx
section "Network Broadcast"
and http://www.microsoft.com/mspress/books/sampchap/5030a.aspx
section "All-Subnets-Directed Broadcast"
The entry you mentioned is the all-subnet directed broadcast address. As 10 is part of the Class A address range an entry with 10.255.255.255 will be created which points to the IP-address of the computer. This entry depends on the Class of the IP-address used (classful).
See also http://technet.microsoft.com/en-us/library/cc958823.aspx
section "Network Broadcast"
and http://www.microsoft.com/mspress/books/sampchap/5030a.aspx
section "All-Subnets-Directed Broadcast"
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for ryanlui's comment #a38368942
for the following reason:
The problem is solved
Accepted answer: 0 points for ryanlui's comment #a38368942
for the following reason:
The problem is solved
Fair enough