How to set Default Gateway for a connection using RRAS and NAT

Hi all...

I have had problems in configuring RRAS to allow LAN client computers to
connect to Internet using the Internet connection present in the server.
Maybe I have found the cause of the problem. Believe it or not, I have tried
this for looong time... several months and I always end in configuring ICS
back, which always works.

When I enable ICS, all works perfectly, that is, all LAN computers can
browse Internet without any problem. When I disable ICS and enable RRAS, all
LAN continue working, but computers cannot browse Internet anymore.

I have compared IPCONFIG /ALL information, routing tables and even PathPing
information when using ICS and RRAS and all looks identical, except one
little detail.

In the IPCONFIG /ALL in the server, when ICS is enabled, it is shown a
default gateway address, which is the address assigned by the ISP. When
using RRAS, Default gateway information is blank. I think that is the cause
that when I PathPing an internet site from a LAN computer, packet only
reaches server, but it doesn't reach internet interface.

For instance, this is the IPCONFIG /ALL concerning internet Interface when
using ICS:

PPP adapter Manquehue:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 200.119.229.94
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 200.119.229.94
DNS Servers . . . . . . . . . . . : 200.74.160.103
200.74.160.104
NetBIOS over Tcpip. . . . . . . . : Disabled

And as I said, when I enable RRAS, Default gateway field appear blank.

If ICS can set that value automatically, I think that using RRAS and NAT is
also possible (manually).

Please, don't point me to some URL's because I have read a lot about RRAS
and NAT, following all directions textually, but no site talks about the
architecture I have in my server.

Thanks
Jaime

 

That your pick. All three of these article are pretty much identical.

299801 - HOW TO: Configure a Windows 2000 Server as a Network Address
Translation Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q299801

310357 - HOW TO: Configure the NAT Service in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;310357

How to configure Network Address Translation in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;816581

 

Robert,

I don't have static IP. Each time I connect to my ISP, it assigns me a new
IP (I connect to my ISP through a DSL router connected to a NIC in the
server). That's why I cannot set default gateway manually using Network
connections.

I wonder, the same as you, why DHCP enabled appears No.


Jaime

 

Phillip, as I wrote, I have followed a lot of guides, the third link among
them, with no success.

Concerning all the documents, I have some main differences:

1.- I have no dial-up interface because what I have is a DSL router, it has
the static IP address of 192.168.1.1. So, I cannot follow instructions for
setting up a dial-up connection using RRAS (in fact, I have followed them,
but obviously without success)

2.- Since I have a DSL router, I created a WAN/PPP connection under Network
Connections. After connected to my ISP I run RRAS wizard. In this case, I can
never add that WAN/PPP interface so that I can enable LAN internet connection
on it.

3.- From RRAS/NAT point of view, I have 2 internal NIC's on my server. One
connected to the LAN and the other connected to the DSL router. The DSL
router is actually the public interface that connects to Internet.

Do you have other suggestion? or.. do you know how can I know the exact
configuration made by ICS? If I manage to imitate what ICS has set up, I
think I could do RRAS to work, hopefully.

Thanks
Jaime

 

If your DSL router's internal IP address is 192.168.1.1, THAT is the default
gateway for your server. Manually enter it on the network connection for
your server.

 

Thanks Eric....

Concerning default gateway, I paste here the IPCONFIG /ALL for the server
when ICS is enabled (allowing LAN computers to connect to internet). As you
see, 192.168.1.1 IP isn't shown anywhere. I knew that DSL modem has that IP
because I searched on Internet about this DSL router and I knew that default
IP is 192.168.1.1, and in fact, if I ping 192.168.1.1 I get response (that's
why I configured Internet interface, the one that connects to the DSL
router, to be in the same network segment). Anyway, When I configure
Internet interface to be in other network segment, ICS always work,
magically.

As I said, when I enable RRAS / NAT, instead of ICS, the only difference is
that default gateway of WAN/PPP interface is blank

Windows IP Configuration

Host Name . . . . . . . . . . . . : srv-dev
Primary Dns Suffix . . . . . . . : DESYTEC.North
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : DESYTEC.North

Ethernet adapter Internet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-11-43-2F-69-26
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : D-Link DFE-530TX PCI Fast Ethernet
Adapte
r (rev.C)
Physical Address. . . . . . . . . : 00-0D-88-CA-8F-CC
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

PPP adapter Manquehue:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 200.119.235.85
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 200.119.235.85
DNS Servers . . . . . . . . . . . : 200.74.160.103
200.74.160.104
NetBIOS over Tcpip. . . . . . . . : Disabled

 

Hello Jaime,

So did you get it to work after all??

I'm still struggling to get NAT set up on a win 2003 server (2 nics + adsl
modem) (no sp1, which i deinstalled after even more (Ics) problems). What do
you think, is it possible to set up NAT on a 2 nic machine + adsl modem at
all !?

All comment/ suggestions welcome,

Fwsmaster

 

That is exactly how I run one. It uses a DSL Modem (no NAT Device)
connected into the external NIC of the RRAS Server with a crossover cable.
ISP assigned IP# is on the external NIC, RRAS performs the NAT.

 

I have 2 nics + adsl router but it didn't work.

I only have successfully configured NAT in a server also with 2 NICS but one
of them is directly connected to Internet.

Unfortunately, I have the same problem as you :-( I think it's possible
because with ICS/ICF all works perfectly, so I think if I imitate ICS/ICF
configuration on NAT, I would be able to connect LAN computers to Internet.

 

But in my case, ISP assigns IP to the DSL router (reflected on a WAN/PPP
connection I added in Network Connections). If NIC connected to the DSL
router would have the valid IP, I think I would never have problems..

 

You have a totally different situation thant what FwsMaster described.
In your case you don't connect any computer Nics to the DSL Device unless
you are trying to create a Back-to-back DMZ. The simplest setup for you is
the connect all machines and the DSL Device's internal facing interface to a
Hub or Switch. So the Hub or Swicth is the physical "center" of the LAN.
If the DSL Device has a built in Switch or Hub you can use it instead,...in
that case the internal facing interface is not physically "visible" and it
simply builtin and is how the built in Switch communicates with the rest of
the DSL Device internally.

 

What I am decribing means you server only needs one Nic, does not use RRAS
and does not use NAT,...your DSL Device is already doing that. If you ran
two nics in the server and ran NAT on it, then you would be creating a
Back-to-Back DMZ,...which means you have to be aware of how that effects the
environment and how you would have to deal with it.