I finally was able to spend time and dig up error 1355 which is a SID error. Whenever you remove a trust relationship you have to bounce the netlogon service to reset permissions on the sysvol. After we did that all was well.
We came across the errors put out by netdom reset command to reset the key between the domains. From: Miller Bonnie L. [mailto:mille...@mukilteo.wednet.edu] Sent: Friday, February 20, 2009 10:32 AM To: NT System Admin Issues Subject: RE: Error on Trust Is this an external trust? I always need WINS or lmhosts entries whenever I have to work with this. Here is an example of the lmhosts file on DC1. DC1 is in Domain A and DC2 and DC3 are in domain B. DC2 would also have a similar file pointing back to Domain A. x.x.x.1 " DOMAINBNAME \0x1b" #PRE x.x.x.1 " DOMAINBNAME \0x1c" #PRE x.x.x.1 dc2servername #DOM: DOMAINBNAME #PRE x.x.x.2 dc3servername #DOM: DOMAINBNAME #PRE -Bonnie From: Benjamin Zachary - Lists [mailto:li...@levelfive.us] Sent: Tuesday, February 17, 2009 10:57 AM To: NT System Admin Issues Subject: Error on Trust Hey all, I have 2 sites setup with a vpn and trust. The vpn went down for about 12 hours yesterday and the trust seemed to expire or break in the same time. When I goto establish it again or try to validate I get an error that the trust passwords need to be reset, I click Yes and then get the specified domain doesn't exist or could not be contacted. I have it working where as I can ping domain1.local from this side and I get the IP of the DC over there, and vice versa, we also re-loaded DNS zones on both sides and that was successful. Any other ideas? Event logs gave some generic security account error, and told me to take my dc and remove it from the domain and rejoin it, which obviously isn't going to be an option J Thanks ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~