I suppose your server is 2012R2, then it will never configure your router even it is UPNP enabled. You have to do port forwarding by your own anyway.
I suggest you visit some "IP Detect" web site through the server IE, to see whether the detected public IP is as expected, then rerun Anywhere Access wizard, configure xxx.remotewebaccess.com again, clear dns cache, ping xxx.remotewebaccess.com again.
It just seems that the setting up of the XXX.remotewebaccess.com is not done correctly. If one tickss the box to choose to set up the router manually then the set up and repair run without error. However it still does not work. The server is server 2012 essentials r2 and the access has worked faultlessly for about a year. It stopped working about four weeks ago and the client just reported its fault about a week ago. I will run the domain set up again with a completely different name and see whether that is the issue. I do not think this is the case as I ran a set up on my workbench server and experienced no issues. I wonder whether the server is unable to detect the external IP address somehow.
Pinging XXX.remotewebaccess.com from different machines on external networks results in different ip addresses which is weird.
Hi lerlh,
Did you access the RWA site on internal network? Any find?
In addition, please refer to following articles and check if can help you.
Windows Server 2012 Essentials: Router Setup
Manage Remote Web Access in Windows Server Essentials
By the way, please also start a BPA scan and check if find relevant issues.
If any update, please feel free to let us know.
Best regards,
Justin Gu
lerlh, Holler if you are still having problems. If you set this domain up elsewhere it could be hung over and or it just takes a lil time to kick in.
If not do from the server whatismyip.com Does it match what your other domain says?
Do any of the other outside ping xxx.remotewebacces.com give the correct ip?
Thanks for the response Junxiang. I have run the access anywhere Wizard many times. I know the port forwarding is correct as the remote access used to work and I can access the login site if I put into the browser the second level domain name associated with the external static IP address. However then you start to get certificate issues.
It just seems that the setting up of the XXX.remotewebaccess.com is not done correctly. If one tickss the box to choose to set up the router manually then the set up and repair run without error. However it still does not work. The server is server 2012 essentials r2 and the access has worked faultlessly for about a year. It stopped working about four weeks ago and the client just reported its fault about a week ago. I will run the domain set up again with a completely different name and see whether that is the issue. I do not think this is the case as I ran a set up on my workbench server and experienced no issues. I wonder whether the server is unable to detect the external IP address somehow.
Pinging XXX.remotewebaccess.com from different machines on external networks results in different ip addresses which
Somehow the client's server does not get the external IP address from the broadband modem. There is only one modem on the network together with a fairly standard switch. I am at a bit of a loss as to what to do next I think I will set up and test a replacement modem on my test bench then install it at the site and see whether that makes a difference. At least I will identify whether this is the area failure.
Once again thanks again fellows for your suggest Jens any other thoughts are welcome
I think your problem is you set it up at your office then move it. If you open whatismyip.com at the permanent home it should match mydomain.remotewedbaccess.com ping
do a bunch of ipconfig /flushdns everywhere and restart all the switches hubs modems dns servers
However I did do some further stress last night on my to split server. I thought I will set up a spare modem and try exchanging their motives at the customer site to see whether that made a difference. When setting up this modem on my test bench system I found I could not get it to work. Change the modem to my existing moment modem and everything worked fine I did the swap twice but could not get the ASUS DSL N11 to work. My normal modem is a ASUS DSL N55U. Neither of these modems seem to support UPNP.
I seem to have got the anywhere access working but I'm not sure I could implement it reliably again. It is frustrating not to learn exactly what needs to be done.
Access to the site by access anywhere has stopped working again. No changes to settings but when I run the repair Wizard I get the error "Dynamic DNS cannot be updated". When I ping the domain XXX.remotewebaccess.com it does not now return the correct external IP address for the server.
Any suggestions as to how to troubleshoot this issue would be greatly appreciated.
lerlh
This happened to me on a particular install. I went round and round following the exact steps that worked on another server on a different network.
The fix was easy.
Log into you live ID account that you setup the personalized domain in the IE browser on the server and bring up your email. Make sure you can see you email on outlook.com
While still logged into your email in the browser, Run your wizard again. It worked for me after that. I don't know why.
This topic is archived. No further replies will be accepted.
Other recent topics
