Problem with different Active Directory server and Internet Gateway

shogyn · 06-05-2007, 02:59 AM

Hi!
We just received a new internet connection at our office (in northeastern Cambodia). Before installing the new connection our network configuration was the following:
- Win 2000 server with Active Directory (domain controller), DHCP server, DNS server, etc.

The new internet connection does not go through the server, but through a router on the network. In order for the clients to access the internet connection I had to use the router as DHCP server (or set it as primary default gateway in the DHCP server on the win 2000 server). When I do that the network gets very strange. Log ins go very slow, some people can't even log in at all.

Can somebody help me? The solution I think about is to use the server as gateway and DNS server, but for all names the server DNS do not recognize, use another gateway and DNS servers (the router and the internet DNS servers). But I do not know how to implement this.

Best regards, Jeremia

shogyn · 06-05-2007, 08:58 PM

Hi!
I finally found the solution myself with some hints from others. Here is my complete config:

1. Use the server as DHCP server (because it's mostly easier to set the settings from here).

2. In the DHCP server set the following options:
003 Router: [Internet router IP]
006 DNS Servers: [Win server IP], [ISP DNS server 1], [ISP DNS server 2]

(Adding the ISP DNS servers here lets the clients access the internet even if the server is down, but the network and router is up)

3. In the DNS server on the Win server:
- Right click on the server
- Choose tab "Forwarders"
- Click "Enable forwarders"
(If this is not possible, see point 4 below)
- Add the ISP's DNS servers to the IP address list

4. If you can not "Enable forwarders" on the server DNS in point 3:
The problem is that the DNS server thinks it is a ROOT (top) DNS server which do not need to ask anyone above for help with DNS lookups. This is mostly not the case, why we need to tell the DNS server that it isn't a ROOT DNS server.
- Expand the Win server
- Expand "Forward Lookup Zones"
- Delete the folder named with a dot (".")
- Restart the DNS server and try to follow the instructions in point 3 again.

Best regards, Jeremia

06-05-2007, 02:59 AM	#1 (permalink)
shogyn Registered User Join Date: Jun 2007 Posts: 8 OS: Windows XP	Problem with different Active Directory server and Internet Gateway Hi! We just received a new internet connection at our office (in northeastern Cambodia). Before installing the new connection our network configuration was the following: - Win 2000 server with Active Directory (domain controller), DHCP server, DNS server, etc. The new internet connection does not go through the server, but through a router on the network. In order for the clients to access the internet connection I had to use the router as DHCP server (or set it as primary default gateway in the DHCP server on the win 2000 server). When I do that the network gets very strange. Log ins go very slow, some people can't even log in at all. Can somebody help me? The solution I think about is to use the server as gateway and DNS server, but for all names the server DNS do not recognize, use another gateway and DNS servers (the router and the internet DNS servers). But I do not know how to implement this. Best regards, Jeremia

06-05-2007, 08:58 PM	#2 (permalink)
shogyn Registered User Join Date: Jun 2007 Posts: 8 OS: Windows XP	Re: Problem with different Active Directory server and Internet Gateway Hi! I finally found the solution myself with some hints from others. Here is my complete config: 1. Use the server as DHCP server (because it's mostly easier to set the settings from here). 2. In the DHCP server set the following options: 003 Router: [Internet router IP] 006 DNS Servers: [Win server IP], [ISP DNS server 1], [ISP DNS server 2] (Adding the ISP DNS servers here lets the clients access the internet even if the server is down, but the network and router is up) 3. In the DNS server on the Win server: - Right click on the server - Choose tab "Forwarders" - Click "Enable forwarders" (If this is not possible, see point 4 below) - Add the ISP's DNS servers to the IP address list 4. If you can not "Enable forwarders" on the server DNS in point 3: The problem is that the DNS server thinks it is a ROOT (top) DNS server which do not need to ask anyone above for help with DNS lookups. This is mostly not the case, why we need to tell the DNS server that it isn't a ROOT DNS server. - Expand the Win server - Expand "Forward Lookup Zones" - Delete the folder named with a dot (".") - Restart the DNS server and try to follow the instructions in point 3 again. Best regards, Jeremia