Windows home server domain name error

So I plugged my server directly into my cable modem, set up remote access, and I still got the same error:. BUT navigating to the url associated with my homeserver, I have the ability to enter my login credentials, and login successfully.

But still the Dashboard shows my domain name has not been set up. There is no link displayed. Is there any other place I can use to gather error reports other than this and the initial log I mentioned? Is there a way to manually fix this? I also noticed that if I purposefully mistype my Live password, I immediately see a "The user name or password is incorrect. Retype your user name and password. But the moment I type in the correct password, that's when I get the message saying there was an error setting up the domain.

I manually synced the time, as requested, via a Remote Desktop Connection. I then launched the Dashboard and tried to configure the remote access and got the same error. Please remember to mark the replies as answers if they help and unmark them if they provide no help. Hi, There is a lot error message like below are recorded in SharedServiceConfig. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue.

Local socket timeout was ' FIX: A. NET Framework 3. I truly understand how inconvenient you feel about the issue , thank you for the efforts you've done so far and your continuing patience. Also, thank you for your understanding. Best Regards, Eve Wang. Same error. This time, I saw the following in the log file named ConfigSvcVerbose. Notifications: Information: [0] LNx Removing one instance of each of the following categories from all neighbors filters except RNx "Initial Configuration Website".

Notifications: Information: [0] LNx Will tell neighbor FNx03 that we are no longer interested in the following categories: "Initial Configuration website". I installed the trial of Windows Server Server Essentials on the same computer, and Remote Access configured correctly the first time. With that, I think there is something wrong either with Home Server setting up the Remote Access, or the servers rejecting the Remote Access first-time configuration.

My Home Server's boot drive died and I was forced to reinstall it and now I can't set up domain name for my server. Everything else is up and configured with only two warnings:. Once you have installed this item, it cannot be removed.

You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Any update? Would you please let us know if you can find the file that Robert mentioned?

Just additional. Please check time settings again and run a synchronization manually. And monitor the result. Meanwhile, please restart Windows Server Domain Management service manually and check if this issue still exists. In addition, please navigate to Event Viewer and check if you can find any error messages. It may help us to go further analysis. Hope this helps. Best regards,. Justin Gu. Office Office Exchange Server.

Not an IT pro? Windows Server TechCenter. Sign in. United States English. Ask a question. Please try again in a few hours I waited a few days, I've swapped time zones, I've tried setting up a new personalized domain. How do I make this work? How were you able to tell the server time was 30 seconds behind the server it was getting a certificate from? And how do you determine what server is giving the certificate?

To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. I have been fighting with this for three days now.