2

Here is the thing, I had made a stupid mistake yesterday. I run "route /f" on a remote machine with Windows Server 2008, and this command cleared the routing tables, including the default route, which is fatal.

Since no one is working on the remote side now, I could not restart the machine. This stupid mistake makes me could not reach the machine thought remote desktop, I have tried to access the machine on another machine (in the same LAN with the broken remote machine), but it did not work.

Is there any way I can get the default route back, so that I could access the remote machine by remote desktop again? Any advice is appreciated! Thank you very much!

huubby
  • 121
  • 1
  • +1 - Interesting situation. If you were on the same LAN segment, it should not have mattered if there was no default route... there must be something larger going on... – Mark Henderson Jan 30 '12 at 02:06
  • @Mark Henderson I tried to ping the broken machine, and I got the arp cache updated with the valid physical address, so I think the machine is still alive – huubby Jan 30 '12 at 02:21
  • http://serverfault.com/questions/352712/how-to-remotely-reboot-a-hung-server – Nic Feb 04 '12 at 21:25

1 Answers1

0

In general, even without the default route the host is still able to communicate within its own broadcast domain. If the Windows Firewall is up, it is quite likely ICMP echoes are filtered, so you would not get responses to ping.

Just try RDP'ing in from the same network. If it fails for some reason (filtered, broken, whatever), check if you still can access the machine via SMB like typing \\server or \\192.168.0.12 (exchange for your server's IP address) into the Explorer address bar. If this turns out to work, try either using psexec \\server cmd (psexec is an optional download) for establishing a remote shell for further debugging or getting to schedule a task remotely which would run a batch for the same purpose.

the-wabbit
  • 40,319
  • 13
  • 105
  • 169