Got it. I am checking with the guys.

Jeffrey, just to give you an update: we are facing some serious problems at our internal network and everybody is rushing around to get it fixed. Your issue is also on the table to be taken care of and we will get back to you the soonest.

Ivan,

What is the status on my issue?

Jeff

Hi Jeffrey.

You really should be able to get the status page, at least. So, we will try to get the DNS out of question. Please, could you go to your hosts files (c:\windows\system32\drivers\etc\hosts), edit it and add your domain for the 127.0.0.1 IP? It should look something like this:

Hi Ivan,

I made the change and restarted the server.  The Status.aspx page is loading.  Enterprise Server is now responding. 

Why did I need to add that entry into the Hosts file when it was not required before when it was working for the last of couple of months?

Jeff

It didn't. Ivan and I were talking this morning and this only circumvents the DNS lookup on the machine in which you add it. We assumed that the problem that you were having was DNS related. So if this machine is your DNS server that resolves your host name, then something changed...OR...your DNS service had died and was no longer responding. We just took DNS out of the formula. So if the rest of the world can log into your ES server and is up, then this entry had absolutely nothing to do with that. We were just going to use this as a diagnostic tool to remove the DNS resolution from the formula so we could get to the status page.

Hi Trent/Ivan,

OK.  I believe I understand your explanation after talking to my network admin.

Thank you for helping me resolve my issue.

Jeff

Glad you got it going, Jeffrey.