RRAS and dial-in problem

Hello,
I have windows 2003 and set up dial-in access for the
domain users. The Internal interface is created and all
seems all right, however when the first dial-in user
connects the Internal interface's gateway is set to that
PC's IP so any other incoming dial-in connection can see
the internal lan but cannot browse the internet. (We also
use dhcp in our network).
I early tried netsh routing ip nat add interface internal,
but the problem persists.
The IP Routing tables show that the first dial-in user PC
has the correct gateway ip, 127.0.0.1, but the rest of the
dial-in connected PCs have the gateway ip identical to the
first connected PC's IP, ie, 10.10.0.200 If there's any
article in kb related to this, I'll be glad to have it
pointed out...
Thanks in advance,
lizet

You seem to have misunderstood how this all works. With W2k3 you do not
need to use the netsh command, although it should still work. In W2k3 RRAS
the internal interface appears as an option in NAT, so you can add the
internal interface as a private interface for NAT directly from the RRAS
console.

The default gateway of each client is its received IP address, which
means that the RAS connection is in fact the default gateway for the client.
(So all Internet traffic goes to the RRAS server's internal interface).

Can your LAN clients access the Internet using NAT on the server? If
they can, adding the internal interface as a private interface in NAT will
allow dialup clients to do the same. The LAN clients use the server's
private NIC as their gateway and NAT interface, dialup clients use the
internal interface for this.

"lizet" <lizet-(E-Mail Removed)> wrote in message
news:1cdc01c4a83b$abe38cd0$(E-Mail Removed)...
> Hello,
> I have windows 2003 and set up dial-in access for the
> domain users. The Internal interface is created and all
> seems all right, however when the first dial-in user
> connects the Internal interface's gateway is set to that
> PC's IP so any other incoming dial-in connection can see
> the internal lan but cannot browse the internet. (We also
> use dhcp in our network).
> I early tried netsh routing ip nat add interface internal,
> but the problem persists.
> The IP Routing tables show that the first dial-in user PC
> has the correct gateway ip, 127.0.0.1, but the rest of the
> dial-in connected PCs have the gateway ip identical to the
> first connected PC's IP, ie, 10.10.0.200 If there's any
> article in kb related to this, I'll be glad to have it
> pointed out...
> Thanks in advance,
> lizet

I had found this article and thought it would apply to win2k3 as well
http://support.microsoft.com/default...;EN-US;q310888
Anyway, the problem is still there. We have three modems for remote access,
LAN users can browse the internet without problems, but only the first dial
in PC that connects to the RAS is able to browse the internet.
The IP Routing table shows that the first dial in PC has a correct IP and
its own IP as gateway, but the other dial in PCs have a different IPs and the
gateway's IP is exactly the same of the first dial in IP.
Shouldn't these dial in PCs take their own IPs as gateway?
Is there any wrong setting at the dhcp?
thanks in advance,
Lizet
"Bill Grant" wrote:

> You seem to have misunderstood how this all works. With W2k3 you do not
> need to use the netsh command, although it should still work. In W2k3 RRAS
> the internal interface appears as an option in NAT, so you can add the
> internal interface as a private interface for NAT directly from the RRAS
> console.
>
> The default gateway of each client is its received IP address, which
> means that the RAS connection is in fact the default gateway for the client.
> (So all Internet traffic goes to the RRAS server's internal interface).
>
> Can your LAN clients access the Internet using NAT on the server? If
> they can, adding the internal interface as a private interface in NAT will
> allow dialup clients to do the same. The LAN clients use the server's
> private NIC as their gateway and NAT interface, dialup clients use the
> internal interface for this.
>
> "lizet" <lizet-(E-Mail Removed)> wrote in message
> news:1cdc01c4a83b$abe38cd0$(E-Mail Removed)...
> > Hello,
> > I have windows 2003 and set up dial-in access for the
> > domain users. The Internal interface is created and all
> > seems all right, however when the first dial-in user
> > connects the Internal interface's gateway is set to that
> > PC's IP so any other incoming dial-in connection can see
> > the internal lan but cannot browse the internet. (We also
> > use dhcp in our network).
> > I early tried netsh routing ip nat add interface internal,
> > but the problem persists.
> > The IP Routing tables show that the first dial-in user PC
> > has the correct gateway ip, 127.0.0.1, but the rest of the
> > dial-in connected PCs have the gateway ip identical to the
> > first connected PC's IP, ie, 10.10.0.200 If there's any
> > article in kb related to this, I'll be glad to have it
> > pointed out...
> > Thanks in advance,
> > lizet
>
>
>