Hi,
Our small office is using 2012 R2 Essentials for our hybrid (i.e. data files stored on a VM that syncs to a cloud storage server) and everything is functioning rather nicely. I've had my share of learning to do and the OS has probably been installed
at least 25 times while learning. Albeit not while the server was in production, but enough times to give me a decent education of everything I shouldn't do.
As of last week, our xxxxx.remotewebaccess.com Microsoft website stopped working. I can still RDP into the server, using our WAN IP address but I've had to make changes in order for our employees to access the server. They only need access to
data files that consist of MS Word, Excel, Publisher, Powerpoint, etc... I do need to publish a specialized application to the server but I've got a "twin" server that I call my Lab computer so I'll do that first on that machine.
I've run Robert's Essentials Tester on the Server and everything reports fine with the exception of the IIS Default Website. I believe the problem occurred when I replaced and added a 3rd NIC to the Server. I removed the DNS entries to the additional
NIC and never enabled the 3rd NIC.
Rather than make matters worse, I'm not going to "dive" into this issue without some guidance from those in the know. I've pasted the error from Robert's tester below.
************************************************
* Essentials Server Configuration Tester *
************************************************
OS Detected: Microsoft Windows Server 2012 R2 Essentials
This tool will check your current Configuration against known Essentials Server Values.
Written by Robert Pearman (TitleRequired.com) October 2015
Version Info: Version: 2.03
1. Test IIS
2. Test CA Infrastructure
3. Test Services
4. Test Service Ports
0. Quit
Enter Task..
1
Only Errors will be shown.
Checking Websites..
Checking Connect Site..
Checking Virtual Directories..
Checking AppPools..
Checking ISAPI Filters..
Checking IIS SSL..
Checking IIS Bindings..
Binding Missing : Default Web Site
Checking IIS Authentication..
Review your results, items in red should be investigated.
The error I get when trying to repair follows:
The domain name was not set up for your server. Wait a few minutes and run the wizard again.
The computer is 100% connected to the internet. I don't knowingly know what I did to change the configuration but this system worked perfectly before the replacement/addition of the NICs. The router is not blocking
anything outgoing.
I've googled and researched the this error and its' recommended "fixes" but when it comes to the IIS fix, there seems to be a wide variety of approaches. Rather than pick one and move forward I'd really appreciate
what would be the correct thing to do.
Thanks so much and best regards,
Tris