I used to have anywhereaccess on our Windows 2012 R2 Server working perfectly. We share a building with other businesses and the IT system had maintenance, since then I've received this error:

enter image description here

They're adamant it's nothing they've done but everything I try doesn't seem to work, I've restarted all HTTP services, deleted old SSL certificates and restarted the IIS web services.

When I visit the page, I'm presented with a blank page.

enter image description here

Lastly, I've also tried looking at what uses port 80 and 443. I used netstat -b -a and I got this result:


I also found it uses PID 4. Which is the "System" enter image description here

Does anyone have any advice or explanation as to why when I login to the remotewebaccess domain it's a blank page?


  • Are you using any public DNS servers such as Open DNS? If so, try changing to googles, and as Open DNS has caused problems with Anywhere access historically. Also is port 80 and 443 accessible from the outside(Telnet to your external IP to those ports, do it from /outside/ of your network)? Do you have control over the router if you are behind NAT. If so, is the ports 80 and 443 properly forwarded to your internal IP? If you are not behind NAT and have a public IP. Check all firewalls, if they arent blocking and you dont have access from outside, call your ISP. – artifex Jul 20 '15 at 13:05

Perhaps the SSL handshake failed , You Could Check if the private Key is missing, or broken ...

I suggest using this Diag tool to help you Spot the issue (of course depending on your IIS) Below is For IIS 7:


And you can also capture a network trace from the client or server, Filter it to show SSL and TLS , it will clearly show you the process...


The browser errorpage that you posted says it quite clearly - the SSL certificate the box serves is invalid for the domain name you access it with.

The web server seems fine, Anywhere Access is not working because the certificate is invalid.

Have the server set up with a valid certificate containing all the domains the server is supposed to be accessed with and it should work.

Update: Try using a different client, a phone or laptop and check if it works there to exclude virus scanners/personal firewalls. When accessing it, I just get 401 - Not authorized and a blank response page. It seems like the default error pages were set to blank pages. Checking with nmap -A -p80,443 does look like IIS is running as it should.

  • It's now a blank page. So it's not the SSL certificate as now it's a blank page. Check OP – Bradly Spicer Jul 20 '15 at 8:35
  • nmap isn't a valid command and I couldn't find it in the windows dir. – Bradly Spicer Jul 21 '15 at 9:40
  • @BradlySpicer NMAP is a port scanning tool and does not ship with Windows. I don't think it would help you any more if you run it on your box since the server seems to be listening on the appropriate ports. – ngn Jul 21 '15 at 10:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.