Jump to content

Windows 2003 NAT not working...


jagomai
 Share

Recommended Posts

Hi,

I've been trying to set up a Windows 2003 Server as NAT.

This is how it looks for now, more computer will be added when it works..:

Internet (Cable modem) <-> (Network card 1) Windows 2003 Server (Network card 2) <-> Switch <-> XP Laptop +...?

I can ping the server, and I can log in remotely into the server (I'm typing this on my laptop, through the server).

Everything seems to work fine, but when I can not ping outside of the server. If I try to ping www.google.com, I only get

Ping request could not find host www.google.com. Please check the name and try a

gain.

I have set up RRAS. In "NAT/Basic Firewall" in RRAS window, I have Network card 2 as "Private interface" and Network card 1 as "Public interface" with NAT and basic firewall enabled..

What am I doing wrong? Why can't I get outside the server from the inside?

Thanks alot!

Link to comment
Share on other sites

Do you have Dynamic Host Configuration Protocol (DHCP) enabled for the inside host?

Do you have Domain Name System (DNS) Server information populated into the DHCP configuration so it's provided to DHCP clients?

The 2003 Server should have itself as Primary DNS Server, and at least two DNS Servers from your ISP for Secondary and Tertiary DNS Servers.

DNS Server Service and DHCP Server Service also have to be enabled on the 2003 Server.

DHCP also has to be configured to give out the 2003 Server as Primary DNS, and possibly the ISP's servers for Secondary and Tertiary DNS Servers.

If you don't know what all of this is about, please look for some Microsoft tutorials that can help explain and can help you configure your network.

If this is for a business network, you should give careful consideration to firewall features on the 2003 server and to securing DNS and DHCP.

Link to comment
Share on other sites

Do you have Dynamic Host Configuration Protocol (DHCP) enabled for the inside host?

Do you have Domain Name System (DNS) Server information populated into the DHCP configuration so it's provided to DHCP clients?

The 2003 Server should have itself as Primary DNS Server, and at least two DNS Servers from your ISP for Secondary and Tertiary DNS Servers.

DNS Server Service and DHCP Server Service also have to be enabled on the 2003 Server.

DHCP also has to be configured to give out the 2003 Server as Primary DNS, and possibly the ISP's servers for Secondary and Tertiary DNS Servers.

If you don't know what all of this is about, please look for some Microsoft tutorials that can help explain and can help you configure your network.

If this is for a business network, you should give careful consideration to firewall features on the 2003 server and to securing DNS and DHCP.

Hey thanks alot for the quick reply!

But all seems to be working now... I turned on the server tonight for some more testing, and it all works... ICMP, Browsing, the works.. I guess it needed a reboot?

It's only for private stuff now, so all is well. :)

Link to comment
Share on other sites

Okay, so now the NAT stopped working again, for some reason. I didn't change any settings, though.

I did notice, however, that in the RRAS config window, in the "General" tab, the interface "Internal" is now marked as "Not available" and "Non-operational"...

Why is this? How could I fix it? I didn't do anything to the configuration, only shutdown / poweron...

Link to comment
Share on other sites

Can you right click on "Internal" and select "Enable," or is it grayed out?

Is there anything in the Windows Event Logs that could help in troubleshooting?

There is no "Enable"-button... Only: "Show TCP/IP Information", "Show Address Translations", etc... I can click "refresh", but nothing happens..

Also, I can click "Properties" on the Internal device and "Enable IP Router Manager".. But it is checked..

Link to comment
Share on other sites

Hm.. Events viewer gives me two warnings.. Here they are in chronological order from the event viewer.

Number one:

Event ID: 30012

The DHCP allocator detected network address translation (NAT) enabled on the interface with index '65540'. The allocator has disabled itself on the interface in order to avoid confusing DHCP clients.

Number two:

Event ID: 30001

The DHCP allocator was unable to check whether the IP address 192.168.0.43 is in use on the network for local IP address 192.168.0.1. This error may indicate lack of support for address-resolution on the network, or an error condition on the local machine. The data is the error code.

The first one is a non-issue according to Microsoft. It's just a standard message. The second one however... Here's what MS support says about it:

Cause:

There is a host on the network which has a duplicate of an IP address in NAT's DHCP pool of addresses.

I mean, sure. My laptop is on the network with an IP address that also has to be NAT:ed! Am I supposed to turn of the DHCP service to use NAT? How can my computers then receive IP addresses? :huh:

Hmm.. what am I doing wrong? The server is connected to a switch first, and through the switch to the other computers... Does this affect anything?

Thanks for any help!

Link to comment
Share on other sites

Also, if I disable DHCP address assignment in RRAS tab NAT/Basic Firewall, the message in the Event Viewer disappears.

But of course it still doesn't work..

Is there a way to manually specify which IP addresses within the network should be mapped to the NAT outgoing network device?

Like, some way to say to Windows that "192.168.0.20" (which is my laptop) always gets NAT:ed? Then there would be no need for this DHCP bullshit.

Link to comment
Share on other sites

Are the IP addresses on the two network cards the Server is using in different IP address spaces? You're not just doing Network Address Translation with the 2003 Server, you're also routing.

Routing requires that the two network interfaces be in different networks.

Please post the two IP addresses of the Server's Network Cards, or send them to me in a message if you're uncomfortable posting.

Link to comment
Share on other sites

Are the IP addresses on the two network cards the Server is using in different IP address spaces? You're not just doing Network Address Translation with the 2003 Server, you're also routing.

Routing requires that the two network interfaces be in different networks.

Please post the two IP addresses of the Server's Network Cards, or send them to me in a message if you're uncomfortable posting.

Hey, thanks for answering.

Yes, they are in two different networks. The private card has IP address 192.168.0.1, while the public one receives a dynamic address from my ISP (right now that would be 84.232.142.27)

Link to comment
Share on other sites

DHCP will greatly simplify your network administration, especially if you are going to be adding more computers to your network.

Make sure your DHCP scope is in the 192.168.0.x range with a mask of 255.255.255.0, and that your Default Gateway is 192.168.0.1 in DHCP. If you have DNS configured on your server, it should be the primary DNS Server given out by DHCP.

Please also take a look at this Microsoft article:

http://support.microsoft.com/kb/837453

Is there a reason you prefer to route through a Windows 2003 Server instead of buying a firewall for $40 or $60?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy