RAS Server giving out wrong gateway

[Brian]

When ever users dial-into my RAS server the are getting
the incorrect information. I have RAS setup for DHCP but
when users dial-in they get the correct IP address but
the subnet and gateway are wrong. The subnet is always
255.0.0.0 and it should be 255.255.255.0 and the gateway
is always the same as the IP address which is obviously
wrong. Any ideas?

 

[Dusty Harper {MS}]

The gateway now becomes the "point-to-point" link between the client and
server. The route basically says that for all unknown traffic go through my
VPN tunnel. This is correct.

DHCP is just handing them the IP, and options

 

[Bill Grant]

As Dusty said, the gateway address must be the "received" IP address,
because that is the link to the RAS server, and that is where the traffic
must go. The netmask is irrelevant (unless you clear the "Use default
gateway .. " box), because all traffic is sent across to the server.

What sort of problems are you having? If you can ping LAN machines by IP
address, your routing is working, and it is probably a name resolution
problem.

 

[Brian]

The problem I am having is I cannot ping anything by IP
address or by name.

-----Original Message-----
As Dusty said, the gateway address must be the "received" IP address,
because that is the link to the RAS server, and that is where the traffic
must go. The netmask is irrelevant (unless you clear the "Use default
gateway .. " box), because all traffic is sent across to the server.

What sort of problems are you having? If you can ping LAN machines by IP
address, your routing is working, and it is probably a name resolution
problem.

The gateway now becomes the "point-to-point" link between the client and
server. The route basically says that for all unknown

traffic go through
my

VPN tunnel. This is correct.

DHCP is just handing them the IP, and options
--

------------------- -------------------

.

 

[Brian]

Another thing. I am trying to RAS in from an NT 4.0
Workstation.

-----Original Message-----
As Dusty said, the gateway address must be the "received" IP address,
because that is the link to the RAS server, and that is where the traffic
must go. The netmask is irrelevant (unless you clear the "Use default
gateway .. " box), because all traffic is sent across to the server.

What sort of problems are you having? If you can ping LAN machines by IP
address, your routing is working, and it is probably a name resolution
problem.

The gateway now becomes the "point-to-point" link between the client and
server. The route basically says that for all unknown

traffic go through
my

VPN tunnel. This is correct.

DHCP is just handing them the IP, and options
--

------------------- -------------------

.

 

[Bill Grant]

If you can't ping by IP there is something wrong with your connection.
What IP does the client receive? What IP does the server allocate to the
connection?

You must be able to ping the server's RAS IP from the client, because
that is just the other end of the link!

Another thing. I am trying to RAS in from an NT 4.0
Workstation.

-----Original Message-----
As Dusty said, the gateway address must be the "received" IP address,
because that is the link to the RAS server, and that is where the traffic
must go. The netmask is irrelevant (unless you clear the "Use default
gateway .. " box), because all traffic is sent across to the server.

What sort of problems are you having? If you can ping LAN machines by IP
address, your routing is working, and it is probably a name resolution
problem.

The gateway now becomes the "point-to-point" link between the client and
server. The route basically says that for all unknown

traffic go through
my

VPN tunnel. This is correct.

DHCP is just handing them the IP, and options
--

------------------- -------------------

--

When ever users dial-into my RAS server the are getting
the incorrect information. I have RAS setup for DHCP but
when users dial-in they get the correct IP address but
the subnet and gateway are wrong. The subnet is always
255.0.0.0 and it should be 255.255.255.0 and the gateway
is always the same as the IP address which is obviously
wrong. Any ideas?

.