ad dc

[Craig A. Mills]

I had a w2k serrver in a nt4 domain. upgraded the nt4 PDC to w2k making it the master DC. I then added the the standalone w2k server as a DC. Now when we access the new DC through network places, map drives in the logon script or otherways, the error comes back logon failure: taget account name is incorrect. If we replace the the computername with ip it works. What permissions got messed up when dcpromo succeeded? Or is there a DNS error that became unbearable with the promotion? MS wasn't any help.

[craig a mills]

Got it. netdom resetpwd did the trick.


------------
Craig A. Mills at 8/30/2002 2:40:13 AM


I had a w2k serrver in a nt4 domain. upgraded the nt4 PDC to w2k making it the master DC. I then added the the standalone w2k server as a DC. Now when we access the new DC through network places, map drives in the logon script or otherways, the error comes back logon failure: taget account name is incorrect. If we replace the the computername with ip it works. What permissions got messed up when dcpromo succeeded? Or is there a DNS error that became unbearable with the promotion? MS wasn't any help.

[Ofir Odeny]

Definitely a DNS resolution problem,
you can verify it with "nslookup command"
Type "nslookup server_name" (without the quotations),
and see if the dns has the correct A record and SRV record for that server.

Ofir.

------------
Craig A. Mills at 8/30/2002 2:40:13 AM


I had a w2k serrver in a nt4 domain. upgraded the nt4 PDC to w2k making it the master DC. I then added the the standalone w2k server as a DC. Now when we access the new DC through network places, map drives in the logon script or otherways, the error comes back logon failure: taget account name is incorrect. If we replace the the computername with ip it works. What permissions got messed up when dcpromo succeeded? Or is there a DNS error that became unbearable with the promotion? MS wasn't any help.