Reply to thread

Message: [QUOTE="Mike Shepperd, post: 9643780"] I've always believed that you need DNS working for it to function, but I haven't tried using detailed HOSTS files... If you analyze the network traffic, that would likely point you in the right direction. Start an analyzer like ethereal on the DC in Domain B when you reproduce the problem. When you see the error, stop the capture and review the traffic. You should see what connections are actually made and what fails. Find out what it's looking for, or what machine it's trying to contact. I believe that the problem is that you're only resolving hostnames, not the FQDN of the Active Directory specific DNS entries. Look in your DNS under the _MSDCS folder and you'll see that there are DC specific entries that you're not likely to have (and are not likely to work) in the HOSTS or LMHOSTS. Secondary zones has always been the way to go. Good luck and post back if you need help with further analysis. Mike Shepperd Sunfire Solutions LLC Seattle, WA [/QUOTE]