I log into the server dashboard, go to “Server Settings” and select remote web access.
Router: WNR35003v2 (Netgear), evertying sets up fine
Domain name: I select Setup. Getting started window, I hit next.
I want to use a domain name I already own, domain name abc.com
I get a screen “Update information on GoDaddy.com”. If I use the button to go to godaddy.com and login, I am presented with a screen filled with information that has nothing to do with anything.
If I come back to set up and press next, I get a prompt to store my domain name info, user name and password I registered with godaddy.com
I hit next, a few seconds later I am presented with a screen: An error occured while setting up your domain name. The domain name was not set up for your server, wait a few minutes and try the wizard again.
====
It appears the easy wizard is no longer the way to do this.
What did I do wrong, and what steps do I need to take?
I think GoDaddy has changed how they approach how they handle business and it has affected how the 2008 wizard works in this instance.
I think the solution I put in works. For the longest time I had www.abc.com forward to www.abc.ca
Now I can use www.abc.com as access to remote web access. It doesn’t seem hard to change the DNS zone records to add remote.abc.com and then cause www.abc.com to forward to www.abc.ca in the future. I can reissue my SSL on remote.abc.com as needed. Fairly straight forward process. And maybe someday I’ll cause remote.abc.ca to forward to remote.abc.com
Right now it is working fine.
Only issues now are:
1. I get a server error that “REmote Web Access is enabled, but an Internet domain is not set up. You must set up a domain name to remotely access the server.” Like I said above, I have no issues accessing it. I think there has to be a way to manually enter it via IIS.
2. Remote Desktop access via Remote Web Access is not working. I RD just fine when not using the Remote Web Access. I’m wondering two things: Is it because the computer in the office uses a non-standard port for RD? I’ve turned off the targets computer firewall to see if it is a port issue, but that doesn’t work. It may be a result of not having a domain as mentioned in 1 above.
I can access the computers remotely through remote web access
Now, new issue:
At home on my Windows 8.1 machines I can access remote.abc.com, login and everything works fine.
At home on my Surface Pro 2 machines I can access remote.abc.com, login and get 404 error (same network, just wireless)
At work, through a local windows 7 pro machine, I can access remote.abc.com, login and everything works fine.
At work, through my Surface Pro 2 machine, I can access remote.abc.com, login and get 404 error (same network, just wireless).
I’ve made sure that my SP2 machine only has IE installed and is the default browser. It is also fully updated through MS updates. I’ve tried turning off it’s firewall to see if it changes anything. Restarted the computer etc etc etc.
