I have a Server 2003 pc with 2 NICs one is connected to my ISP while the other is connected to my private network. I have DHCP installed and NAT setup to share the internet. My client pcs get the local IP for the network but cannot connect to the internet. I googled this problem and can't find any info that will work.
You have setup the Routeing RRAS Roles too correct? http://articles.techrepublic.com.co...
Or are your proxying your Internet Trafic?
"NAT setup"? You only went into the registry, correct?
No "NAT and basic firewall" through RRAS. I was just following a guide online on how to set up 2003 as a NAT router. I went to RRAS and did the setup wizard and chose the "Network address translation" option which is NAT and it makes it share the public IP but for some reason it is not doing that.
How are you cabled? Like so? Internemodem<>router<>server nic1[server]server nic2 lan<>pcs
Post an ipconfig /all from a workstation and the server for review. If no router change the first octet on the internet facing nics ip address to xxx
Internemodem<>server nic1[server]server nic2 lan<>router(DHCP forwarder)<>pcs Server ipconfig:
Windows IP Configuration Host Name . . . . . . . . . . . . : ryans-server Primary Dns Suffix . . . . . . . : BelNet.net Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : BelNet.net hvc.rr.com Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8169 Gigabit Ethernet Adapter Physical Address. . . . . . . . . : 00-0A-CD-1A-2F-2F DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.0.1 Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : hvc.rr.com Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection Physical Address. . . . . . . . . : 00-08-02-CA-90-EE DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 98.15.202.166 Subnet Mask . . . . . . . . . . . : 255.255.248.0 Default Gateway . . . . . . . . . : 98.15.200.1 DHCP Server . . . . . . . . . . . : 10.91.96.1 DNS Servers . . . . . . . . . . . : 127.0.0.1 208.67.222.222 208.67.220.220 Lease Obtained. . . . . . . . . . : Friday, April 16, 2010 2:49:58 PM Lease Expires . . . . . . . . . . : Friday, April 16, 2010 3:49:58 PMWorkstation ipconfig:
Windows IP Configuration Host Name . . . . . . . . . . . . : RYAN-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce Networking Controller Physical Address. . . . . . . . . : 00-26-18-08-F5-FF DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::6069:27aa:26ed:c870%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : 192.168.0.2 DHCPv6 IAID . . . . . . . . . . . : 234890776 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-09-E2-C8-00-26-18-08-F5-FF DNS Servers . . . . . . . . . . . : 192.168.0.2 NetBIOS over Tcpip. . . . . . . . : EnabledAlso for some reason the DHCP server is not handing out the IPs so I have to edit the NIC on the workstation to use a certain IP. Anyway I am able to access local things on the network but the internet is not shared for some reason.
Why this address for your workstation... "Default Gateway . . . . . . . . . : 192.168.0.2"
Shouldn't it be 192.168.0.1 because that is the IP of your server. What is on 192.168.0.2?
P.S. I noticed...
"DNS Servers . . . . . . . . . . . : 192.168.0.2"
So do you have two severs one for your gateway and another for your DNS and that is what is on the .0.2 address? If so can you give us an IPCONFIG of that servers NIC too?
192.168.0.2 is the DHCP forwarder. It is like a switch.
a dhcp helper forwards dhcp request/ack thru a router. your server is the dhcp provider for the lan. You are not passing dhcp from your router thru the server so this last statement makes no sense. It appears the workstation has the wrong ips for gateway and dns. Both should be your server at 192.168.0.1 unless you have a ms dns server at 192.168.0.2. Do you have a second server? Actually both should be runing dns server and I see no dns entry on the static assignment on the server.
So I assume you have the DNS forwarder on that box too. Any ways try changing the default gateway on your client computer and see if it fixes your problem. You might also want to do a TRACERT YAHOO.COM to see what path the packets are tacking through your network.
You have an interesting Topology there. Can you explain how the DHCP forwarder fits into your network diagram. does it rout through the server you are trying to setup as a router or is it physically connected to another network?
oops, never mind look at what Wanderer posted because yes even with the Gateway being set right it still will not work unless you get you DNS server setup right.
ok wait a min lol i think i found the problem. My router can be made into a switch and i didn't turn on all the settings i had to to make it a switch. I will test it and report back on if it worked or not. I will also change the gateway and dns stuff to the server.
Ok I made the dns and default gateway 192.168.0.1 and fixed the router problem but it still didn't share the public IP. I even tried to plug the workstation directly into the server lan nic and that didnt work either.
"I even tried to plug the workstation directly into the server lan nic and that didnt work either." Well that's not going to work unless you use a Crossover Cable.
as for your issue I am guessing that you are having a DNS problem. Did you try pinging YAHOO's IP address insted of their FQDN? If it pings then it is not a routing issue but a DNS issue. If it does not ping then it is a routing issue. Also, I recommend to do a trace route to see how the packets are flowing through your topology.
Ad Choices