setup of NAT with DHCP & DNS in server 2003?

Question

I have a machine running Windows Server 2003 (with internet working on it), which I want to be my router/dhcp server for my small network. I have a DSL interent provider.

My Server is already the DHCP server and the LAN is working perfectly. All computers can talk to each other, as well as the server.

There are two NICs in the server. One connects to my switch on the lan side (call it the LAN NIC), the other goes to the DSL modem (call it the WAN NIC). The LAN NIC has a static IP, the WAN NIC has an automatic IP (being provided by the DSL Router/modem)

Then I install Routing + Remote Access, setting it up as a "NAT", and selecting the WAN NIC as the network device that has the internet. Turned it on, everything seems fine. The DHCP server is allocating IP's.

My SERVER has the internet now (as it did before), and does all the LAN based routing for my entire network just fine.

PROBLEMS:
1) Client's cannot connect to the internet.

2) DSL provider provides two DNS servers. but how do I configure DHCP to use those addresses?

Please guide - thanks

Answer 1

Set the Gateway and DNS settings in DHCP to the server LAN card. Go into DNS applet and put your ISP DNS servers in "Forwarders"

Answer 2

You can easily check if the problem is DNS by putting an IP address in a client computer's browser. Eg 74.125.67.100

If it works then the problem is DNS. If it doesn't work you have another problem.



You should be able to tell your client PCs to use the address of the DSL modem as a DNS Server. The Server2003 should route the DNS request on to the modem.

Answer 3

Been a LONGGG time since I setup a server over an appliance of some sort to do my routing for me, and I wouldn't do it for a client. It's too clunky of a solution compared to what's out there on the market for super cheap nowadays.



But hey, let's have some fun!



First off, if you manually add the DNS settings to your client systems, do they have internet? (alternatively you could add them to the DHCP as dns servers after the server ip address)



It may be that you only need to add a DNS forward to your server. Google that and you'll get better instructions for doing so if everything else is setup right.. which it looks like to me you know what your doing and it probably is.

Answer 4

in simple terms as Mark T mentioned. you pick to path in the time of those enjoying cards. no longer NAT in the time of them. even with the undeniable fact that, honestly. a greater applicable answer is to spend $a hundred on a swap, and connect them that way without going around the server. it is going to eliminate the burden and overhead of routing off the server, which could be substantial.