locked
Remote Access to WHS Console - Time out. RRS feed

  • Question

  • I never had problems with this issue before, but suddenly it appears on every home server where i am trying to connect to.

    I connect to the home server without any problems. Then I jump to Computers, Remote Acces to Windows Hme Server Console and then click Connect to your Home server.

    First my browser pops up this message:

    Remote desktop Connection
    A website wants to start a remote connection. The publisher of this remote connection cannot be identified.
    Publisher: Unknown publisher
    Type: Remote Desktop Connection
    Remote computer: xxxxxx.homeserver.com

    After selecting connect I get this message:
    The remote connection to the computer timed out. Please connect again.

    I have checked this both from a vista and a xp client both fully updated running IE 7.

    Any help willl be much appreciated
    Wednesday, December 17, 2008 12:39 AM

Answers

  • Hi Olaf,

    Thanks your quick response.
    http://server works OK and I now opened port 4125 and every thing works 100%
    Thank you very much indeed.

    /morten 
    • Marked as answer by MortenBrun Wednesday, December 17, 2008 3:47 PM
    Wednesday, December 17, 2008 3:46 PM

All replies

  • Hi,
    this often happens, if a corporate firewall on the client location is blocking the port needed for the communication (4125).
    Did you add your homeserver.com domain to Trusted Sites in Internet Explorer?
    Best greetings from Germany
    Olaf
    Wednesday, December 17, 2008 8:35 AM
    Moderator
  • Hi Olaf

    Yes this is already done.
    There must have been some changes with the lately MS patches as no change this end. And it appears on 2 different home servers.

    /morten
    Wednesday, December 17, 2008 2:46 PM
  • Hi Morten,
    the server site is usually not the reason, a blocked port 4125 on client site, corporate firewall (you didn't tell, from which locations you tried), or ISP blocking (or port forwarding in the router configuration wrong) are the more known reasons.

    Maybe you can try from within your network to open
    http://server
    on one client (replace server with the NetBIOS name of your WHS) and see, if the function is working via internal access.
    I just tested the one machine, which is still reachable via homeserver.com and can still connect fine to the server via Remote Access website.
    Best greetings from Germany
    Olaf
    Wednesday, December 17, 2008 3:29 PM
    Moderator
  • Hi Olaf,

    Thanks your quick response.
    http://server works OK and I now opened port 4125 and every thing works 100%
    Thank you very much indeed.

    /morten 
    • Marked as answer by MortenBrun Wednesday, December 17, 2008 3:47 PM
    Wednesday, December 17, 2008 3:46 PM
  • Olaf Engelke said:

    Hi Morten,
    the server site is usually not the reason, a blocked port 4125 on client site, corporate firewall (you didn't tell, from which locations you tried), or ISP blocking (or port forwarding in the router configuration wrong) are the more known reasons.

    Maybe you can try from within your network to open
    http://server
    on one client (replace server with the NetBIOS name of your WHS) and see, if the function is working via internal access.
    I just tested the one machine, which is still reachable via homeserver.com and can still connect fine to the server via Remote Access website.
    Best greetings from Germany
    Olaf



    Hello Olaf,

    I seem to be having the same problem as Morten, but I don't fully understand your suggested solution.

    When I access my server from my work, I have to type https://******.homeserver.com in order for it to work.  If I type http://******.homeserver.com I get an error message.

    Once I've access my site, I can download pictures and I can access my shared folder, etc.  The only problem is that I cannot access any of the client PCs, nor can I access the server.

    SilkRod
    Thursday, December 18, 2008 10:27 AM
  • Hi,
    http = port 80, https = port 443 and Remote Desktop Proxy = port 4125. If these 3 ports are configured properly on your side (Windows Firewall allows on the server, which is the default for WHS and port forwarding in the router is configured properly for these 3 ports), I can only imagine, that your ISP is blocking server services via port 80.
    In relation to port 4125 both your ISP or settings of the corporate firewall in the place, from where you try to reach the server, may be the reason.
    Best greetings from Germany
    Olaf
    Thursday, December 18, 2008 11:31 AM
    Moderator