> No especially big deal -- you only have to be able to
> route freely to ignore the routers for everything except
> browsing which is a practical requirement for WINS
> Servers.
>
> "Mark" <me[ at ]mymail.com> wrote in message
> news:On%23QH4QiHHA.4904[ at ]TK2MSFTNGP05.phx.gbl...
>> Looking for some step-by-step instructions for accomplishing the
>> following.
>>
>> I have 2 locations.
>>
>> Location #1 has a Windows 2003 Server w/AD. It's IP address is
>> 192.168.1.10
>> Location #2 has a Windows 2003 Server (without AD). It's IP address is
>> 192.168.0.10
>> The 2 locations talk to each other through a secure VPN tunnel (SonicWall
>> Firewall boxes).
>>
>> I want to be able to join the server in location #2 to the domain at
>> location #1. Server #2 has Server #1's ip address for it's primary DNS. I
>> can ping the servers in both directions but when I try to join the domain
>> it says that "a domain controller for the domain could not be contacted".
>
> That's almost certanly a DNS problem if you can route fully.
>
>> DNS issue maybe?? Any ideas?
>
> Yes. If it is not routing.
>
> Where are you DNS servers? Do both (all of) the DNS Servers know
> how to find ALL of the records for your domain, all DCs?
>
>
> --
> Herb Martin, MCSE, MVP
>
http://www.LearnQuick.Com> (phone on web site)
>