After installing two Server 2016 Essentials servers this week, I found Anywhere Access on both servers didn’t work properly. When I browsed to the Remote Web Access URL (mycompany.remotewebaccess.com) , I was always greeted with the Internet Information Services (IIS) page.
I figured I may have setup something wrong, so I double-checked my settings but everything was setup correctly.
I then went to mycompany.remotewebaccess.com/remote and the site then came up fine.
This is the workaround I found to fix this issue.
Step One: Open Internet Information Services (IIS)
Step Two: Go to Sites > Default Web Site > HTTP Redirect
Step Three: Check the box Redirect requests to this destination: “Enter company URL with /remote at the end.
Check the box “Only redirect requests to content in this directory (not subdirectories)”
Step Four: Click Apply You should be set now. If this doesn’t work for you, restart the Default Web Site.
I found this forum thread on TechNet with other experiencing the same issues. It wouldn’t be a bad idea to comment on that thread. That will help bring it to Microsoft’s attention. I believe this is a bug with Server 2016. Server 2012 and 2012R2, this worked perfectly without having to do this HTTP Redirect. I will keep you posted if I learn more.
Please comment below if this helped you. You can find me on Twitter and check out my YouTube Channel.
In 2012 R2 this is not accomplished with a redirect, but using code in default.aspx, this appears to have been removed in 2016. Are you using the SKU or the Role? I notice that the Default Web Site points to c:\inetpub on the role, not “C:\Program Files\Windows Server\Bin\WebApps\Site”
If you update the content directory to the ‘correct’ path it should work as expected.
Hello Robert, I checked on a server 2012 Essentials and I saw they don’t use the redirect to accomplish this either. I figured something must be missing, but I used the http redirect for a temporary fix. I am using the Server 2016 Essentials SKU. I’ll let you know where that path points.
Seems to be the same on SKU and Role, https://windowsserveressentials.com/2016/10/31/remote-web-access-login-page-redirect/
This solution will stop the RD Gateway server working properly.
Agreed. Any fix for the RD Gateway not working?