Can't get Clients to Connect to WHS
-
Monday, September 24, 2007 7:56 PM
Just finished my 6th Server Reinstallation and everything seems to be setup on the WHS. But, I can't get the clients to connect. Tried three of them ad get the same error message:
"An unknown network error has occurred"
I have rebooted the WHS several times and still get this message. Anything else I need ti know/do?
Ted
Answers
-
Wednesday, September 26, 2007 2:21 PM
Well, although the network here is running on two gigabit hubs/switches, the router is provided by Verizon for their FIOS Internet service (Mi424WR). Can't do anything about that. Maybe MS should work with the large internet providers to make sure they are compantible? Tha routers listed in the hardware compatibility list are probably a very small representative sample of what folks have in their homes. And setting up a router for Port Forwarding and Static NAT is not easy. I am not a computer guru, just a financial planner! But, I do mess with this stuff all of the time just to keep the network in my office and home running 90% of the time! Couldn't have kept WHS running for the past 3 months without this forum for which I am very appreciative. And since 4 of my 8 home computers are running Vista Media Center, that could never had happened without The Green Button Forum!
Thanks again.
Ted
All Replies
-
Monday, September 24, 2007 8:28 PMHave any of them connected successfully? Have you reinstalled the connector on the clients?
-
Monday, September 24, 2007 8:36 PMModerator
This error could occur because of several reasons.
-
an unsupported router or a router that needs a firmware update
-
time clocks could be off on the Windows Home Server and/or clients
-
netBIOS is not enabled on the clients
-
other various networking issues
-
-
Monday, September 24, 2007 9:39 PM
"Other various networking issues" !!! Yep, that ,must be it!
I restored the router to its defaults and reset the Port Forwarding settings for WHS. Now, I can RDP into WHS fine (couldn't before after the reinstall) and can see the WHS web site on homeserver.com. Tried Connector from this client again...no luck. Same error. No clients will connect. And, yes, they have been connected for three months now, except when it has crashed (5 times). Bout to run out of keys if I have to do this again!
OK, used the Home Connector setup.exe that was in the Addins folder on the WHS across the network...and, it worked. I'll try the other 8 clients now. Thanks!
-
Monday, September 24, 2007 10:34 PM
I had this issue, and the same workaround (install connector over network) solved it for me too. It's such a simple workaround, but it took me a very long time to find it. Most google queries resulted in technical suggestions like changing the "hosts" file and things like that. This seems to be a common error. Should probably be in the FAQ, if it isn't already.
Aaron
-
Tuesday, September 25, 2007 1:13 PMYou're right. It ought to be in the FAQ. Got all 8 clients reconnected using the network. Oh well, Just hope it stays up for awhile now. Maybe RTM has fixed these issues???
-
Tuesday, September 25, 2007 5:50 PM
The aletrnative, is to just run the program 'Discovery.exe' from the WHS folder on the client. That will re-connect your existing clients' Connector software to the re-installation.
Colin
-
Tuesday, September 25, 2007 10:19 PMModerator
TMG01 wrote: "Other various networking issues" !!! Yep, that ,must be it!
I restored the router to its defaults and reset the Port Forwarding settings for WHS. Now, I can RDP into WHS fine (couldn't before after the reinstall) and can see the WHS web site on homeserver.com. Tried Connector from this client again...no luck. Same error. No clients will connect. And, yes, they have been connected for three months now, except when it has crashed (5 times). Bout to run out of keys if I have to do this again!
OK, used the Home Connector setup.exe that was in the Addins folder on the WHS across the network...and, it worked. I'll try the other 8 clients now. Thanks!
Because of the way most home networks are setup, your home network relies heavily on your home router. Since you were able to install after browsing for the home server and installing the connector that way, I can only assume your computer just needed the correct netBIOS information.
During many demo events and testing, I've had several different routers. I've gotten 8 or so of the same name brand, model and firmware but only 2 out of the 8 worked correctly. Now I only purchase "Works with Vista" or "Certified for Vista" routers and they all work 100% of the time.
It's nice to know browsing for the Server path helped this process along and serves as a work around.
-
Tuesday, September 25, 2007 10:46 PMModerator
Here's the link to the router compatibility page.
-
Wednesday, September 26, 2007 2:21 PM
Well, although the network here is running on two gigabit hubs/switches, the router is provided by Verizon for their FIOS Internet service (Mi424WR). Can't do anything about that. Maybe MS should work with the large internet providers to make sure they are compantible? Tha routers listed in the hardware compatibility list are probably a very small representative sample of what folks have in their homes. And setting up a router for Port Forwarding and Static NAT is not easy. I am not a computer guru, just a financial planner! But, I do mess with this stuff all of the time just to keep the network in my office and home running 90% of the time! Couldn't have kept WHS running for the past 3 months without this forum for which I am very appreciative. And since 4 of my 8 home computers are running Vista Media Center, that could never had happened without The Green Button Forum!
Thanks again.
Ted