Discussion Locked

NAT in Win2k Server

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have two Win2k seervers running. They are server01 & server02. Server01 is the Domain controler. It is running dhcp and dns also. It has two nic cards installed with static ip's assigned two both. I am trying to get NAT to work. It's been enabled through RAS. My problem is my global nic gets out to the internet just fine. My local nic which server02 is connected to is able to ping by ip, but not by name. On server 02 in the networking properties box I have "Obtain ip from dhcp server" selected and also "Obtain DNS from DHCP server" selected. Yet server01 can browse the web and server02 can't. Server02 can ping ip addresses on the web but is unable to ping for example www.yahoo.com. When I manually enter the dns server into the dns fieldeverything works. But I don't think I should have
to do that. So please someone help me stop the INSANITY!!!!

10 replies

by quintar51

You should use static IP addresses for servers. That will also mean that you'll need to specify the DNs addresses. You did it for server1, why not server2 as well?

Technically, you should still obtain DNS server addresses from the DHCP server, with the way you have it setup now. Try checking your scope. Did you specify DNS in the scope options? If not, do so, and it should work.

by cg it

Don't use obtain automatically IP and DNS on server #2. Specify a IP address for server #2. Specify the IP address of server #1 as the DNS server that server #2 uses to resolve names to IP addresses [provided server #1 is a DNS server]. Also specifiy server #1's WAN NIC IP address as the gateway in server #2's network properties. [Can't get out without specifing the gateway].

[Note: It's my understanding that NAT and DHCP can't be used together on the same segment for client IP address assignment. NAT is for clients who access the internet using a static private IP address scheme for public access which hides the true domain IP address. DHCP on the other hand assigns IP's to clients [a dynamic IP scheme]. When DHCP clients accesses the internet they do so showing the domain IP address not the DHCP IP address assigned by DHCP [unless there is a firewall between the WAN and LAN or a DSL/Cable router with DHCP [and DHCP is used by the router to assign IP's to clients connecting to the"ROUTER"]. Then what is seen on the internet is the IP address the router assigned to "it's clients" [the whole domain if only 1 server is connected to the router] not the ISP IP address assgined to you. [This is regardless of NAT or DHCP on the LANside].

by cg it

Questions: what the devil is server #2's role? BDC server? DHCP server? Web server? Email server? File server? FTP Site server? SQL server? Is the second server for a subdomain? Are you trying to cluster DC servers? What O/S(s) are being used? If W2K, is AD being used? If so did you replicate AD to the second server if the second server is a BDC?

by avswamy

NAT and DHCP can be used together, there is no problem on using both, but for dns where you said you have configured to get from dhcp it also can be used, but not recommended--give the dns of your domain ip in dns. And for your problem is there is no configuration for forwarding to external(ISP-DNS), configure forwarding the dns traffic for external traffic which is not resolved by this domain.But you should get one problem forwarding in dns server properties which is disabled after intalling active directory, you have to do it before installing active directory.
I hope this will help you.

This discussion is closed to new replies.