B
Blair
We have two Windows 2000 domains(A & B) that are trusted each way.
Users from one domain(A) login to a Terminal Server on another domain(B)
with ID's created from domain B(It's just earsier this way, considering
the application config). These user id's are members of a global
security group, that has rights to print queues residing in domain A. So
in their TS session, they are attaching to printers that they would
normally use in their local environment. Anyway, all of the printers
that have been defined for them, now have a status of: "Opening", or
"Access denied, Unable to Connect", or just "Unable to Connect". I'm
thinking that there is perhaps a trust issue. Users on domain B can
connect to shares created on domian A, but it seems when we try to do
the opposite, it says that domain controllers or server are not
available. I'm not sure what could have happened, but it looks as
thought one direction of the trust has been compromised. Any thoughts
would be greeeaaat!
Thanks,
Blair
Users from one domain(A) login to a Terminal Server on another domain(B)
with ID's created from domain B(It's just earsier this way, considering
the application config). These user id's are members of a global
security group, that has rights to print queues residing in domain A. So
in their TS session, they are attaching to printers that they would
normally use in their local environment. Anyway, all of the printers
that have been defined for them, now have a status of: "Opening", or
"Access denied, Unable to Connect", or just "Unable to Connect". I'm
thinking that there is perhaps a trust issue. Users on domain B can
connect to shares created on domian A, but it seems when we try to do
the opposite, it says that domain controllers or server are not
available. I'm not sure what could have happened, but it looks as
thought one direction of the trust has been compromised. Any thoughts
would be greeeaaat!
Thanks,
Blair