NAT in Windows 2000 Server

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

Guest

Let me see if I can describe this accurately... I have a Dell server with
two NIC cards. One card is for the Internet connection and has a static IP,
DNS server numbers assigned, etc. The server sees the Internet just fine.
My end goal is to make this server into a router by using NAT. However, I
set DHCP up before I set up NAT and assigned the other NIC card to
192.168.0.1 and a subnet of 255.255.255.0 which worked fine. My client
computers were being assigned IP addresses and the world was right. So, I
then set up NAT in order to "link" the two NIC's and allow my clients to surf
the Internet. I followed the instructions on how to do this right off the
Microsoft KnowledgeBase site. I clicked on "Automatically assign IP
addresses by using DHCP" since I was already using DHCP and also clicked on
"Clients using DNS" because there are two DNS server addresses assigned by
our ISP (Nuvox). I didn't change the DHCP settings or the network card
settings (which has to gateway IP typed in as the directions stated). Now,
my clients are assigned an IP address and the correct subnet but no gateway
and are unable to surf the Internet. However, I can go in and assign a
manual IP address 192.168.0.200, subnet 255.255.255.0, gateway 192.168.0.1
(the LAN NIC card IP address), and the DNS server addresses, and I get the
Internet on the client computers. But I don't want to manually assign every
client since these clients will be wireless and be getting on via wireless
gateways! Keep in mind though that I'm trying to get all of this to work
with a wired laptop for now so that the wireless issue is not in the picture
yet. What am I doing wrong that causes my laptop to not obtain a gateway or
DNS numbers when set to obtain an IP address automatically??? This has me
stumped!
 
In your DHCP scope options add 003 Router to pump out the 192.168.0.1
gateway to the clients.

If this server is or becomes a domain controller, then it and all clients
should point to 192.168.0.1 for DNS, and you would use the server's DNS
console to configure Forwarders to the ISP DNS servers.

Doug Sherman
MCSE, MCSA, MCP+I, MVP
 
Since everything is already set up perfectly for it, why not just uninstall
or disable the DHCP service, and use ICS instead of NAT. DHCP will be set up
as a part of the process, and 192.168.0.0 is the default LAN network for
ICS.

....kurt
 
Back
Top