can not direct inside network internet request to outside network

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

Guest

I have an 'inside' network connected to a Win2K Server through one NIC. I
have an 'outside' network (adsl modem/router) connected to another NIC on the
same Win2k Server. From the Win2K Server I can see both networks (before
enabling RRAS) including pinging www sites on the Internet. I tried using
RRAS to route the
'inside' network to the 'outside' network by doing the following:

1.) Running the Configure and Enable RRAS wizard on the Server.
2.) Selecting the 'Internet connection server' in the Common Configurations
dialog
3.) Set up a router with the NAT routing protocol in the Internet
Connection Server Setup dialog
4.) Selected the 'outside' network under the 'Use the Selected Internet
Connection' in Internet Coonection dialog
5.) Selected the 'inside' network in the Network Selection dialog for
Select the routing interface for the network that should have access to the
Internet.
6.) Finish wizard

The RRAS service then starts.

Not only does it not share the connection, I can no longer access the
Internet through the 'ouside' from the Win2K Server. Ping of a www returns
the translated IP address for that website but then times out for the ping
that IP address.

I am obviously not understadning something Does anybody have some
suggestions?

Attached is the ipconfig/all output. The only difference between this and
RRAS enabled is wether the IP Routing Enabled is 'yes' or 'no'.

Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : seir1srv
Primary DNS Suffix . . . . . . . : SEIRCORP.seir.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : SEIRCORP.seir.com
lan
seir.com

Ethernet adapter wireless:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys LNE100TX(v5) Fast Ethernet
Adapter #3
Physical Address. . . . . . . . . : 00-0C-41-ED-C7-D4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.202
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.3
DHCP Server . . . . . . . . . . . : 192.168.0.3
DNS Servers . . . . . . . . . . . : 10.10.1.1
Lease Obtained. . . . . . . . . . : Friday, September 24, 2004 8:55:55 AM
Lease Expires . . . . . . . . . . : Saturday, September 25, 2004 8:55:55 AM

Ethernet adapter outside:
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Linksys LNE100TX(v5) Fast Ethernet
Adapter #2
Physical Address. . . . . . . . . : 00-0C-41-EF-A2-72
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Friday, September 24, 2004 9:21:46 AM
Lease Expires . . . . . . . . . . : Saturday, September 25, 2004 9:21:46 AM

Ethernet adapter notused:
Media State . . . . . . . . . . . : Cable Disconnected
Description . . . . . . . . . . . : Intel(R) 82559 Fast Ethernet LAN on
Motherboard
Physical Address. . . . . . . . . : 00-30-48-10-8D-6A

Ethernet adapter Inside:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys LNE100TX(v5) Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-03-6D-20-25-8C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.1.1
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 127.0.0.1
 
Hi

Maybe this will help if you missed out something:

How To Configure the NAT Service in Windows 2000

IN THIS TASK
==============
Configure Windows 2000 RRAS NAT Server
Configure RRAS NAT Service To Assign IP Addresses And Perform Proxy DNS
Queries

SUMMARY
=========
This step-by-step article describes how to configure the NAT service in
Windows 2000. The Windows 2000 Routing and Remote Access service includes a
Network Address Translation (NAT) routing protocol. When the NAT protocol
is installed and configured on the RRAS server, internal network clients
with private IP addresses can access the Internet through the external
interface of the NAT server.


Configure Windows 2000 RRAS NAT Server
=======================================
When internal network clients send a request for the Internet, the NAT
protocol driver intercepts the request and forwards the request to the
destination Internet server. All requests appear to come from the external
IP address of NAT server. This effectively hides your internal IP addresses
scheme.

To configure the Windows 2000 RRAS NAT server:

1. On the Administrative Tools menu, click Routing and Remote Access.
2. In the Routing and Remote Access console, expand your server name and
then expand the IP Routing node in the left pane of the console.
3. Right-click the General node, and then click New Routing Protocol.
4. In the New Routing Protocol dialog box, click to select the Network
Address Translation (NAT) protocol, and then click OK.
5. Right-click the Network Address Translation (NAT) node in the left
pane, and then click New Interface.
6. Select the interface that represents your internal network interface,
and then click OK.
7. In the Network Address Translation Properties dialog box, click the
Private interface connected to private network option, and then click OK.
8. Right-click the Network Address Translation (NAT) node in the left
pane, and then click New Interface.
9. Select the interface that represents your external network interface,
and then click OK.
10. In the Network Address Translation Properties dialog box, click the
Public interface connected to the Internet option. Click to select the
Translate TCP/UDP headers (recommended) check box. This is required if you
have only a single IP address bound to the external interface. Click OK.

The Windows 2000 NAT server can automatically assign IP addresses to
internal network clients. This is a viable option if you do not have a DHCP
server already assigning addressing information to clients on the internal
network.


Configure RRAS NAT Service To Assign IP Addresses And Perform Proxy DNS
Queries
=======================================================================

The NAT server can also perform DNS queries on the behalf of NAT clients.
The RRAS NAT server resolves the Internet host name that is included in the
client request and then forward the IP address to the client.

To configure the RRAS NAT service to assign IP addresses and perform proxy
DNS queries on the behalf of internal network clients:

1. Right-click the Network Address Translation (NAT) node in the left
pane, and then click Properties.
2. In the Network Address Translation (NAT) Properties dialog box, click
the Address Assignment tab. Click to select the Automatically assign IP
addresses by using DHCP check box. You can type a network ID and subnet
mask in the IP address and Mask boxes.
3. Click the Name Resolution tab. Click to select the Clients using Domain
Name System (DNS) check box. If you use a demand-dial interface to connect
to the Internet, click to select the Connect to the public network when a
name needs to be resolved check box. Click the interface to dial in the
Demand-dial interface box.
4. Click Apply, and then click OK.

NOTE: After you follow these basic configuration steps, internal network
clients are able to access servers on the Internet.


The information in this article applies to:

o Microsoft Windows 2000 Server


Reference Link:
================
http://support.microsoft.com/default.aspx?scid=kb;en-us;310357&Product=win20
00

Shilpa Sinha
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Thank you for the suggestions. We did resolve the problems. If anyone is
interested it is list in the post in the Windows Server Networking newsgroup
under 'routing internal network IP to outside network'.

The problems resolved to get thing working:
there were 2 default gateways (ony one a computer is allowed, I missed it in
the configuration, they were both autmatically assigned)
There was a "." in the domain controllers forward DNS table the prevented
corrected DNS mapping to the outside (KB article 291382)
 
Back
Top