Problem joining older PC's to win2k domain

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We just installed a WIN2K domain controller at a location where there was none before. The WIN2K DC had the latest service pack applied and was a dual processor 1Ghz server with 1Gig of memory . There were about 50 NT 4.0 workstations to join on the new domain. All had service pack 6A installed. Half of the workstations were older PC's like Pentium II's 300 - 500 Mhz. The other half were Pentium III's & Pentiun IV's. The newer NT 4.0 workstations joined the domain the first time. On the older PC's we had to just keep trying to join the domain time and time again. They would finally join and after that would work OK. Many took 10 - 15 attempts before joining correctly. The error was that no domain controller could be found. The PC's and domain controller were hooked up to the same switch. The newer PC's joined the first time. Does anyone have any ideas as to what might be wrong or what can be done to fix this problem?
 
The NT4 boxes are looking for the PDC Emulator. If they can't contact it,
they won't be able to join the domain. Is your PDC Emulator FSMO Holder at a
remote site with a bad data link?

--
--
Brian Desmond
Windows Server MVP
(e-mail address removed)12.il.us

Http://www.briandesmond.com


perplexed-n-GA said:
We just installed a WIN2K domain controller at a location where there was
Click to expand...
none before. The WIN2K DC had the latest service pack applied and was a
dual processor 1Ghz server with 1Gig of memory . There were about 50 NT 4.0
workstations to join on the new domain. All had service pack 6A installed.
Half of the workstations were older PC's like Pentium II's 300 - 500 Mhz.
The other half were Pentium III's & Pentiun IV's. The newer NT 4.0
workstations joined the domain the first time. On the older PC's we had to
just keep trying to join the domain time and time again. They would finally
join and after that would work OK. Many took 10 - 15 attempts before
joining correctly. The error was that no domain controller could be found.
The PC's and domain controller were hooked up to the same switch. The newer
PC's joined the first time. Does anyone have any ideas as to what might be
wrong or what can be done to fix this problem?
 
Brian's right -

I feel your pain. Sometimes the NT4 boxes can be a major pain if WINS
records are not registered correctly. Search WINS by record type and see if
the Domain Controller and Domain Master Browser (PDC emulator) are listed
with the correct ip addresses.

If that's the problem:

Unable to Add Workstation to Domain: 'A Domain Controller for Your Domain
Could Not Be Contacted'
http://support.microsoft.com/default.aspx?scid=kb;en-us;272124

In addition to the suggestions listed there, moving the PDC emulator role
from one DC to another temporarily (and moving back if desired) will
register the WINS records again - but keep an eye on the records, becasue if
the DC is having trouble with WINS registration the records will tombstone
again.
 
Back
Top