Saturday, February 24, 2007 10:05 PM
From each of my home computers I can see the shared drives, backup files automatically on each computer and copy files into the shared directories.
However, when I right click on the WHS taskbar icon and click on the Windows Home Server Console option I get the password prompt box, from any of the home computers, but when I enter the password I get:
"This computer cannot connecto to your home server. Check your network connection and make sure your home server is powered on. If your home server has recently restarted, try again in a few minutes."
Anyone have any thoughts on this? The icon is green and says that my server is healthy. I have run the Connect CD a couple of times and all goes well. The server is running fine and reports a healthy status, all 5 HD's drives are healthy. All of the computers and the WHS are in the same workgroup. I have rebooted the WHS but this does not seem to remedy the problem.
Thanks in advance,
Sunday, February 25, 2007 12:14 AMModerator
1. Is this a Vista machine? There is a known issue of Vista machines unable to connect.
2. Do you have a firewall ON? Do you run OneCare?
Sunday, February 25, 2007 1:12 AM
This is not a Vista Machine it is an XP Pro. All machines are XP Pro
I have a firewall which is a CISCO PIX 501.
I am using OneCare, on all machines, but it has on its firewall set to allow Microsoft Home Server
Sunday, February 25, 2007 1:49 AM
I have 2 Vista Ultimate systems on the Home Server setup right now... The wired is 64 bit so unable to have it on the home server console but it can access the home server in all other methods fine. The wireless system has no problems at all connecting to the home server console..
Sunday, February 25, 2007 5:03 PM
There is a long known about bug in OneCare that can cause networking problems when the firewall is set to share files and folders "only with computers on the local network(subnet)". The workaround is to change the setting to "share with all computers, even those on the internet". Usually when this bug rears it's ugly head, it blocks all network access, but it can be intermittent and unpredictable. Give it a try. This bug is well known in the OneCare beta community, and I have submitted a suggestion with the WHS team to try to help solve this issue.
Monday, February 26, 2007 11:48 PMModeratorYou will have to allow port 1138 and 8912 for the console and backups to work correctly. OneCare blocks these ports.
Tuesday, February 27, 2007 6:10 AMPlease get TALQ report on the client and send the CAB number (see usual bug reporting hints).
Tuesday, February 27, 2007 8:07 PM
I had the same problem, but found i had setup several ip ranges on my xp pc. Setting it to just one fixed my problem.
Thursday, March 08, 2007 1:16 AMModeratorI revised my ports that need to be unblocked by your home computers firewall in my earlier post in this thread. :-)
Thursday, March 08, 2007 8:41 PMI too am suffering from this problem. 2 Vista Ultimate machines, 1 XP pro, and 1 XP home machine cannot connect to the server using WHS - I can access the files on the server, but not Console access.
This problem goes back to when I had to shut down and restart to install a new HD. I haven't been able to access since - I had to connect the system to a monitor, keyboard and mouse to add the hard drive.
All of the the ports I can think of on my router are pointed to the server - 443, 4125, 80, 1139, and 8192 - I realize that some of this is not appropriate, but I'm trying to troubleshoot.
Tuesday, March 20, 2007 5:12 AM
I'm pretty much in the same boat. Just installed WHS on a new machine. Trying to run WHS Console from a XP Pro SP2 machine. I can see and browse the WHS box from My Network Places, but WHS Console won't connect. When I run Discovery.com, it freezes after I put in the WHS password. Indeed, it freezes so hard that I have to use Task Manager to kill a bunch of processes before the XP Pro machine will re-boot. I'm running Windows Live OneCare, but have the firewall turned off.
Tuesday, March 20, 2007 10:37 AM
Same here, 2 of our 3 PC's XPPro can see the shares, run backups, connect to the WHS console, the 3rd a laptop with XP Home can access the WHS shares but cannot connect to the WHS console, tried wireless, wired, no firewall, cd whs console install, WHS share console install, changed username on Laptop, and WHS, tried new users on laptop and WHS still it will not connect to the WHS server to run the console. Can ping the TCP/ip address and netbios name of the server and all other devices on the lan.
Whats so special different about this one device a Laptop, frustrating, and run out of ideas.
Anyone got any series of activities or tasks that seemed to work when all else failed ?
Saturday, March 24, 2007 8:02 PMI've got the exact same problem here. Can browse shared folders on server, can run backups, etc. Cannot connect to server console from any machine (XP or Vista), and cannot Remote Desktop into the server. I had no problem doing any of these things a couple hours ago, but it just started. I've rebooted all the machines and have been troubleshooting, but no luck.
Saturday, March 24, 2007 9:52 PM
The only way that I know how to resolve this problem is to reboot.
Saturday, March 24, 2007 11:21 PM
bander88 wrote: I've got the exact same problem here. Can browse shared folders on server, can run backups, etc. Cannot connect to server console from any machine (XP or Vista), and cannot Remote Desktop into the server. I had no problem doing any of these things a couple hours ago, but it just started. I've rebooted all the machines and have been troubleshooting, but no luck.
I'll chime in with another vote on this. Early this morning, I suddenly got a warning concerning the expiration of WHS and that it needed to be activated. It has already been activiated some time ago and I have received this warning a couple of times over the past couple of weeks with no effect on operations.
When I logged on this afternoon, I cannot access the WHS Desktop via any machine nor can I Remote into the desktop. Times out and claims no contact. Yet the access to shared folders and normal operations (save, open files, etc.) seem OK.
Is the advice to reboot the WHS server or the client machine?
Saturday, March 24, 2007 11:48 PM
I had the same problem, fixed it by adding the server to the hosts file in
edit hosts file
add ipaddress of server followed by name of server