<div>
You do indeed need to use a domain name. Part of the remote web access website is that it is intended to be accessed by remote users, hence the name. The only way that could work is with a domain name. If the user isn't remote, there is no reason to access or use the website. So the two are intrinsically tied.
</div>


You do indeed need to use a domain name. Part of the remote web access website is that it is intended to be accessed by remote users, hence the name. The only way that could work is with a domain name. If the user isn't remote, there is no reason to access or use the website. So the two are intrinsically tied.

<div>
So you can't just set up, for instance, an intranet using <a href="http://servername/intranet" rel="ugc">http://servername/intranet</a>&nbsp;that is NOT access outside of the network?
</div>


So you can't just set up, for instance, an intranet using http://servername/intranet [http://servername/intranet] that is NOT access outside of the network?

<div>
<div class="content wysiwyg-content">
I'm trying to set up a 2012 Essentials Server and I'm having issues with the internal default website. When I go to <a href="http://servername/" rel="ugc">http://servername/</a>&nbsp;i get a message saying Remote Web Access is turned off. When I go through the Remote Web Access config wizard, it's asking me to use a domain name. Is it not possible to use just the server name? Do i have to use an actual domain name?
</div>
</div>


I'm trying to set up a 2012 Essentials Server and I'm having issues with the internal default website. When I go to http://servername/ i get a message saying Remote Web Access is turned off. When I go through the Remote Web Access config wizard, it's asking me to use a domain name. Is it not possible to use just the server name? Do i have to use an actual domain name?

Access to default website 2012 Server Essentials

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.