Sign in
Microsoft.com
 
Windows Server TechCenter
 
 
 
Windows Server TechCenter > Windows Server Forums > Directory Services > Joining remote site to domain - DNS issues
Ask a questionAsk a question
Search Forums:
 

AnswerJoining remote site to domain - DNS issues

  • Tuesday, November 03, 2009 7:29 PMclarkebc Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I have a Windows 2003 Server running a single domain on a single subnet.  (192.168.8.x)  There is a remote office a few blocks away that is connected via hardware VPN through the company's ISP (Rainbow Broadband)  The remote office uses the (192.168.10.x) subnet.  From a remote office PC (at IP 192.168.10.121), I can ping PC's in the main office location by their IP addresses (192.168.8.x) but there is no DNS resolution, I cannot ping by machine name and, most importantly, I cannot join to the domain as the PC in the remote location cannot locate the domain controller in the main office.  I tried adding a reverse lookup zone in AD on the server for the remote subnet (192.168.10.x) but that doesn't seem to resolve the problem.  There is no server at the remote location, just 4 PC's currently connected in a Workgroup environment.  Any ideas as to how I can get them to join to the domain and see the PC's in the main office?  Thanks for your help.
     

Answers

  • Tuesday, November 03, 2009 7:41 PMMarcin PolichtMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Make sure that computers in the remote office point to the DNS server in the main office that hosts your AD zones as their primary DNS server - and disable any port filtering on the VPN link (in particular any that would block DNS/AD related traffic)...

    hth
    Marcin

     
  • Tuesday, November 03, 2009 11:46 PMJorgeSilvaMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    I have a Windows 2003 Server running a single domain on a single subnet.  (192.168.8.x)  There is a remote office a few blocks away that is connected via hardware VPN through the company's ISP (Rainbow Broadband)  The remote office uses the (192.168.10.x) subnet.  From a remote office PC (at IP 192.168.10.121), I can ping PC's in the main office location by their IP addresses (192.168.8.x) but there is no DNS resolution, I cannot ping by machine name and, most importantly, I cannot join to the domain as the PC in the remote location cannot locate the domain controller in the main office.  I tried adding a reverse lookup zone in AD on the server for the remote subnet (192.168.10.x) but that doesn't seem to resolve the problem.  There is no server at the remote location, just 4 PC's currently connected in a Workgroup environment.  Any ideas as to how I can get them to join to the domain and see the PC's in the main office?  Thanks for your help.

    - The DNS server used by your domain should be configured in those client machines. If you've problems with machines querying over WAN your DC at the Main Office, you may want to consider having a local DNS server on client's site. That DNs server hould have a copy of the DNS Zone for your domain at the main office.

    I hope that the information above helps you. This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.
     

All Replies

  • Tuesday, November 03, 2009 7:41 PMMarcin PolichtMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Make sure that computers in the remote office point to the DNS server in the main office that hosts your AD zones as their primary DNS server - and disable any port filtering on the VPN link (in particular any that would block DNS/AD related traffic)...

    hth
    Marcin

     
  • Tuesday, November 03, 2009 11:46 PMJorgeSilvaMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    I have a Windows 2003 Server running a single domain on a single subnet.  (192.168.8.x)  There is a remote office a few blocks away that is connected via hardware VPN through the company's ISP (Rainbow Broadband)  The remote office uses the (192.168.10.x) subnet.  From a remote office PC (at IP 192.168.10.121), I can ping PC's in the main office location by their IP addresses (192.168.8.x) but there is no DNS resolution, I cannot ping by machine name and, most importantly, I cannot join to the domain as the PC in the remote location cannot locate the domain controller in the main office.  I tried adding a reverse lookup zone in AD on the server for the remote subnet (192.168.10.x) but that doesn't seem to resolve the problem.  There is no server at the remote location, just 4 PC's currently connected in a Workgroup environment.  Any ideas as to how I can get them to join to the domain and see the PC's in the main office?  Thanks for your help.

    - The DNS server used by your domain should be configured in those client machines. If you've problems with machines querying over WAN your DC at the Main Office, you may want to consider having a local DNS server on client's site. That DNs server hould have a copy of the DNS Zone for your domain at the main office.

    I hope that the information above helps you. This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.