Windows Forum

Ask something
Discussion Locked

No Domain Controller can be found.

0 helpful
9 replies

by geol

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm working with a WAN system, not the servers, just the work-stations. No probs creating the accounts and logging on except in one case. The scenario.
A user moved from one location to another, different IP address and machine name-the machine already had a registered used at that address with a profile- Initial logging on to the domain and creation of the account on the server at that address worked fine, the profile creation worked fine, account accessed, machine on the network, all okay.
Shut the machine down. Restart, no domain controller can be found, except maybe once in 10 tries. Not using dhcp. Sorry if this is a niave question, I'm not quite au-fait with networking yet, but this is driving me nuts!
any suggestions, apart from a big hammer!!

9 replies

by timthetoolman

You may find its now a non-issue as you read this...

In fact you may never check this entry again !? :-)

My guess would be that you have both PDCs and BDCs on your network and that initially the account was added to the PDC (as it is...) and following the shutdown was trying to be authenticated against a BDC which hadn't had the accounts database replication happen yet...

About one in ten tries at that point was an authentication against the PDC (for whatever reason...) and success!
OK... if this isn't the case and he/she still cant authenticate then...

Well, nothing else comes to mind apart from a bizarre hardware problem so - use that hammer!

Cheers,
Tim.

by geol

Your description, and #4 seem to have my problem in a nut shell, maybe my hammer and I should head for the server administrators, thanks.

by haritom

Greetings,

1.Change the system name first.
2.Without restarting change the same to workgroup with workgroup.
3.Finally look for the domain.

Check for the proper syntax of domain name and case sensitive password.

Look for proper driver for the NIC.
Ping the localhost. Look for ipconflict. ping the local ip address. Check for the subnet, Gateway.

Regards,
Harish.C.

by geol

I'd been down that road already, but thanks for letting me know I wasn't wandering aimlessly.

by lee.read

Try looking at resolution. Either lmhost file or WINS entry is incorrect. I have had same problem before and it turned out to be WINS server that had been "hand tweeked".

Hope this helps.

by geol

You may have pointed to the answer, the fault is certainly not at the workstation end.

This discussion is closed to new replies.