Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just had a server in our lab disallow me from adding it as a host in Windows Load Balancing.

Suddenly, out of the blue (cause this has been working fine), when I tried to re-add the machine into the load balanced cluster, it requested credentials. I am logged in as a domain administrator which is the same procedure I've used to add the other machines into the cluster and even this machine in the past. When I supply a local machine administrator credentials, it allows me through.

When I look at the administrators group, all domain accounts display only SID's (rather than the friendly display names). When I try to add domain admins it reports that the account already exists.

The only way I could resolve this was to remove the server from the domain, reboot, and add it back onto the domain, and reboot.

After that, everything was fine and I could add the machine back into the load balancing cluster without any problems while logged on with the same account that was originally refused.

Does anyone know what caused this, and if there is a less extreme way to correct this problem?

Updates: Event logs are not very usefull as we have a application on the server that generates allot of events, and by the time I realise the problem the event log has cycled, but I have oberved some DNS related entries in the past.

We also had major issues with the time service in the past. According to Microsoft the clocks should just sync with the PDC by default. Yea, right... we had Microsoft out for about 3 days before they could resolved the issue. (Turned out we didn't have NetBios Installed) This is however resolved now, and I confirmed the time when I realised the issue, because I know this has been an issue in the past.

share|improve this question
Tell us what the event log says, up to the time you found the problem. – mfinni Apr 18 '12 at 13:19
Is your clock on that server showing the proper time (is it in sync with the PDC's)? – HostBits Apr 18 '12 at 13:34
A time problem could have caused this. A DNS problem could definitely have caused this. Gotta look at the logs. – mfinni Apr 18 '12 at 17:37
I had another server giving me problems which I just noticed to be the same problem, which was resolved by following the same procedure. Any other ideas are welcome. If I notice this again, I'll be sure to check event logs imediately. (See updates above) – Gineer Apr 19 '12 at 15:03
up vote 0 down vote accepted

This problem does seem to relate to the DNS. It seems that some of our servers had multiple (conflicting) entries in DNS. Note that in one case one of the server's issues were caused by another machine having two entries (one of which was the same IP address as the machine exibiting the problems.) I hope this helps someone.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.