I am connecting to a Windows 2008 server remotely using Teamviewer. I am not sure why, but after connecting to the server, I can no longer connect to Windows XP clients using Remote Desktop. I have tried restarting the server, but that did not fix this. I noticed when trying to ping the machines through name or IP address I am getting a "destination host unreachable" error, but all settings look correct and unchanged. Pinging ict-07.LCS.LOCAL [10.39.4.60] with 32 bytes of data: Reply from 10.39.4.2: Destination host unreachable. Reply from 10.39.4.2: Destination host unreachable. Reply from 10.39.4.2: Destination host unreachable. Reply from 10.39.4.2: Destination host unreachable. Ping statistics for 10.39.4.60: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), And the IPconfig file shows the following: Windows IP Configuration Host Name . . . . . . . . . . . . : LCS-2K8-01 Primary Dns Suffix . . . . . . . : LCS.LOCAL Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : LCS.LOCAL Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : HP NC326i PCIe Dual Port Gigabit Server Adapter #2 Physical Address. . . . . . . . . : D8-D3-85-C1-71-59 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 10.39.4.2(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.254.0 Default Gateway . . . . . . . . . : 10.39.4.1 DNS Servers . . . . . . . . . . . : 10.39.4.2 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Local Area Connection* 9: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{BE676A51-2633-48DD-9654-4361B89F250B} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Does anyone have any ideas please on what might be wrong?

The datagram was delivered to the network specified in the network ID portion of the IP address but could not be sent to the specific host indicated in the address. Again, this usually implies a routing issue. Check your route tables.

"Destination Host Unreachable" is an indication that your system does not have the appropriate information on how to route the packet. While your settings look correct, take a look at the local routing table. --> Start, RUN, CMD, ROUTE PRINT Visit: anITKB.com, an IT Knowledge Base.

Here are the results: =========================================================================== Interface List 11 ...d8 d3 85 c1 71 59 ...... HP NC326i PCIe Dual Port Gigabit Server Adapter #2 1 ........................... Software Loopback Interface 1 14 ...00 00 00 00 00 00 00 e0 isatap.{BE676A51-2633-48DD-9654-4361B89F250B} 13 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.39.4.1 10.39.4.2 266 10.39.4.0 255.255.254.0 On-link 10.39.4.2 266 10.39.4.2 255.255.255.255 On-link 10.39.4.2 266 10.39.5.255 255.255.255.255 On-link 10.39.4.2 266 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 10.39.4.2 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 10.39.4.2 266 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 10.39.4.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 1 306 ff00::/8 On-link =========================================================================== Persistent Routes: None I also ran arp -a and got this: Interface: 10.39.4.2 --- 0xb Internet Address Physical Address Type 10.39.4.1 00-16-4d-df-16-ec dynamic 10.39.4.9 00-e0-81-60-78-bf dynamic 10.39.4.15 00-80-87-f4-2f-e6 dynamic 10.39.4.16 00-80-87-1b-d8-78 dynamic 10.39.4.17 00-80-87-e4-2b-39 dynamic 10.39.4.18 00-80-87-ab-ec-a5 dynamic 10.39.4.19 00-c0-ee-43-95-40 dynamic 10.39.4.20 00-c0-ee-43-95-7c dynamic 10.39.4.95 00-21-70-2e-3f-1e dynamic 10.39.5.255 ff-ff-ff-ff-ff-ff static 224.0.0.22 01-00-5e-00-00-16 static 224.0.0.252 01-00-5e-00-00-fc static 224.0.1.1 01-00-5e-00-01-01 static 239.255.255.250 01-00-5e-7f-ff-fa static 255.255.255.255 ff-ff-ff-ff-ff-ff static The IP's shown are static and mostly printers. The reply OK to Ping requests. Would this error message (Destination host unreachable) also show if the machines have been switched off? I am not able to physically visit the site at the moment, but am wondering if the three machines have shut themselves down. Although if this is the case, I have been sending Magic Packets to them, which has not been waking them up.

I think that you should change the metric for the network 0.0.0.0 and give it a lower value. Change it and tell me if the problem is solved or not.

This link will help you to change your routes: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/route.mspx?mfr=true

hi , Yes, if the machines are switched off you receive destination host unreachable. I would run netmon utility / ethereal utility from the server to better diagonize the problem even after you fix the route problem suggested by useful helper.

Actually, I am pretty sure that if the target hosts are switched off, the ICMP error message would be "Request Timed Out". "Destination Host Unreachable" is clearly indicating that your computer does not have the information needed to reach the next hop. The fact that the 10.39.4.60 host does not have an entry in your ARP cache is a problem. Without the host's MAC information, it is not possible to deliver packets to that system. It is possible that the 10.39.4.60 is having network issues (cable, switch port, driver, etc...) Visit: anITKB.com, an IT Knowledge Base.

Thanks for the help so far. I am now going to wait till I can physically have a look at the system and see what is going on. The site is closed until 23rd August and I will update this when I have more info.

OK, we will wait for you.