Help, Please

[x]

I'm hoping someone in here can assist me. This is likely a very simple
problem, and I'm just too thick to see the solution staring back at me, and
if that's the case, I can accept that. But I really need to get this
working.

ISSUE: setting up dial-up access on Win2K server for a WinXP client system.
Server also serves LAN controller, and routes LAN systems to use High speed
connection.

Dial up system connects, no problem, using either the user names associated
with the DOMAIN, or if I set up a Demand Dial interface specifically.
However, in either case, once the connection is made, the connected system
does not get through to the internet. It is set up to use 'default gateway
on remote network', and obtains an IP address from the server. But once it
connects, its IP address and the Default Gateway get set to the same
address. (IE. 192.168.0.17) But the gateway should get set to 192.168.0.1.

How can I resolve this issue?

 

[Bill Grant]

No, the gateway should not be 192.168.0.1 . Your dialup client is
connected to the LAN by a point-to-point link. All traffic for the LAN (or
the Internet) must go across this link, and the IP address associated with
the link is the "received" IP. So the client's default gateway address
should be this received IP. See MS KB 254231.

Getting Internet access for the remote is a different matter. How do the
LAN clients get to the Internet? Does the RRAS server do NAT, or is that
done by the router? What is doing DNS?

 

[x]

No, the gateway should not be 192.168.0.1 . Your dialup client is
connected to the LAN by a point-to-point link. All traffic for the LAN (or
the Internet) must go across this link, and the IP address associated with
the link is the "received" IP. So the client's default gateway address
should be this received IP. See MS KB 254231.

Getting Internet access for the remote is a different matter. How do the
LAN clients get to the Internet? Does the RRAS server do NAT, or is that
done by the router? What is doing DNS?

Yes, the RRAS server does NAT for the LAN to connect to the high-speed
connection. The DNS is actually being done by our service providers' DNS
servers.

 

[Bill Grant]

With the default settings, a dialup client cannot get to the Internet
through NAT on the same server. The "internal" interface which the remote
client uses does not send data via NAT. To make this interface an input to
NAT, you must use the following netsh command from a command prompt.

netsh routing ip nat add interface internal private

After you run this command, you will see in the RRAS console that the
internal interface is now added as an input to NAT.

 

[x]

With the default settings, a dialup client cannot get to the Internet
through NAT on the same server. The "internal" interface which the remote
client uses does not send data via NAT. To make this interface an input to
NAT, you must use the following netsh command from a command prompt.

netsh routing ip nat add interface internal private

After you run this command, you will see in the RRAS console that the
internal interface is now added as an input to NAT.

Works like a charm Thanks again, Bill!