NAT configuration with AD

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have loaded Windows 2000 Server on two machines. Servers are networked with a Dell PowerConnect 2016 switch. In a workgroup setting, I enabled NAT on one of the servers. Server 1 is functioning as a DHCP server also. The other server, and an XP Pro box were able to successfully connect to the Internet over a broadband cable modem

Next I ran dcpromo and installed AD on server one with integrated DNS. Now I cannot get to the Internet from Server 2 or the XP box. I have network connectivity between all three PC's. I can ping the internal network and anything on the Internet. I just read another article in which the poster said he could not type the IP address in the web browser and reach a web site. Well I can do this from both Server 2 and XP Pro. Just cannot get their with a URL. I know it has to be DNS but what could it be? Went through all of the settings and everything is setup according to book and several knowledge base articles.

Any ideas?

John
 
Dcpromo will configure a root zone under your forward lookup zone. It's
represented by a " . " Delete it and restart the service.

John Kruskie said:
I have loaded Windows 2000 Server on two machines. Servers are networked
Click to expand...
with a Dell PowerConnect 2016 switch. In a workgroup setting, I enabled NAT
on one of the servers. Server 1 is functioning as a DHCP server also. The
other server, and an XP Pro box were able to successfully connect to the
Internet over a broadband cable modem.
Next I ran dcpromo and installed AD on server one with integrated DNS. Now
Click to expand...
I cannot get to the Internet from Server 2 or the XP box. I have network
connectivity between all three PC's. I can ping the internal network and
anything on the Internet. I just read another article in which the poster
said he could not type the IP address in the web browser and reach a web
site. Well I can do this from both Server 2 and XP Pro. Just cannot get
their with a URL. I know it has to be DNS but what could it be? Went through
all of the settings and everything is setup according to book and several
knowledge base articles.
 
That did the trick. Now comes the why. Why deleting the "root zone" fixes this problem.

John
 
A root zone is one method used by your server to resolve a name that cannot
be resolved locally. I don't know why 2000 puts this in automatically, but
when your server sees the root zone, name resolution stops.

With no root zone configured, name resolution requests go the root zones on
the Internet.
 
Back
Top