14 replies to this topic

[nlitend1]

I released my domain in order to move it to a whs test machine and now have been trying for over 48 hours to re-establish my domain on my production box. I am able to log in with my Windows Live ID and I am able to choose a registered name associated with that account..but when it moves to the step..."Connecting to the Windows Server domain name service provider..." it hangs and eventually throws an error "The Domain name was not set up for you server. Wait a few minutes and run the wizard again. An unexpected or unknown problem occurred. Please wait a few minutes, and then try again."

I have set the ports 80 and 443 to forward to my server as before and able to see the server page via remotely placing in the WAN IP address (of course the cert does not recognize the web address and fails for remote access though)

Any ideas? I have a hard time believing it would have been down for this long...but really have no idea where to go from here. Has anyone re-registered successfully in the past 2 days?

Thanks,

nlitend1

[jmwills]

2 days, no, but within the past week, yes. Flush the DNS cache from that machine and see what happens.

[nlitend1]

2 days, no, but within the past week, yes. Flush the DNS cache from that machine and see what happens.

Thanks for the reply. ran ipconfig/ flushdns on the production server with same result. Is there anything else?

EDIT: I might also add that this WHS 2011 is running in a Virtualbox VM on top of windows 7. Network adapter is bridged.

Edited by nlitend1, 22 February 2012 - 03:58 PM.

[jmwills]

Does the remote setting point back to the test machine?

[nlitend1]

Does the remote setting point back to the test machine?

No, i never got it to work on the test machine. Giving up on that... just want it back to my main box

[ikon]

I was wondering exactly what you meant by "released my domain"?

[nlitend1]

I was wondering exactly what you meant by "released my domain"?

i'm not sure 'release' is the right word. (IIRC that's what the option said when i removed my xxx.homeserver.com entry on the production machine though) It basically 'released' xxx.homeserver.com so it could be attached to a different server.

[ikon]

i'm not sure 'release' is the right word. (IIRC that's what the option said when i removed my xxx.homeserver.com entry on the production machine though) It basically 'released' xxx.homeserver.com so it could be attached to a different server.

Ah. This is a specific WHS thing? Got it.

[nlitend1]

Ah. This is a specific WHS thing? Got it.

Ah, yes. It's the wizard that runs under server settings > remote web access > Domain name in WHS 2011.

[nlitend1]

Update! It got it working. I noticed that the time on the server was 2 minutes behind my laptop when using RDP...so I did the manual "update now" to the clock and it worked the first try after. No idea how the time can lag behind when it's set to sync with "time.windows.com"...but I think manually updating the clock fixed the error. Maybe coincidence, not really sure. Thanks for all the help guys! WHS FTW

[ikon]

I doubt it's a coincidence. 2 min. off is exactly the time where Windows domain servers begin denying access. The rule is that all computers in a Windows domain must be synced within 2 min. or they won't be able to access server resources. I know I keep saying 'domain', and you probably don't have an official 'domain', but I suspect the timing is important anyway.

[jmwills]

The client is probably looking at the BIOS clock and the server is looking at an actual time server. Configure the client to look at the same timeserver.

I thought it was a 5 minue window? Too much @(*&$%^@( to remember.

[ikon]

I checked just before posting; it is 2 min.

[jmwills]

I just wonder if this has anything to do with the newly appearing monitoring error. My Launpad was clear at 0615 this morning, at 0617 the alert appeared and I could find nothing in the error logs with that time stamp on it, either client or server side.

I am going to point the client and server to the same time server and watch it. If nothing else, I can rule that out.

[ikon]

I just wonder if this has anything to do with the newly appearing monitoring error. My Launpad was clear at 0615 this morning, at 0617 the alert appeared and I could find nothing in the error logs with that time stamp on it, either client or server side.

I am going to point the client and server to the same time server and watch it. If nothing else, I can rule that out.

Cool. I know I don't need to say it, but let us know