It is better to have DNS in the office B. Since you have VPN, it is recommended to setup WINS. This search result may help,
Name resulotion on VPNSymptom: You have a Windows 2000/2003 server is configured as VPN running DNS, WINS, you may experience some connection issues. 1) the internal computers ...
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<email@example.com> wrote in message news:firstname.lastname@example.org oups.com...
This issue has me ripping my hair out, it is very frustrating...
We recently purchased a Dell workstation with Windows Vista Business
Upon connecting this workstation to the network, I am unable to join
it to the domain.
We have two offices that fall under the one domain safe-trac
It does not have a FQDN, well that is it's FQDN, it is a domain that I
did not setup.
In one office, office A, is server A, which is a Domain Controller
with DNS installed.
In the other office, office B, is server B, which is also a Domain
Controller, but does not have DNS installed.
I have configured our Vista workstation with a static IP address in
office B, with DNS set to server A and the same gateway as server B.
The office are connected via an IPSEC VPN.
No other odd domain problems have been experienced, both server A and
B have Windows 2003 installed.
I have had no other problems joining WinXP workstations to this
When I attempt to join the Vista workstation to the domain, I get the
following error message:
"An Active Directory Domain Controller for the domain safe-trac could
not be contacted
Ensure that the domain name is typed correctly"
In the debug\dcdiag.txt file is the following:
"The domain name safe-trac might be a NetBIOS domain name. If this is
the case, verify that the domain name is properly registered with
If you are certain that the name is not a NetBIOS domain name, then
the following information can help you troubleshoot your DNS
DNS was successfully queried for the service location (SRV) resource
record used to locate an Active Directory Domain Controller for domain
The query was for the SRV record for _ldap._tcp.dc._msdcs.safe-trac
The following AD DCs were identified by the query:
Common causes of this error include:
- Host (A) records that map the name of the AD DCs to its IP addresses
are missing or contain incorrect addresses.
- Active Directory Domain Controllers registered in DNS are not
connected to the network or are not running."
Now what I can't understand from this is that it finds the Domain
Controllers, yet cannot contact them!!!!!
>From the Vista workstation, I can nslookup both servers and of course
I have also tried to create a computer account in the AD and try to
add the computer to the domain the 'other' way, to no avail, same
An important note, but should make no difference is that office A and
office B are in different subnets. But this has proved to be no issue
when adding WinXP workstations to the domain.
Any ideas on where I can start to diagnose this?