Can't connect to server via console

[guest]

It says it can't find the server.

However I can access my shares just fine from any computer and OS on my network. I can run backups. Even start the backup from the connector tray icon.
The console on ther server itself does recognize when computers are connected and powered on.

I can successfully ping the server too.

The console icon continues to provide the server health status.

This did work on this computer running Vista x64 and then it stopped. I am now running Windows 7 x64. My HTPC is running Windows 7 32bit.
And yesterday I just bought a laptop running Vista 32bit and I installed the connector software on there directly from the server and the console won't connect from there either.

I did notice that I couldn't connect via the website so I uncofigured the router in the settings in the console and then had it configure it again and that fixed that issue. But I still can't connect via the console.

My desktop and the server are connected to the same router. My laptop connects to another router on my network that I setup as an access point.

My server has it's own monitor, keyboard and mouse. But I will be pulling them soon to use with another computer build.

[guest]

Try switching back to the DNS servers provided by Comcast. OpenDNS does some non-standard things with DNS lookups which result in exactly the symptoms you describe.


If switching back to the Comcast DNS servers corrects the issue, you can try asking OpenDNS for assistance with their systems. I suggested about 18 months ago that they should write up some FAQ articles describing how to configure OpenDNS and Windows Home Server to work peacefully together; I don't see anything in their support area so I presume they haven't done so.


Workarounds include adding an entry to the HOSTS file on each home computer that's joined to your server to allow them to find the server without a DNS lookup. This will work for backups and single file restore, but a bare metal restore (using the Restore CD) will probably require you to "turn off" OpenDNS temporarily.

[guest]

Yes, it was openDNS causing the issue. I edited the HOSTS file and it solved the problem. Thanks!