Microsoft > Forums Home > Windows Home Server Forums > Windows Home Server Software > WHS RC remote access won't let me in
Ask a questionAsk a question
 

Proposed AnswerWHS RC remote access won't let me in

  • Sunday, October 14, 2007 1:36 AMKelly42 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I'm having a problem authenticating into my WHS using remote access.  Unlike a previous poster, I don't run a domain (and am not violating the WHS license).  I'm still running the RC version.

    I have enabled my user account for remote access.  I've forwarded ports 80, 443, and 4125 on my router to the WHS IP.  Interestingly, I had to change the port for my router's web interface, because I found myself at this web interface when I tried to access my livenode.com domain name.  Anyway, I'm now testing the remote access by browsing to the WHS IP from within my home network.  I reach the WHS login page and enter my account information, but then I get the error that "The logon name or password is incorrect. Please retype the logon name and password."

    I've checked my username and password about a million times, and I've successfully used them from the same computer to map the WHS shares.  It's not my credentials, as far as I can tell.  I don't need to input my username as "SERVER\user", right?  Just "user"?

    I also have a hopefully-unrelated problem with port 4125: I've forwarded it, and I can confirm that in my router setup, but I can't "see 4125 as "open" from web-based port scanners.  80 and 443 are reported as "open" with no problems.

    I'd really appreciate any help with getting remote access to work.  Thanks!!

All Replies

  • Sunday, October 14, 2007 8:27 AMAndrew EdneyMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Have you tried having a look through the Remote Access document that MS have published as its very useful for troubleshooting? You can download it here: http://www.microsoft.com/downloads/details.aspx?FamilyID=8505e3a8-bbbc-445d-ba65-13782661dcb0&DisplayLang=en

     

    To answer your question about username, yes, its just the username for your account you are using for WHS (not the WHS admin account).


    Andrew

  • Tuesday, October 23, 2007 7:21 AMKelly42 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks, Andrew, for your reply.  I've sorted out my password problem (though its origin still flummoxes me).

    I can connect to my server's webpage remotely, but I can't use Remote Access.  I get onto the Remote Access connection screen, and then I get the following message:

    "The remote connection to the computer timed out.  Please connect again."

    I have read the Technical Brief for WHS Remote Access, and I've followed the troubleshooting instructions.  I can't figure out why I'm not able to get Remote Access to connect.  Perhaps it's from my perhaps-unrelated problem with port 4125, as above:

    I also have a hopefully-unrelated problem with port 4125: I've forwarded it, and I can confirm that in my router setup, but I can't "see 4125 as "open" from web-based port scanners.  80 and 443 are reported as "open" with no problems.

    Any ideas?  Thanks for your time!
  • Tuesday, October 23, 2007 8:08 AMbrubberMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    1. Port 4125 is essential for remote access. Make sure it's routed to the correct IP address (the one from your WHS box).  If this is OK there is obviously something (windows or router firewall?) blocking this port.

    2. You have to use IE(7) browser (unless you want to spend some time configuring other browsers to run ActiveX)

    3. Your website should be added to trusted zones in IE

    4. IE security settings should allow you to download and install the necessary ActiveX Add-Inn

     

  • Wednesday, October 24, 2007 12:27 AMkariya21MVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
     Kelly42 wrote:
    Thanks, Andrew, for your reply.  I've sorted out my password problem (though its origin still flummoxes me).

    I can connect to my server's webpage remotely, but I can't use Remote Access.  I get onto the Remote Access connection screen, and then I get the following message:

    "The remote connection to the computer timed out.  Please connect again."

    I have read the Technical Brief for WHS Remote Access, and I've followed the troubleshooting instructions.  I can't figure out why I'm not able to get Remote Access to connect.  Perhaps it's from my perhaps-unrelated problem with port 4125, as above:

    I also have a hopefully-unrelated problem with port 4125: I've forwarded it, and I can confirm that in my router setup, but I can't "see 4125 as "open" from web-based port scanners.  80 and 443 are reported as "open" with no problems.


    Any ideas?  Thanks for your time!

     

    If you're sure everything else is set up correctly, I would guess your ISP is blocking that port.

  • Thursday, October 22, 2009 3:40 PMJosh Van Den Wildenberg, MCP Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer

    What are the operating systems of the computer you are trying to remote to?
    Do you see the green light next to the name?
    Try this post too : http://social.microsoft.com/forums/en-US/whssoftware/thread/ee2189d3-70e3-4743-bb11-502102271d45
    I also had an issue with one client.

    Josh


    Josh Van Den Wildenberg, MCP IT Continuity LLP
  • Monday, November 02, 2009 3:25 AMAdam HerscherModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Lots of great suggestions in this thread.  Two more bits of information:

    1. It's normal that port 4125 doesn't show up as "open" from web-based port scanners in the same way that 80 and 443 do.  This is because, for added security, your home server doesn't actually open port 4125 until you click to connect to a computer through the remote access web site.

    2. I've often seen this error from customers who are connecting from corporate/business networks where there are IT firewalls in place that do not allow for TCP connections on port 4125.  If you're trying to connect from work, you may want to check with someone in your IT department.