DNS help needed

Hi all...I have a 2003SBS that I just ramped up as the Domain Controller for a company that was previously networked via workgroup.  They have 2 remote offices connected via an always on VPN (Linksys RV016 at main office, RV041 at remote locations).  I am using DHCP and DNS on the server, and have switched off DHCP on the RV016.  The remote offices are still using the Router DHCP.   Everything is fine at the main office, but I want to join the PC's at the romote office to the domain.  While I can ping the IP address, I can't resolve the server name across the VPN.  Here are the IP scopes
Main Office 192.168.0.x, Remote office 1: 192.168.150.x, remote office2: 192.168.1.x
I don't think the VPN will work if I make the remote offices in the same scope of the main office...so how do I get 192.168.150.x computers to resolve names on 192.168.0.x???
JDCTECHAsked:
Who is Participating?
 
bhnmiConnect With a Mentor Commented:
Right click my computer on the server and select manage. Expand services and expand IIS. if you right click on default website and select properties you will get a dialog box. There will be a directory security tab here. This is where you can change permissions to the internal website. Be careful what you do here, you can hose it. I would recommend backing it up first.
0
 
bhnmiCommented:
set the DNS server in the dhcp scope at the remote office to the IP  address of your domain controller. All the AD information is at the local site living on the DC.
0
 
Alan Huseyin KayahanCommented:
   Hi JDCTECH
        A client has to have the IP of the domain controller (DNS server) of the domain you want to join it as the preferred DNS server. So, you either have to assign the IP of DC is main office as the preferred DNS server for client is Remote office, or if remote has a DNS server, add the main office's domain controller IP as forwarder.

Regards
     
0
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

 
JDCTECHAuthor Commented:
OK, I was able to configure the remote router to point the client DNS IP to the server first, then the ISP second.  I can ping the server by IP, still not by name.  Here is my IPCONFIG /all
IP 192.168.150.102
Sub 255.255.255.0
GW: 192.168.150.1
DNS1: 192.168.0.5  (this is the 2003SBS)
DNS2: 24.92.226.12
I get 'Ping request could not find the host 2003sbs...'
0
 
bhnmiCommented:
Use the command nslookup at the command line.

What does it say for server?
0
 
bhnmiCommented:
I would also remove the ISP DNS server for the interim while we try and get this working.
0
 
JDCTECHAuthor Commented:
nslookup shows 192.168.0.5 2003sbs.domain.local
When I ping 2003sbs no reply I get 'non-existant domain'
This is interesting...when I try to browse to 192.168.0.5/connectcomputer I get:
HTTP Error 403.6 - Forbidden: IP address of the client has been rejected.   How do I unblock addresses in this IP range?
0
 
bhnmiCommented:
enter the fqdn not the host name. ie: 2003sbs.domain.local when trying to join the domain.
0
 
bhnmiCommented:
You can unblock the IP address range by adding the IP address range of the remote site to the directory security for the virtual server in IIS that handles the adding a computer.
0
 
bhnmiCommented:
on the post above the last disregard. You need to enter the fqdn for the domain, domain.local when adding it, not just the domain.
0
 
JDCTECHAuthor Commented:
OK, please elaborate on IIs virtual server instructions

Thanks, Dan
0
 
JDCTECHAuthor Commented:
Thanks for your help, sorry to take so long closing.  I went with a different approch in the end
0
All Courses

From novice to tech pro — start learning today.