Lost in the VPN

  • Thread starter Thread starter nkingcade
  • Start date Start date
N

nkingcade

I am attempting to join machines to a remote DC across a
VPN. The machines can't find the DC. I have done
everything, including a static route to the DC. I can't
pass NetBios broadcasts thru the routers. I am attempting
to find the DC through the DNS process. I suspect that my
config is not correct. In addition, I don't see _msdc,
_tcp, ...etc in the active directory integrated dns server
app that I loaded.

Neal
 
In
nkingcade said:
I am attempting to join machines to a remote DC across a
VPN. The machines can't find the DC. I have done
everything, including a static route to the DC. I can't
pass NetBios broadcasts thru the routers. I am attempting
to find the DC through the DNS process. I suspect that my
config is not correct. In addition, I don't see _msdc,
_tcp, ...etc in the active directory integrated dns server
app that I loaded.

Neal
Click to expand...

Can you post an unedited ipconfig /all for the DC and the actual Domain name
from AD Users & Computers?
I need to verify you don't have a disjointed name space and that you have
TCP/IP configured correctly.
 
Kevin,

I most certainly will. I will be back to the network in a
couple of hours. Thanks.

Neal
 
The clients at the remote site need to point at the DC running DNS for the AD ONLY. Do not point them at any other DNS server.
Alternatively, you could setup a member server at the remote site with DNS on it. Configure a secondary of the AD domain on
this DNS server and clients at the remote site could then use the local DNS server for DNS. This would be a much more efficient
method.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.
 
Mike,

I don't have the hardware to place a secondary at the
remote sites. One of the remotes only has four PC's.
However, I will point them at the remote DNS/DC. Thanks
abunch.

-----Original Message-----
The clients at the remote site need to point at the DC
Click to expand...
running DNS for the AD ONLY. Do not point them at any
other DNS server.
Alternatively, you could setup a member server at the
Click to expand...
remote site with DNS on it. Configure a secondary of the
AD domain on
this DNS server and clients at the remote site could
Click to expand...
then use the local DNS server for DNS. This would be a
much more efficient
method.

Thank you,
Mike Johnston
Microsoft Network Support
Click to expand...
confers no rights. Use of included script samples are
subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all
Click to expand...
responses to this message are best directed to the
newsgroup/thread from
 
Back
Top