Cannot find Primary DC??

[Alec]

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Hi,

We had 2 WindowsNT4 servers in an NT domain; a PDC and a
BDC. We have now added 2 new BDC's to the mix to prepare
for an NT 4.0/Exchange 5.5 migration to Win2k3/Exchange
2k3. Yesterday, we promoted one of the new BDC's to
become the new PDC. The old PDC was demoted successfully
to a BDC.

Now, I can run server manager on the new PDC as well as
on the 2 BDC's that were not touched. But when I run
server manager on the old PDC, I get the message "Cannot
find the Primary DC for domain".!!

I tried rebooting the old PDC but no luck. Event logs
look ok - ie they show that the SAM is replicating.

Net accounts on the old PDC reports this:

Force user logoff how long after time expires?:
Never
Minimum password age (days): 1
Maximum password age (days): 365
Minimum password length: 6
Length of password history maintained: None
Lockout threshold: 5
Lockout duration (minutes): 30
Lockout observation window (minutes): 30
Computer role:
BACKUP
Primary Domain controller for workstation domain:
Unknown
The command completed successfully.

The old PDC was/is the Exchange 5.5 server as well. Any
help would be appreciated!

Thanks,

Alec

 

[Guest]

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Immediately after attempting to open user manager open
a dos prompt and run nbtstat -c and verify the domain name
1b unique name is pointing towards your new PDC. Also
not the TTL or Time to Live. If it's 600 secs or -1. A -1 tells
me the BDC is pulling the name from it's local lmhosts file and
a -600 or less tells me the name is being pulled from WINS. If
the latter then open the WINS database and sort by name then
delete the 1b entry pointing towards the old PDC.


"Alec" <amcmillan@darcydeacon.com> wrote in message news:
> We had 2 WindowsNT4 servers in an NT domain; a PDC and a
> BDC. We have now added 2 new BDC's to the mix to prepare
> for an NT 4.0/Exchange 5.5 migration to Win2k3/Exchange
> 2k3. Yesterday, we promoted one of the new BDC's to
> become the new PDC. The old PDC was demoted successfully
> to a BDC.
>
> Now, I can run server manager on the new PDC as well as
> on the 2 BDC's that were not touched. But when I run
> server manager on the old PDC, I get the message "Cannot
> find the Primary DC for domain".!!
>
> I tried rebooting the old PDC but no luck. Event logs
> look ok - ie they show that the SAM is replicating.
>
> Net accounts on the old PDC reports this:
>
> Force user logoff how long after time expires?:
> Never
> Minimum password age (days): 1
> Maximum password age (days): 365
> Minimum password length: 6
> Length of password history maintained: None
> Lockout threshold: 5
> Lockout duration (minutes): 30
> Lockout observation window (minutes): 30
> Computer role:
> BACKUP
> Primary Domain controller for workstation domain:
> Unknown
> The command completed successfully.
>
> The old PDC was/is the Exchange 5.5 server as well. Any
> help would be appreciated!

>
> Alec

 

[Guest]

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Thanks Michael,

There were multiple entries in the lmhosts file!


"Michael Giorgio - MS MVP" <Michael.Giorgio@NoSpam.mayerson.com> wrote in
message news:%23TImKZSFFHA.464@TK2MSFTNGP09.phx.gbl...
> Immediately after attempting to open user manager open
> a dos prompt and run nbtstat -c and verify the domain name
> 1b unique name is pointing towards your new PDC. Also
> not the TTL or Time to Live. If it's 600 secs or -1. A -1 tells
> me the BDC is pulling the name from it's local lmhosts file and
> a -600 or less tells me the name is being pulled from WINS. If
> the latter then open the WINS database and sort by name then
> delete the 1b entry pointing towards the old PDC.
>
>
> "Alec" <amcmillan@darcydeacon.com> wrote in message news:
>> We had 2 WindowsNT4 servers in an NT domain; a PDC and a
>> BDC. We have now added 2 new BDC's to the mix to prepare
>> for an NT 4.0/Exchange 5.5 migration to Win2k3/Exchange
>> 2k3. Yesterday, we promoted one of the new BDC's to
>> become the new PDC. The old PDC was demoted successfully
>> to a BDC.
>>
>> Now, I can run server manager on the new PDC as well as
>> on the 2 BDC's that were not touched. But when I run
>> server manager on the old PDC, I get the message "Cannot
>> find the Primary DC for domain".!!
>>
>> I tried rebooting the old PDC but no luck. Event logs
>> look ok - ie they show that the SAM is replicating.
>>
>> Net accounts on the old PDC reports this:
>>
>> Force user logoff how long after time expires?:
>> Never
>> Minimum password age (days): 1
>> Maximum password age (days): 365
>> Minimum password length: 6
>> Length of password history maintained: None
>> Lockout threshold: 5
>> Lockout duration (minutes): 30
>> Lockout observation window (minutes): 30
>> Computer role:
>> BACKUP
>> Primary Domain controller for workstation domain:
>> Unknown
>> The command completed successfully.
>>
>> The old PDC was/is the Exchange 5.5 server as well. Any
>> help would be appreciated!
>
>>
>> Alec
>
>

 

[Guest]

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Cool. Your welcome. Thanks for the update.

"Alec McMillan" <amcmillan@darcydeacon.com> wrote in message
news:%23q8PKNTFFHA.1392@tk2msftngp13.phx.gbl...
> Thanks Michael,
>
> There were multiple entries in the lmhosts file!