Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Remote Access Issues RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    On the Vail Beta, the remote access keeps dropping at random times.  The webpage will disappear, and then in the general settings, remote access will not be available because the router is not configured.  I'll click the repair button and the issue is repaired and the site is back.  10 to 15 minutes later, the site is down again and the router is no longer configured.

    I have manually added port forwarding rules to the router forwarding HTTP/80, HTTPS/443 to the Vail server, but the issue continues. 

    With WHS v1, these port forwarding rules were all that was needed.

    Router is a DLink DIR-655 with latest firmware.

    Any ideas anyone?

    Tuesday, April 27, 2010 9:50 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    Correct.
     
    Technically you ONLY need port 443 for total functionality, minus the redirection from http://blah.homeserver.com to https://blah.homeserver.com.  So if you want to be ULTRA secure, turn off UPnP on your router, and only forward port 443.  then make sure you type in the https://, if you don’t, you’ll get a 404 not found.
     
    4125 was used in the legacy Remote Desktop Proxy, and is only needed in WHS v1 and SBS 2003.
     
    Cheers,
       Sean
     
    This post is "AS IS" and confers no rights.
     
    "Ken Warren" wrote in message news:1d6bfe79-4e59-49b1-aaf9-f37b754bc1cc...
    No, per Microsoft in another thread, Vail uses the built-in Terminal Services Gateway, and therefore shouldn't need port 4125.
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, May 5, 2010 1:07 AM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Did you set up the DHCP reservation for your home server so it constantly gets the correct IP?
     
    Who is your ISP? are you sure they aren’t dropping packets? what other Internet bound applications are running on your network?
     
    Sean
     
    This post is "AS IS" and confers no rights.
     
    "Noonien Soong" wrote in message news:2a6e0a1b-d345-4670-9818-64aaad1d3503...

    On the Vail Beta, the remote access keeps dropping at random times.  The webpage will disappear, and then in the general settings, remote access will not be available because the router is not configured.  I'll click the repair button and the issue is repaired and the site is back.  10 to 15 minutes later, the site is down again and the router is no longer configured.

    I have manually added port forwarding rules to the router forwarding HTTP/80, HTTPS/443 to the Vail server, but the issue continues.

    With WHS v1, these port forwarding rules were all that was needed.

    Router is a DLink DIR-655 with latest firmware.

    Any ideas anyone?

    Tuesday, April 27, 2010 10:59 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the reply.

    Vail has a static IP address, so no DHCP and router is configured using the static IP.

    ISP is comcast and they've been fine with WHS v1, was just when I started using Vail that it started acting up.  I also work from home via a seperate system that connects via a VPN, so if the ISP was dropping packets, I would notice, but the connection has been smooth all day.

    I do still have my WHS v1 system online, but before I started the Vail install, I reconfigured the v1 site to use HTTP/8080 and HTTPS/444 and updated the port forwarding in the router to match.

    Tuesday, April 27, 2010 11:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    That old WHS v1 might be the problem, If you’re router supports UPnP, it’s going to try every 10 minutes (or so) to redirect port 80 and 443 to itself, even if you said to use the other port.  Can you turn off remote access on your WHS v1 box and let us know what happens then?
     
    Sean
     
    This post is "AS IS" and confers no rights.
     
    "Noonien Soong" wrote in message news:ad3b9626-d857-4a62-83b2-d299cf886f86...

    Thanks for the reply.

    Vail has a static IP address, so no DHCP and router is configured using the static IP.

    ISP is comcast and they've been fine with WHS v1, was just when I started using Vail that it started acting up.  I also work from home via a seperate system that connects via a VPN, so if the ISP was dropping packets, I would notice, but the connection has been smooth all day.

    I do still have my WHS v1 system online, but before I started the Vail install, I reconfigured the v1 site to use HTTP/8080 and HTTPS/444 and updated the port forwarding in the router to match.

    Wednesday, April 28, 2010 3:39 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    I had this same issue, but did have remote access on my WHS v1 turned off.  What would happen is I could bring up the v2 web page and log in no issue.  Upon clicking on "connect" for my WHS v2 server, I would get the login screen for the remote session, after that I would get a message that Dashboard was going to be run and needed the password for the Administrator account to allow it.  I would enter the password and the remote session would begin with the Dashboard in a window.  After about 10 to 30 seconds the whole window would disappear yet I was still logged into the server.

    What resolved the issue was I added Administrator rights to my login, and the difference upon logging in again to the server is that instead of asking for the administrator password, it would just give a warning that Dashboard was going to run and for me to say either Yes or No.  Choosing Yes, the remote session with dashboard would start but this time it would start in full screen instead of a window and i was able to stay logged in as long as I needed.

    Not sure if this is a problem, but what worked for me.

    Todd

    Wednesday, April 28, 2010 4:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Todd, this appears to be a bug; I've verified that it happens for me too on Windows 7, though not on Windows Vista.

    I'll report it on Connect (edit: here ), can you do so as well (more logs is a good thing)?

     

    I'm not on the WHS team, I just post a lot. :)
    Wednesday, April 28, 2010 5:27 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Will do once I get home.  Thanks for pointing out the log file collector, missed that.

    Todd

    Wednesday, April 28, 2010 6:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have the same router as the original poster.  Installed Vail on a test rig several hours ago & the installation went smoothly.  Set up user account before attempting to install connector on client.  Then proceeded to set up remote access & this is where i hit a roadblock, tried numerous times but still no joy.

    start the remote setup, runs through it's procedures & then starts verifying.  after a short period, it fails with the results 1: router blocked 2: port forwarding failed.  check router & upnp & port forwarding ok.  checked dhcp reservation, all ok.  correct ip address & mac address for vail.  so tried again & again for over an hour, same problem.

    Before I started, to prevent any problem/conflict, shutdown ver 1.  As this problem bugged me, shutdown vail, pulled the caddie out, & reinserted Server 2008R2.  no problems experienced.  So tried the Vail caddie in my SBS 2008 system, same problem, reinstalled SBS caddie & checked router, again no problems experienced.

    restarted ver 1, tried remote access, no problems.

    From what i can see with Vail, i like it, but wish to throughly test it, but cannot do so without remote access.  Any advice would be very much appreciated.

     

    note becaue of the different motherboards/components between Server 2008 R2 & SBS 2008, reformatted the drive on the SBS rig & did fresh install of vail.

    • Edited by Sirius B Saturday, May 1, 2010 3:37 AM spelling
    Saturday, May 1, 2010 3:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Just wanted to add, that you might need to add port forwarding for port 4125 also.  All the documentation I've read on the Vail sites mention port 80 and port 443 but seem to leave out 4125.

    http://www.homeserverland.com/wiki/w/whs/d-link-dir-655-router.aspx is a link to a webpage that explains port forwarding in full detail with regards to the D-Link DIR 655 wireless router and I found the information worked well with the latest beta Vail.

    I was having a heck of a time getting the Remote Access to remain constant with my DIR 655 when trying to access it externally. 

     

    Tuesday, May 4, 2010 9:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    No, per Microsoft in another thread, Vail uses the built-in Terminal Services Gateway, and therefore shouldn't need port 4125.
    I'm not on the WHS team, I just post a lot. :)
    Tuesday, May 4, 2010 11:29 PM
    Moderator
  • Question
    Sign in to vote
    1
    Sign in to vote
    Correct.
     
    Technically you ONLY need port 443 for total functionality, minus the redirection from http://blah.homeserver.com to https://blah.homeserver.com.  So if you want to be ULTRA secure, turn off UPnP on your router, and only forward port 443.  then make sure you type in the https://, if you don’t, you’ll get a 404 not found.
     
    4125 was used in the legacy Remote Desktop Proxy, and is only needed in WHS v1 and SBS 2003.
     
    Cheers,
       Sean
     
    This post is "AS IS" and confers no rights.
     
    "Ken Warren" wrote in message news:1d6bfe79-4e59-49b1-aaf9-f37b754bc1cc...
    No, per Microsoft in another thread, Vail uses the built-in Terminal Services Gateway, and therefore shouldn't need port 4125.
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, May 5, 2010 1:07 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello , I am having the same issue with the same router. Installed WHS2011, tried to set up remote access. hit the same error message. I am using DIR-655 router and the ports (80 and 443) are already open. rebooted several times both router and server.. no use.. any one fixed this issue? appreciate if any one can help? a
    Tuesday, May 10, 2011 2:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    DIR-655
    Firmware Version: 1.35NA
    Hardware Version: A3
     No problems here.  Wizard worked fine here.

    _______________

    BullDawg
    In God We Trust
    _______________
    <ramaarneh> wrote in message news:8b7a3ed6-eefc-4672-bd56-c09320a2e26d@communitybridge.codeplex.com...

    Hello , I am having the same issue with the same router. Installed WHS2011, tried to set up remote access. hit the same error message. I am using DIR-655 router and the ports (80 and 443) are already open. rebooted several times both router and server.. no use.. any one fixed this issue? appreciate if any one can help? a

    BullDawg
    Tuesday, May 10, 2011 10:02 PM