Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Win2K Server - NAT Help 1

Status
Not open for further replies.

rpz620

IS-IT--Management
Jun 7, 2002
12
US
I am having difficulty implementing NAT on my home network and permitting internet connectivity to any machine other than my Win2K server.

Setup is as follows:

Win2K Server
Private LAN NIC
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 198.6.1.4

Public NIC
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

PP adapter Verizon Online DSL:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interf
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : xx.xxx.xx.xxx
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : xx.xxx.xx.xxx
DNS Servers . . . . . . . . . . . : 151.202.0.84
151.203.0.84

I have both NAT and DHCP running on the same Win2K machine with and I am NOT using the NAT DHCP allocator. I am getting IP address info properly allocated to my clients using my private LAN NIC IP (192.168.0.1) as the default gateway. For some reason or other the translation is not being made and I am unable to get internet connectivity to any PC's connected to my switch off of the server.

Thoughts?
 
Win2K Server
Private LAN NIC
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 198.6.1.4


Why do you have 198.6.1.4 as a DNS for the Win2k Server.

Try using the DNS server on the Server itself like this:

Win2K Server
Private LAN NIC
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.0.1


Hope this helps,

Regards,

Akart
 
Thanks for the pointer. That DNS UNET's DNS...I changed it to the server itself to no avail. The problem is not resolving the name to IP as I have also attemted to ping IP's to no avail.
 
Can you do this on your server?

Type ipconfig /all in to the command line, highlight the text and click the top left of the open window and select copy. Then paste it in to this forum for a better look at your setup.

Akart
 
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : win2ksvr
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : ADMtek AN983 10/100Mbps Fast Etherne
t Adapter
Physical Address. . . . . . . . . : 00-02-2A-B4-25-D9
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 198.6.1.4

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Compaq NC3161 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-50-8B-77-17-B7
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

PPP adapter Verizon Online DSL:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : xx.xxx.xx.xx
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : xx.xxx.xx.xx
DNS Servers . . . . . . . . . . . : 151.202.0.84
151.203.0.84

C:\>
 
Ok, this worked on my end.

Change the DNS on the client computers to include both Ips of 198.6.1.4 and 192.168.0.2

If this does not fix. Also change the DNS on both Ethernet adapter Local Area Connections on the Server (Which is how i have it set up) to the IP of your Win2k servers IP. Yours is 192.168.0.2

This should work!

Akart

 
Thanks for your continued advice. Unfortunately DNS has not been the issue. I can not even ping a known IP address on the internet so resolving names to IP's is a secondary concern at this point in the gaem. I made the suggested change just to be sure and the results remain, no internet access from the switch.
 
I see...

In that case. If you can't even ping anything from the win2k server then the problem is with your modem connection.

You should be able to get free technical support for that from your ISP.

Sorry i could not help you further...

Akart
 
I am not certain you understand the underlying problem. I am able to access the internet from the server but not from any PC which is utilizing NAT through a switch off of the server. There is a problem with the NAT service.
 
I see 2 Nic's and one PPP entry....The public entry of 192.168.0.2, is that the address that the ISP is providing ??? If so then that could be the problem...You are trying to route on the same subnet....Change your internal DHCP to something else (172.16.x.x which is a private IP) and see if that works...
 
Actually, the PPP entry is the address provided by the ISP. The 192.168.0.2 is the address that I assigned to that NIC.
 
No, it is PPPOE, (ethernet) it is a DSL connection.
 
OK you have lost me.....If this is using an Ethernet card, then why do you have 2 private IP addresses???? I currently use NAT with a cable modem and one NIC has a 192.168.x.x address for internal and the other has a DHCP address from the ISP. The adapter connected to the DSL needs to have a DHCP address from the provider or static IP from the provider, then you should reconfigure NAT in RRAS....If the DSL connection does not connect to a NIC then you must select the connection type in RRAS for the Public connection....Either way you cannot route on the same subnet....FYI
 
1. You don't need the public adapter so disable that.

2. Server. Take the DNS address out if you don't have DNS services on the server. If you do, enter in 127.0.0.1 or the address of the server.

3. Server. Enable Internet Sharing in your private connection thru network and dialup connections.

4. Workstation. If your grabbing a IP address dynamically from the server, you should be able to ping it. If your server provides DNS services, then your workstation DNS should point to the server. If not, point it to your ISP's DNS.

5. Workstation. Ping a outside address using the a external ip address. If that works, then you have a outside connection. If it doesn't, change your server's Internet connection to the other connection.

6. Workstation. Ping a outside address using a DNS name. If that is working then your DNS is resolving. If not, try changing your DNS to your ISP's.

Hope this helps.

Perry
 
I do need the public adapter. That is my interface to the DSL modem/internet. Perhaps you meant that I can take out the IP address and just use DHCP for it.
 
Yes....But the Public NIC must get an address from the ISP in order to route successully.. If you use ICS then you must completely disable RRAS NAT or you will have issues. ICS runs its own DNS and DHCP mini servers which could mess you up even more....reply to IC@neo.rr.com and I will provide you a step by step guide for configuring NAT on Windows 2000 Server.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top