RCP Server Unavailable

[rkerr]

Hi All,

I am running Active Directory on w2k servers in mixed mode with a one way trust relationship running between 2 domains, each with their own Active Directory.
When browsing the network from a server in the untrusted domain and then trying to access resources on a server in the trusted domain using logon credentials for the trusted domain I get the message 'RPC server is unavailable', I have tried deleting the WINS cache from both domains and also set my DNS servers to forward to each other to see if that would help, I have also checked the RPC service properties and the login details and it all seems to be correct.
Does anyone have any tips on resloving this?, would deleteting the trust relationship and recreating it help?
Any help greatly appreciated

 

[rkerr]

Apologies, obviously not concentrating, should be RPC Server not RCP........

 

[GlenJohnson]

Two schools of thought come to mind. Can you do a tracert from the untrusted to the trusted? Just want to see if you can get through physically. Second, try setting the dns to point to themselves instead of each other. DNS can cause a lot of problems in this area. Make sure all is well.

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin feel free to join the Tek-Tips in Chicago, Illinois Forum.

TTinChicago
Johnson Computers

 

[rkerr]

Glen,

I can do a tracert from the untrusted to the trusted, I have just pointed the DNS servers to themselves and am waiting for the changes to synchronize around our sites, this problem seems to be intermittent as well, this morning I could connect to remote resources for a short time but am now getting the same message as previously.
Our gateway of last resort(ISA Server) is also in the list of DNS forwarders for the domain.
Is this all pointing to a more serious DNS issue on the network?
Thanks
Rob

 

[GlenJohnson]

this problem seems to be intermittent as well, this morning I could connect to remote resources for a short time but am now getting the same message as previously

Can you locate anything that may have changed? Check your logs just before and just after you could connect. See what changed to make it where you couldn't connect.

Is this all pointing to a more serious DNS issue on the network?

Still a bit early to tell, but I wouldn't worry yet. Good luck.

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin feel free to join the Tek-Tips in Chicago, Illinois Forum.

TTinChicago
Johnson Computers