Link to home
Create AccountLog in
Avatar of Allen Morris-Yates
Allen Morris-YatesFlag for Australia

asked on

Windows 2012 R2 Essentials Anywhere Access setup cant get past domain name identification

I have installed a new instance (not an update from SBS 2011 or anything of that nature) of Windows Server 2012 R2 Essentials in a virtual machine running under 2012 R2 Hyper-V - everything up to this point is working fine.  I am now attempting to setup Anywhere Access.  When the wizard reaches the step where it asks "Do you own a domain name?" I select the option "I want to use a domain name I already own" and enter that (its a domain).  The wizard goes off "Checking your domain name", then responds with the message that "The list of domain services available for your server cannot be found. Make sure your server is connected to the internet. If this problem continues, wait a few minutes then try again."  The server is definitely connected to the internet as it has successfully downloaded and installed updates.  And in any case, I don't understand why it should need domain services as the domain name is already owned - does it perhaps think that I must have it registered with an MS approved domain registrar?  It appears that the wizard is missing an alternative step.  Is the problem due to my having installed Windows Server 2012 R2 Essentials rather than the more capable Windows Server 2012 R2 Standard then enabling the Essentials role?  I have searched TechNet and the various MS blogs but can't find anything that helps.  Any advice would be greatly appreciated.
Avatar of Davis McCarn
Davis McCarn
Flag of United States of America image

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Check C:\ProgramData\Microsoft\Windows Server\Logs\Dashboard.log. It may take a little while to dig through this file, but you may find something relevant.

Try searching that file for the string "Unable to connect to the Internet". If that doesn't reveal anything, feel free to post the log here, unless it's simply gigantic.
Avatar of Allen Morris-Yates


Thanks for the assistance - very much appreciated.  Whilst the detailed solution wasn't the answer, it did point me in the right direction, which was to examine the DNS entries being used by the server.  Turns out I had left the primary DNS pointing to an external source, one I had been using to enable internet access whilst downloading the OS image prior to setup.  As Davis noted, the wizard was expecting the domain to be resolvable when it fact it couldn't be by that external source.  Once I had removed the rogue DNS entry everything went smoothly.