Blah

Apparently, the file server here in the house downloaded and installed an update from MS sometime recently and rebooted. Sometimes, it'll respond to pings when I ping by IP address and sometimes when I ping by its name. Unfortunately, pinging by name brings up an IP address nowhere near correct (192.168.175.1 vs. 192.168.1.75 (the correct IP)). Remote Desktop doesn't want to connect to it. Rebooting doesn't help at all. I'm hoping it's not totally hosed. I'll have to find a monitor, keyboard, and mouse for it tomorrow and check it then. Luckily, all the important data is on seperate drives from the OS/applications.

Any ideas on how to get the bastard to respond to Remote Desktop without going through all the hassle of pulling it out, relocating it, and connecting a monitor, keyboard, and mouse to it? It's running Windows Server 2003.

If it is hosed, I may switch the main OS to CentOS and run Server 2003 in a VM.