G
Guest
Guest
Archived from groups: microsoft.public.windowsnt.domain (More info?)
Hey... got a strange situation with NT4 machines connecting to a Win2k3 forest.
We have a test.company.com and ad.company.com domain. Our NT4 machines are in the test.company.com domian.
There is a transitive two-way trust set up between test and ad, and all machines are joined to the test domain. At the login screen we can select ad.company.com as a domain for our XP and Windows 2000 workstations. But... we can only log in to the TEST domain from the NT4 machines.
the TEST.company.com also has trusts set up with our legacy NT4 domains. All workstations can log into these, including the NT4 workstations. (So all machines have access to all domains when joined to test.company.com, except that NT4 cannot connect to the AD.company.com domain).
My thinking is that we might have something wrong with the way we installed the dsclient tools on the NT4 workstations, but I'm not sure.
If anyone has any idea how to resolve this, that would be absolutely awesome.
Thanks!
Hey... got a strange situation with NT4 machines connecting to a Win2k3 forest.
We have a test.company.com and ad.company.com domain. Our NT4 machines are in the test.company.com domian.
There is a transitive two-way trust set up between test and ad, and all machines are joined to the test domain. At the login screen we can select ad.company.com as a domain for our XP and Windows 2000 workstations. But... we can only log in to the TEST domain from the NT4 machines.
the TEST.company.com also has trusts set up with our legacy NT4 domains. All workstations can log into these, including the NT4 workstations. (So all machines have access to all domains when joined to test.company.com, except that NT4 cannot connect to the AD.company.com domain).
My thinking is that we might have something wrong with the way we installed the dsclient tools on the NT4 workstations, but I'm not sure.
If anyone has any idea how to resolve this, that would be absolutely awesome.
Thanks!