Client on different subnets using old NT4 DC to authenticate?

[ianbnet]

Hi all,

After a recent upgrade from NT4 to 2K3 on my domain, I now have 2x2K3 DCs, and 2 NT4 DCs. The problem is that on my biggest subnet, .50, most (not all!) of the client machines are not authenticating with the 2003 domain controller, and are not getting group policy applied, are not registering in DNS, etc etc. It's a pain.

The 2K3 machines are in the .51 and .52 subnets, while .50 only has an NT4 domain controller. Is this the problem? Should I demote that old NT4 machine? I haven't wanted to do that until I'm sure, but I'm running out of ideas.

None of the manual ideas I've tried have worked. Registering DNS through login scripts (/registerdns),

AD Sites and Services, by the way, has the .50 and .51 subnets in the same site, with only the one 2K3 DC listed in that site.

Any ideas are appreciated.

Thanks!

 

[ianbnet]

wow... so after hours of banging my head against this, i found a solution seconds after posting. figures. but it appears that changing the domain membership from the old XXXX domain to the new XXXXX.XXXXX.local did the trick.

Now the question is if I can find away to change every machine on site without going one by one and doing it manually... oy.