installed DHCP, DNS on windows server 2003 network - then installed NAT but not getting internet on clients?

Question

I have win 2003 server network with DHCP & DNS installed n working - then i wanted internet on client computers - i installed NAT but not able to get internet on it. Please guide me how to install or steps to do it?
internal ips by dhcp scope 200.168.1.1 - 200.168.1.254 (working fine). not able to figure out how to set the 2nd nic in a way that it provides internet to the clients - plz help

Answer 1

First, you are using the wrong IP range - 200.168.1.1-254 is NOT a reserved private range. You could have problems accessing some web sites if you use that address range. You should be using any of the following ranges:



192.168.x.x

172.16-31.x.x

10.x.x.x



All the above ranges are reserved for private IP addresses and are considered non-routeable. Meaning even if you posted them here, no one can hack into your network UNLESS you posted your public IP address (the one given to your by your ISP).



Second, what are your Gateway settings on each NIC? Only the NIC that is connected to the internet gets a gateway - the other should be left blank. (How does the packet know which gateway to use when it has two to pick from?)



Third, when you setup NAT, HOW did you setup NAT? You should have configured Routing and Remote Access (RRAS). Assuming your network settings were all set correctly, this should have been an easy, wizard driven, configuration.



Finally, WHY would you ask for help HERE? Yahoo Answers does not provide a forum that encourages two way communications. So you can answer questions asked of you - but I'm never notified that you did... so I probably won't see this again until I check it for voting next weekend... A FORUM that encourages problem resolution, such as www.tek-tips.com or www.experts-exchange.com or a newsgroup.

Answer 2

I found this maybe its a help to you:



Now to answer your question..your question is probably "Do I have to shut off DHCP on the ISP supplied gateway?" The answer is "NO". Matter of fact, you're safer to leave it on. That DHCP service will be broadcasting on the WAN interface of your server..which is not part of your LAN, the server will not pass that DHCP on through its routing.



What I do before running the ICW....is give each NIC the IP that I want. Your server has 2x NICs you say. What I do, is right click each on in my Network Properties window..and re-name them accordingly...by default you'll have something like Local Area Connection 1 and Local Area Connection 2. The NIC going to the broadband connection...I'll rename WAN. The NIC going to the switch for the local network...I'll call LAN.



I then assign them IP's based on how I wish to setup my network. The WAN NIC...I'll assign it a static IP address that's within the range of the broadband router. Say your ISP supplied gateway is..192.168.1.254...give your WAN NIC an IP in that range...but outside the gateways DHCP pool. Meaning..if the ISP supplied gateway runs DHCP...say it hands out addresses starting at 2 or 100 or whatever...just pick an IP that it would not normally hand out. Since you'll only have 1x device connected to it...you're pretty safe. Pick something like 192.168.1.11.



Now for your LAN side...you'll need a different IP range naturally, so do something like 192.168.3.11 for the LAN NIC. You only have to fill in the IP and subnet mask....when you run the ICW...it will fill in the necessary gateway, DNS, and WINS...and should setup the proper binding provider orders.



Reason to leave DHCP on in your ISP gateway? Just as a safety net. It's harmless leaving it on, since it's not on your local network. And if you "forget" the settings 'n what not...you can just flip your WAN NIC to obtain auto..and start over again.



So normally it's true...in most cases (except for larger networks with active directory)...you only want 1x DHCP service on a network. With Active Directory and multiple servers..you can have a couple of DHCP services...AD will spread the load there, they won't compete.



Once you talk about a multi-homed server though, such as in this case..we're technically talking about 2x separate networks here..the WAN NIC, and the LAN NIC. The router can run DHCP for the WAN interface..even though he won't really use DHCP there, but it's harmless and better to leave it on. And the server will run DHCP for the LAN interface.

Answer 3

Just as Mark T said. You want to ROUTE across those cards. Not NAT across them.



Though, honestly. a better solution is to spend $100 on a switch, and connect them that way without going across the server. It will remove the burden and overhead of routing off the server, which can be significant.

Answer 4

Use the "Server Management Tool" and run the wizard for "routing and remote access".

Answer 5

HAV U TTRIED REINSTALLIN THE CARD SO A BOOT RECOGNISES IT? OTHERWISE WAS GONNA PASTE IN SAME AS ABOVE ETC