|
| |||||||||
| Tags: destination, host, unreachable |
![]() |
| | Thread Tools | Search this Thread |
|
#1
| |||
| |||
| Destination Host Unreachable
I have an issue "pinging" a specific host (or IP for that matter.) I am running Windows XP SP3 on a private network, that is joined to a SBS2003 Domain. All other computers on the network are running fine, and do not have this routing issue. I cannot seem to figure out why I cannot be routed to a specific IP. I noticed that I was unable to download any drivers from dell. All drivers directly download from dell come from the site ftp.us.dell.com. When I nslookup this, I can resolve it to 143.166.170.10. If I try to ping either 143.166.170.10 or ftp.us.dell.com, I get the destination host unreachable error. I will paste some diagnostic information below. C:\Documents and Settings\MLoughran>ping ftp.us.dell.com Pinging ftp.ins.dell.com [143.166.11.10] with 32 bytes of data: Destination host unreachable. Destination host unreachable. Destination host unreachable. Destination host unreachable. Ping statistics for 143.166.11.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Documents and Settings\USER>print route Can't find file route C:\Documents and Settings\USER>route print =========================================================================== Interface List 0x1 ........................... MS TCP Loopback interface 0x2 ...00 19 b9 1b 84 6a ...... Broadcom NetXtreme 57xx Gigabit Controller - Pac ket Scheduler Miniport =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.123.254 192.168.123.111 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.123.0 255.255.255.0 192.168.123.111 192.168.123.111 20 192.168.123.111 255.255.255.255 127.0.0.1 127.0.0.1 20 192.168.123.255 255.255.255.255 192.168.123.111 192.168.123.111 20 224.0.0.0 240.0.0.0 192.168.123.111 192.168.123.111 20 255.255.255.255 255.255.255.255 192.168.123.111 192.168.123.111 1 Default Gateway: 192.168.123.254 =========================================================================== Persistent Routes: None C:\Documents and Settings\USER>nslookup Default Server: seminole.ourdomainlocal Address: 192.168.123.10 > ftp.us.dell.com Server: seminole.ourdomain.local Address: 192.168.123.10 Non-authoritative answer: Name: ftp.ins.dell.com Address: 143.166.170.10 Aliases: ftp.us.dell.com > exit C:\Documents and Settings\USER>clear 'clear' is not recognized as an internal or external command, operable program or batch file. C:\Documents and Settings\USER>clear 'clear' is not recognized as an internal or external command, operable program or batch file. C:\Documents and Settings\USER>clr 'clr' is not recognized as an internal or external command, operable program or batch file. C:\Documents and Settings\USER>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : MEL1 Primary Dns Suffix . . . . . . . : ourdomain.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : ourdomain.local ourdomain.local Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : ourdomain.local Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Cont roller Physical Address. . . . . . . . . : 00-19-B9-1B-84-6A Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.123.111 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.123.254 DHCP Server . . . . . . . . . . . : 192.168.123.10 DNS Servers . . . . . . . . . . . : 192.168.123.10 Primary WINS Server . . . . . . . : 192.168.123.10 Lease Obtained. . . . . . . . . . : Tuesday, September 22, 2009 10:59:06 AM Lease Expires . . . . . . . . . . : Tuesday, September 29, 2009 10:59:06 AM C:\Documents and Settings\USER>ping 143.166.170.10 Pinging 143.166.170.10 with 32 bytes of data: Destination host unreachable. Destination host unreachable. Destination host unreachable. Destination host unreachable. Ping statistics for 143.166.170.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Documents and Settings\USER>ping ftp.us.dell.com Pinging ftp.ins.dell.com [143.166.170.10] with 32 bytes of data: Destination host unreachable. Destination host unreachable. Destination host unreachable. Destination host unreachable. Ping statistics for 143.166.170.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Documents and Settings\USER>route print =========================================================================== Interface List 0x1 ........................... MS TCP Loopback interface 0x2 ...00 19 b9 1b 84 6a ...... Broadcom NetXtreme 57xx Gigabit Controller - Pac ket Scheduler Miniport =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.123.254 192.168.123.111 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.123.0 255.255.255.0 192.168.123.111 192.168.123.111 20 192.168.123.111 255.255.255.255 127.0.0.1 127.0.0.1 20 192.168.123.255 255.255.255.255 192.168.123.111 192.168.123.111 20 224.0.0.0 240.0.0.0 192.168.123.111 192.168.123.111 20 255.255.255.255 255.255.255.255 192.168.123.111 192.168.123.111 1 Default Gateway: 192.168.123.254 =========================================================================== Persistent Routes: None C:\Documents and Settings\USER>ping google.com Pinging google.com [74.125.45.100] with 32 bytes of data: Reply from 74.125.45.100: bytes=32 time=52ms TTL=46 Reply from 74.125.45.100: bytes=32 time=53ms TTL=46 Reply from 74.125.45.100: bytes=32 time=53ms TTL=46 Reply from 74.125.45.100: bytes=32 time=53ms TTL=46 Ping statistics for 74.125.45.100: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 52ms, Maximum = 53ms, Average = 52ms C:\Documents and Settings\USER>ping 127.0.0.1 Pinging 127.0.0.1 with 32 bytes of data: Reply from 127.0.0.1: bytes=32 time<1ms TTL=64 Reply from 127.0.0.1: bytes=32 time<1ms TTL=64 Reply from 127.0.0.1: bytes=32 time<1ms TTL=64 Reply from 127.0.0.1: bytes=32 time<1ms TTL=64 Ping statistics for 127.0.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms Additional Info: My firewall device at 192.168.123.254 can ping both ftp.us.dell.com and the IP address just fine. ALL OTHER PC's behind the firewall can ping/tracert both just fine, this is only on my PC. Anyone have ANY ideas I can try to resolve this issue? |
|
#2
| |||
| |||
| Re: Destination Host Unreachable mikeyuf@gmail.com wrote: > I have an issue "pinging" a specific host (or IP for that matter.) > > I am running Windows XP SP3 on a private network, that is joined to a > SBS2003 Domain. All other computers on the network are running fine, > and do not have this routing issue. > > I cannot seem to figure out why I cannot be routed to a specific IP. > I noticed that I was unable to download any drivers from dell. All > drivers directly download from dell come from the site > ftp.us.dell.com. When I nslookup this, I can resolve it to > 143.166.170.10. If I try to ping either 143.166.170.10 or > ftp.us.dell.com, I get the destination host unreachable error. I will > paste some diagnostic information below. > > C:\Documents and Settings\MLoughran>ping ftp.us.dell.com > > Pinging ftp.ins.dell.com [143.166.11.10] with 32 bytes of data: > > Destination host unreachable. > Destination host unreachable. > Destination host unreachable. > Destination host unreachable. > > Ping statistics for 143.166.11.10: > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), > > C:\Documents and Settings\USER>print route > Can't find file route > > C:\Documents and Settings\USER>route print > =========================================================================== > Interface List > 0x1 ........................... MS TCP Loopback interface > 0x2 ...00 19 b9 1b 84 6a ...... Broadcom NetXtreme 57xx Gigabit > Controller - Pac > ket Scheduler Miniport > =========================================================================== > =========================================================================== > Active Routes: > Network Destination Netmask Gateway Interface > Metric > 0.0.0.0 0.0.0.0 192.168.123.254 > 192.168.123.111 20 > 127.0.0.0 255.0.0.0 127.0.0.1 > 127.0.0.1 1 > 192.168.123.0 255.255.255.0 192.168.123.111 > 192.168.123.111 20 > 192.168.123.111 255.255.255.255 127.0.0.1 > 127.0.0.1 20 > 192.168.123.255 255.255.255.255 192.168.123.111 > 192.168.123.111 20 > 224.0.0.0 240.0.0.0 192.168.123.111 > 192.168.123.111 20 > 255.255.255.255 255.255.255.255 192.168.123.111 > 192.168.123.111 1 > Default Gateway: 192.168.123.254 > =========================================================================== > Persistent Routes: > None > > C:\Documents and Settings\USER>nslookup > Default Server: seminole.ourdomainlocal > Address: 192.168.123.10 > >> ftp.us.dell.com > Server: seminole.ourdomain.local > Address: 192.168.123.10 > > Non-authoritative answer: > Name: ftp.ins.dell.com > Address: 143.166.170.10 > Aliases: ftp.us.dell.com > >> exit > > C:\Documents and Settings\USER>clear > 'clear' is not recognized as an internal or external command, > operable program or batch file. > > C:\Documents and Settings\USER>clear > 'clear' is not recognized as an internal or external command, > operable program or batch file. > > C:\Documents and Settings\USER>clr > 'clr' is not recognized as an internal or external command, > operable program or batch file. > > C:\Documents and Settings\USER>ipconfig /all > > Windows IP Configuration > > Host Name . . . . . . . . . . . . : MEL1 > Primary Dns Suffix . . . . . . . : ourdomain.local > Node Type . . . . . . . . . . . . : Hybrid > IP Routing Enabled. . . . . . . . : No > WINS Proxy Enabled. . . . . . . . : No > DNS Suffix Search List. . . . . . : ourdomain.local > ourdomain.local > > Ethernet adapter Local Area Connection: > > Connection-specific DNS Suffix . : ourdomain.local > Description . . . . . . . . . . . : Broadcom NetXtreme 57xx > Gigabit Cont > roller > Physical Address. . . . . . . . . : 00-19-B9-1B-84-6A > Dhcp Enabled. . . . . . . . . . . : Yes > Autoconfiguration Enabled . . . . : Yes > IP Address. . . . . . . . . . . . : 192.168.123.111 > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > Default Gateway . . . . . . . . . : 192.168.123.254 > DHCP Server . . . . . . . . . . . : 192.168.123.10 > DNS Servers . . . . . . . . . . . : 192.168.123.10 > Primary WINS Server . . . . . . . : 192.168.123.10 > Lease Obtained. . . . . . . . . . : Tuesday, September 22, > 2009 10:59:06 > AM > Lease Expires . . . . . . . . . . : Tuesday, September 29, > 2009 10:59:06 > AM > > C:\Documents and Settings\USER>ping 143.166.170.10 > > Pinging 143.166.170.10 with 32 bytes of data: > > Destination host unreachable. > Destination host unreachable. > Destination host unreachable. > Destination host unreachable. > > Ping statistics for 143.166.170.10: > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), > > C:\Documents and Settings\USER>ping ftp.us.dell.com > > Pinging ftp.ins.dell.com [143.166.170.10] with 32 bytes of data: > > Destination host unreachable. > Destination host unreachable. > Destination host unreachable. > Destination host unreachable. > > Ping statistics for 143.166.170.10: > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), > > C:\Documents and Settings\USER>route print > =========================================================================== > Interface List > 0x1 ........................... MS TCP Loopback interface > 0x2 ...00 19 b9 1b 84 6a ...... Broadcom NetXtreme 57xx Gigabit > Controller - Pac > ket Scheduler Miniport > =========================================================================== > =========================================================================== > Active Routes: > Network Destination Netmask Gateway Interface > Metric > 0.0.0.0 0.0.0.0 192.168.123.254 > 192.168.123.111 20 > 127.0.0.0 255.0.0.0 127.0.0.1 > 127.0.0.1 1 > 192.168.123.0 255.255.255.0 192.168.123.111 > 192.168.123.111 20 > 192.168.123.111 255.255.255.255 127.0.0.1 > 127.0.0.1 20 > 192.168.123.255 255.255.255.255 192.168.123.111 > 192.168.123.111 20 > 224.0.0.0 240.0.0.0 192.168.123.111 > 192.168.123.111 20 > 255.255.255.255 255.255.255.255 192.168.123.111 > 192.168.123.111 1 > Default Gateway: 192.168.123.254 > =========================================================================== > Persistent Routes: > None > > C:\Documents and Settings\USER>ping google.com > > Pinging google.com [74.125.45.100] with 32 bytes of data: > > Reply from 74.125.45.100: bytes=32 time=52ms TTL=46 > Reply from 74.125.45.100: bytes=32 time=53ms TTL=46 > Reply from 74.125.45.100: bytes=32 time=53ms TTL=46 > Reply from 74.125.45.100: bytes=32 time=53ms TTL=46 > > Ping statistics for 74.125.45.100: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 52ms, Maximum = 53ms, Average = 52ms > > C:\Documents and Settings\USER>ping 127.0.0.1 > > Pinging 127.0.0.1 with 32 bytes of data: > > Reply from 127.0.0.1: bytes=32 time<1ms TTL=64 > Reply from 127.0.0.1: bytes=32 time<1ms TTL=64 > Reply from 127.0.0.1: bytes=32 time<1ms TTL=64 > Reply from 127.0.0.1: bytes=32 time<1ms TTL=64 > > Ping statistics for 127.0.0.1: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 0ms, Maximum = 0ms, Average = 0ms > > > Additional Info: > > My firewall device at 192.168.123.254 can ping both ftp.us.dell.com > and the IP address just fine. > > ALL OTHER PC's behind the firewall can ping/tracert both just fine, > this is only on my PC. > > Anyone have ANY ideas I can try to resolve this issue? A lot of companies and individuals set their servers/pcs/routers to swallow ping packets. In other words you can ping them as much as you like, but your request is ignored and the ping fails giving an unreachable message. They do this to prevent their servers becoming overloaded answering ping requests, which otherwise could either crash the server, or slow it down to the speed of an arthritic snail. |
|
#3
| |||
| |||
| Re: Destination Host Unreachable
"mikeyuf@gmail.com" <mikeyuf@gmail.com> wrote in news:8bb44b80-2d2f-4a8e-a39f-a5af26d77ba5@z28g2000vbl.googlegroups.co m: > I have an issue "pinging" a specific host (or IP for that matter.) > > I am running Windows XP SP3 on a private network, that is joined > to a SBS2003 Domain. All other computers on the network are > running fine, and do not have this routing issue. > > I cannot seem to figure out why I cannot be routed to a specific > IP. I noticed that I was unable to download any drivers from dell. > All drivers directly download from dell come from the site > ftp.us.dell.com. When I nslookup this, I can resolve it to > 143.166.170.10. If I try to ping either 143.166.170.10 or > ftp.us.dell.com, I get the destination host unreachable error. I > will paste some diagnostic information below. > > Additional Info: [...] > > My firewall device at 192.168.123.254 can ping both > ftp.us.dell.com and the IP address just fine. > > ALL OTHER PC's behind the firewall can ping/tracert both just > fine, this is only on my PC. > > Anyone have ANY ideas I can try to resolve this issue? > Your configuration info looks fine for the network topology you describe. The one bit of info you did not post was the result of a tracert. From what I can tell, everything is pointing to your nameless "firewall device" at 192.168.123.254. Firewall devices can be configured to allow/deny based on IP addresses, ports, and MAC addresses among other things. Check the configuration of your firewall device to see if you've excluding yourself by virtue of your firewall device settings. As a test, try replacing it with a simple router. If you have any firewall software installed on your computer, check that too. You might also try "LSPFix". Sometimes it will fix strange problems like this. <http://www.cexx.org/lspfix.htm> HTH, John |
![]() |
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "Destination Host Unreachable" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Cydia problem in China - apt.saurik.com Host Unreachable | Christia | Portable Devices | 7 | 24-09-2010 09:11 AM |
| A socket operation was attempted to an unreachable host | Tanveer Joshi | Technology & Internet | 6 | 26-06-2010 01:14 AM |
| VISTA Can't See Printer 'Host Unreachable' | bitsailor | Windows Vista Network | 4 | 16-04-2009 06:23 AM |
| Unicast and destination host host unreachable. | Rush | Windows Server Help | 6 | 24-08-2007 03:53 PM |
| NLB "host unreachable" error | Lloyd | Windows Server Help | 3 | 09-08-2005 02:43 AM |