After establishing a one way way trust relationship from a Windows 2000
resource domain to a Win NT 4.0 accounts domain, the trust relationship
continually breaks. The trust goes in on both domain controllers, and it
appears to work at first, but after you attempt to bring up the machines in
the resource domain from a machine in the accounts domain, as when you
assign a permission on a file, you usually get a modal error dialog
indicating that:
"The trust relationship between the primary domain and the trusted domain
failed"
This happens when you try to select the resource domain from NT 4 server
manager, and when you try to set a permission on a file in the resource
domain that references any account in the accounts domain. As soon as you
do a Properties | Security on a file in the resource domain, and then select
the accounts domain and attempt to view specific accounts and groups, you
get the trust failed message."
How can I get the trusts to stick? So far the whole trust feature set seems
entirely too fragile to rely on in a production mode. It takes almost
nothing to break a trust. Any ideas are appreciated.
--
Will
NOTE: To reply, CHANGE the username to westes AT uscsw.com
I have never had problems running trust between NT4 and W2K domains.It works
fine
"CHANGE USERNAME to westes" <junk...@uscsw.com> wrote in message
news:OxeFeWcd$GA....@cppssbbsa02.microsoft.com...
Our configuration is that the lab domain controller runs AD in mixed mode,
and has two ethernet cards. The lab segment is almost 100% Windows 2000
machines, but has maybe one NT 4 machine. The segment that connects to
the Windows NT 4 domain is almost 100% NT 4 machines. The trust is with an
NT 4 domain controller.
We can't get the trusts to stick. They break almost as soon as we establish
them, with any level of real use.
--
Will
NOTE: To reply, CHANGE the username to westes AT uscsw.com
"Thierry DEMORRE" <nospam...@winwise.fr> wrote in message
news:eX17avzd$GA.258@cppssbbsa04...