Team is asking for your help - WHS Connector Join issues
Our team is trying to create a comprehensive picture of the issues people have when running connector on their client machines and joining server. Because of wide range of configurations of networks we will never be able to create many of these scenarios in the lab.
If you have experienced an issue with joining your clients please:
- send email to home-server@hotmail.com
- we will establish direct contact and try to figure out what your problem is and try to fix it.
Your help is very much appreciated!
All Replies
- I know this is an old issue, but I encountered it this afternoon. (7-2-2007) My e-mail is clrasmus< at >gmail.com. Thanks..... I love to submit a bug report with "cabs" but thats a little beyond what I can do....
Chuck.
To create and submit the TALQ logs, please follow the following steps on both the server and your client machines:
- Click on Start
- Click on Run
- Type "C:\Program Files\Windows Home Server\TALQ.exe"
- Press Enter
- Enter your Connect handle (Same as your forums username, Chuck Rasmus
][) when prompted - If a Windows Error Reporting message appears, click submit to Microsoft
- Record CAB Number
- Post in forum with description of problem, setup, and cab number
Also, just send an email to the address given, probably headed 'WHS Connector Issues' and they will get back to you.
Colin
Hey I just installed WHS the other day on my new server computer. Everything went very smothly untill i tryed to install the connector on my Client computer. I got to the sceen that says please enter your password and i did. Then it said unable to connect to the windows home server. I have tried the host file workaround, but i really dont feel like going around to all my computers and doing that. I have been reading around on the board and read a article on MSDN but nothing has seem to actualy fix the problem. Im pretty sure it has somthing to do with my router but i could be wrong. It is a brand new Lynksys G router, and i updated the firmwear just yesterday. When i try to do remote desktop connection and type in "SERVER" it says it cannont find it. But when i turn in the ip address then it works fine. Does anyone know how to fix this.
My CAB# 355907652
Setup: 3 Client computers, 1 WHS, 1 router, Have only tried installing the connector softwear on one of the client computers which is running windows XP Pro SP2.
Hi Eibach, I just logged in locally to check the full computer name of my "Windows Home Server", I don't remember if I changed it or not, but the full computer name of it is, "winhomeserver". I did a remote desktop to it by it's ip, and the server name from Win xp pro, no problems getting to it, either way, before I installed the connector CD on this computer. Since you can get to it by ip, is the name "server" the full computer name of your WHS?. Also, if you login though the actual Home server console, does that work? I just installed the connector cd after I saw you post, and I logged into the Home server console ok also. I would think that since you can get it to by ip, (us old net guys usually do it that way anyway, force of habit I guess), I don't think it is a network, or router problem, because you can get to it. I did notice on another XP computer, it and WHS were having a duel over the password, but that did get resolved by letting the password keep on the whs, not keeping it on the XP computer. I have the connector cd installed on 2 xp computers, and one vista computer. No problems getting to the server from any of them, either by the console login, or by the shared folders shortcut. Try a login locally, check the name, log out locally, and try using the full computer name again, on the client computer. If that still fails, uninstall / reinstall the connector, might work the second time around. Sorry for the long post, but I hope it helps. Somtimes I do babble too much
.Cheers, Kevin
- Hey Kevin, dont worry about the long post. I need as much help as i can get im new at all this =P. Anyway i have tried to uninstall it a couple times and still it has failed. the only way i can seem to get around it is by changeing my HOST file in the windows/system32/drivers/ect/host directory. so if you have any other sugestions that would be great lol. But thank you so much for your help before =P
- I was also having the same issues when using the home connector software. It worked at first when I was using the beta version but when I updated to the RC version the connector software stopped working. Due to some various other reasons I had to reformat my XP machine and now the connector software works.
- Hi Eibach, are the 2 services that the connector software installs, running? WHSConnector.exe, and WHSTrayApp.exe ? Also, take a look at the event logs on both the server and the client to see if there are any errors listed. After the connector software installed, did the WHS add it, or did this fail because they wouldn't talk to each other? Adding an entry to the hosts file will work, but the WHS and the client should engage in a "browser war" after the connector software is installed. The WHS should take over as the master browser, it is based off of server 2003, and it should keep the list of computers in it. Also, any type of security software, like a personal firewall, a program that locks the hosts file, etc., should be disabled untill after the connector software is installed. Let me know if you find any errors in the logs or not. Usually the computers talk more on the network than the people using them do, lol. Kevin.
- What the whs team is saying is something I discovered. To install the connector after the rc install you must uninstall your personal firewall and also disable windows firewall. This was always the case when running windows onecare. I was able to install with zone alarm disable as well as sunbelt. It seems even with exceptions set you still must disable your firewalls. After doing this I have always been able to install the connector. Restoring a backup however is a whole other issue...
Chuck.
To create and submit the TALQ logs, please follow the following steps on both the server and your client machines:
- Click on Start
- Click on Run
- Type "C:\Program Files\Windows Home Server\TALQ.exe"
- Press Enter
- Enter your Connect handle (Same as your forums username, Chuck Rasmus
][) when prompted - If a Windows Error Reporting message appears, click submit to Microsoft
- Record CAB Number
- Post in forum with description of problem, setup, and cab number
Also, just send an email to the address given, probably headed 'WHS Connector Issues' and they will get back to you.
Colin
Sorry to hijack your response but after I complete step 6 above, I get no CAB#, just a thank you and a close button. Where should this CAB# be indicated? I am running this on my server machine, not the clients.
Thanks.
- I have found that my personal firewall, (Zone Alarm Pro), didn't have to be disabled, but I had to allow the connector software to access the trusted zone that I put the WHS in. As for the windows firewall, and this is in XP, ZA will automatically disable it, but it does get an exception for the connector software put in it. I have no troubles with the connector software, except for the password duel, after I reboot the first time after the connector install, in XP. Although making the password changes should happen "NOW", it takes a little bit of time for the client and the WHS to shake hands again with the new credentials. In Vista, and with ZA Security suite installed, add the whs to my trusted zone, let the connector software access the trused zone, but no password war in Vista. Taking down the firewalls, would be the first logical step if the client and server won't talk to each other. Depending on how you set up your home network, and firewalls on the clients, if you are a little taken back as to how the outbound and inbound filtering, rules, etc. work with firewalls, then most defenatly disable all, then renable creating exceptions, or the rules that you need to you don't block each other from talking. Sorry for the long post. I do babble way to much, lol
I am still having this problem i was wondering if anyone had figured out the reason that this is happening???? please help!!!
thanks
- I am currently having a constant problem.
New installation of whs (4th time now)
When I install the connector software on client computers it finds the server but cannot join.
I get an error message saying the computers firewall may be blocking (it isn't)
There may be a proxy (if there is it is on two different makes of computer) - Britishbob said:
I am currently having a constant problem.
New installation of whs (4th time now)
When I install the connector software on client computers it finds the server but cannot join.
I get an error message saying the computers firewall may be blocking (it isn't)
There may be a proxy (if there is it is on two different makes of computer)
I would suggest you start your own thread and give as many details as possible (instead of adding to a thread from 18 months, one Power Pack and numerous updates ago ;) ). You might also want to provide the results of ipconfig /all from your client and your server.
