Problem connecting to 2nd domain
I've got 2 servers each one their own domain (yes I know it's not ideal but I'm kinda stuck with this setup for now!). One is running 2k3 server , one running 2K server and the last is running NT server. They are all trusted with each other. All users log on to the 2K domain and they have various drives mapped to each of the 3 servers and this enables them to access network resources and networked applications. Normally this is fine, however the 2K server is having problems accessing the 2k3 server.
One the NT and 2k3 server I can see the 2K server and browse it's shared resources, but on the 2K server I can see the other 2 servers in network places and I can browse the NT server fine. But if I try to browse the 2K3 server I get a window up asking for a network username and password for that domain. This password box also comes up when users try to access a networked application that resides on the 2K3 server.
I've tried rebooting the 2K server and also restarting the netlogon service but the problem is stil there. I don't know if it's a DNS or Trust problem, or something else, but it's pretty critical. Any suggestions folk?
One the NT and 2k3 server I can see the 2K server and browse it's shared resources, but on the 2K server I can see the other 2 servers in network places and I can browse the NT server fine. But if I try to browse the 2K3 server I get a window up asking for a network username and password for that domain. This password box also comes up when users try to access a networked application that resides on the 2K3 server.
I've tried rebooting the 2K server and also restarting the netlogon service but the problem is stil there. I don't know if it's a DNS or Trust problem, or something else, but it's pretty critical. Any suggestions folk?
ASKER
Nope, still no joy doing that.
I have fixed it by rebooting both servers, removing the trust and re-instating it. All works fine now, but I'm fairly sure that was a sledgehammer for a nut situation!!!
I have fixed it by rebooting both servers, removing the trust and re-instating it. All works fine now, but I'm fairly sure that was a sledgehammer for a nut situation!!!
not always! windows can be funny....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
when you enter credentials, are you able to access the shares?
Cheers!