dv

Just an update.

I can NLTEST /DCNAMEOMAIN and it prints the correct
server name.

I tried downloading and running a version of netdom that
Michael Giorgio pointed to in one of the threads here.

I got an error to the effect that this action requires
directory services. I tried again and got access denied if
I recall correctly. The XP box I ran it on did in fact
appear to be joined to the domain despite the error. But
when I tried to add a domain user to the local machine I
got a trust error. I tried nltest /SC_QUERYOMAIN and got
an RPC error..

No luck so far..


So

at

side.

michael giorgio - ms mvp

Hi,

I am assuming you have an NT 4.0 domain in place?
If so how many BDCs? Open a dos prompt on the PDC
and all run nbtstat -n and verify there are not conflicts
particularily the domain name 1c group name for DCs. Next
run nbtstat -a against the name of each BDC and verify there
are no conflicts in their name tables. Next check the system log
of the event viewer on your PDC and verify there are no services
failing.

dv

Interesting.. I am showing a conflict on the 1c group name
on the PDC. Yet I find no conflicting record in WINS. I
had a NT4 BDC loaded up on this other server for a little
while but I wiped it and reloaded W2k3 on it. However that
machine is neither a member server of this NT4 domain nor
is it running as a AD domain controller. I deleted the
machine account for it too. I double checked the W2k3
machine with nbtstat -n to make sure it wasn't registering
1c and it wasn't. Another NT4 member here shows no
registration of 1c. Not sure what is conflicting then.

there

system log

services

ready

michael giorgio - ms mvp

The domain name 1c netbios name is a group name
containing the tcp/ip address of the PDC and all BDCs
on the domain. Only DCs will register this name not
members or workstations. This name must be resolved
during the authentication sequence. A reboot of the PDC
should resolve the conflict.