New Domain - VPN issues - looking at old domain
I’ve had a Microsoft vanity domain on a machine since 2016. It died on Friday due to GoDaddy no longer renewing the SSL certificates, BUT the dynamic DNS from remotewebaccess.com still functions.
What I did was get a new domain and certificate for remote access and ran the wizard. That went fine. You can get a working RDP file just fine. What the configuration wizard did not do is take out the old vanity.remotewebaccess.com and put in the remote.vanity.com in the VPN connect exe. The exe starts the setup and goes right past the part where I could put in the remote address and adds it to the list of network adapters. I can add the address
I looked at the Domain Manager key in regedit, and it’s got the vanity.remotewebaccess.com as the provider.
Do I need to go back and release the vanity.remotewebaccess.com and then run the manual setup again?
- AskAmyS asked 2 months ago
- You must log in to post comments.
Yes, unfortunately the remotewebaccess.com Microsoft personalized domain names no longer work in Windows Server Essentials. Microsoft is aware of the issue, but obviously doesn’t care enough to correct them at this late point in the product’s lifecycle. Therefore, in order to continue using the Anywhere Access/Remote Web Access features of Essentials you will indeed need to manually set up your very own custom/vanity domain name instead. I have a step-by-step writeup on how to just that available over here:
How To Manually Set Up A Custom / Vanity Domain Name In Windows Server Essentials
That being said… If you were previously using a Microsoft personalized domain name, then you do not need to release it in order to successfully set up a custom/vanity domain name. The Domain Manager key in the registry has separate sections for use with a manually configured domain name as well as for a Microsoft personal domain name, and the Anywhere Access/Remote Web Access wizard configures the required section accordingly (i.e. there shouldn’t be any reason for you to have to go in and manually edit that registry key AFAIK).
EDIT: You may want to take a look at my answer to this post as well:
- Mike answered 2 months ago
- last edited 2 months ago
- I did all of that. I have the new domain and certificate. That part works. However, my VPN users are still getting the old domain when being connected through the new domain connector. What I did was disconnect them from the old connection and redid them with the new connector. When I download it, I get the new domain in the download name, but when I run the connector, that point where it connects to the server, it sees the old microsoft domain and not the one I bought and installs that old domain as the adapter in network connections. Then the install fails. The install will sort of create a user, but will not join the domain. I have tried changing the connector in the network adapters to the new domain, but that doesn’t resolve the issue. The SSL certificate is tied to the name, so using the WAN IP address doesn’t work, either If you would like to see this in action, I’ll be happy to set something up for you.
- You must log in to post comments.
I went through the server registry and found 3 instances of the old Remote Access domain and no instances of the new domain. I replaced the old name with the new name in each instance and restarted the server. I downloaded the new connector, and ran the installation and was able to complete the connection. I got a message that said I could not be logged in and to try again or close. I rebooted my machine and tried again. I got the same message, but looking at the dashboard, it showed I was connected, so I just closed the warning on the remote machine. I was able to map drives to the server. What didn’t come down was the server folders folder, the little green connector in the system tray, and the login script didn’t run. I can live with that.
- AskAmyS answered 2 months ago
- You must log in to post comments.
