Asked by:
Connector Problems

Question
-
I've tried all the troubleshooting steps in connector manual. I've re-installed server and connector software. I've (I think) properly configured my apple airport extreme router (port forwarding). I've verified my firewall settings. I've pulled my hair out.
The problem is--I can't seem to connect to my home server with the connector--though all the folders, etc. are accessible. It shows the progress bar moving across, and then it just ends up being a blue screen (just like login screen without login window).
I did an advanced trouble shooter session--and it reported the following:
[3]100611.105618.5794: Network: =========================================================
[3]100611.105618.5794: Network: =========================================================
[3]100611.105618.5794: Network: Test Check EnrollId 55000 - id.aspx begin.
[12]100611.105618.5804: Network: Server name is : BOGEY
[12]100611.105618.5804: Network: URL formed: http://XXXX:55000/enrollid/id.aspx
[12]100611.105618.5804: Network: Looking for proxy information...
[12]100611.105618.5804: Network: Proxy Enabled: False
[12]100611.105618.5804: Network: Getting Response...
[3]100611.105630.5804: Network: Test Check EnrollId 55000 - id.aspx end.
[3]100611.105630.5804: Network: Information for test Check EnrollId 55000 - id.aspx:
Test Timed Out.
[3]100611.105630.5804: Network: =========================================================
[3]100611.105630.5804: Network: =========================================================
[3]100611.105630.5804: Network: Test Check EnrollId 55000 by IP - id.aspx begin.
[11]100611.105630.5804: Network: Getting ip from test ResolveName
[11]100611.105630.5804: Network: Server name is : 192.168.1.5
[11]100611.105630.5804: Network: URL formed: http://xxx.xxx.x.x:55000/enrollid/id.aspx
[11]100611.105630.5804: Network: Looking for proxy information...
[11]100611.105630.5804: Network: Proxy Enabled: False
[11]100611.105630.5804: Network: Getting Response...
[12]100611.105630.6064: Error: Thread was being aborted.
[3]100611.105642.5804: Network: Test Check EnrollId 55000 by IP - id.aspx end.
[3]100611.105642.5804: Network: Information for test Check EnrollId 55000 by IP - id.aspx:
Test Timed Out.
[3]100611.105642.5804: Network: =========================================================
[3]100611.105642.5804: Network: =========================================================
[3]100611.105642.5804: Network: Test Check Enroll 56000 - id.xml begin.
[5]100611.105642.5804: Network: Server name is : BOGEY
[5]100611.105642.5804: Network: URL formed: https://xxxxx:56000/enroll/id.xml
[5]100611.105642.5804: Network: Looking for proxy information...
[5]100611.105642.5804: Network: Proxy Enabled: False
[5]100611.105642.5804: Network: Getting Response...
[11]100611.105642.6024: Error: Thread was being aborted.
[5]100611.105654.5904: Error: Thread was being aborted.
[3]100611.105654.6004: Network: Test Check Enroll 56000 - id.xml end.
[3]100611.105654.6004: Network: Information for test Check Enroll 56000 - id.xml:
Test Timed Out.
[3]100611.105654.6004: Network: =========================================================
[3]100611.105654.6004: Network: =========================================================
[3]100611.105654.6004: Network: Test Check EnrollId 56000 - id.xml begin.
[10]100611.105654.6004: Network: Server name is : BOGEY
[10]100611.105654.6004: Network: URL formed: https://xxxxx:56000/enrollid/id.xml
[10]100611.105654.6004: Network: Looking for proxy information...
[10]100611.105654.6004: Network: Proxy Enabled: False
[10]100611.105654.6004: Network: Getting Response...
[10]100611.105654.6054: Network: Succeed.
[10]100611.105654.6194: Network: Native client30 called
[10]100611.105655.2294: Network: Native server30 called
[10]100611.105655.2344: Network: Native server60 called
[10]100611.105655.2344: Network: Checking response with <ID>1</ID>...
[3]100611.105655.2344: Network: Test Check EnrollId 56000 - id.xml end.
[3]100611.105655.2344: Network: Information for test Check EnrollId 56000 - id.xml:
<ID>1</ID>- Edited by brandtryan Friday, June 11, 2010 3:14 PM edit server name
Friday, June 11, 2010 3:13 PM
All replies
-
Hi,
the connector has nothing to do with port forwarding.
What kind of home server do you have - a self built or an OEM model?
If you use the Remote Desktop client from a PC, can you access your Home Server desktop then?
Can you start the console directly from the server desktop?Please check the FAQ How to handle error message “The Password is incorrect” attempting console access (especially if the server is self built and has a NVidia graphics card) and How to Troubleshoot Network Connection Problems with Windows Home Server, if one of the mentioned issues could be the cause.
If you cannot figure out any network configuration issues or other reasons, please post the output of the command ipconfig /all from the server and one client here.
Best greetings from Germany
OlafFriday, June 11, 2010 9:02 PMModerator