RRAS is not passing dial-up traiffic

We have installed a new Server 2003 Std SP1 box for Remote Access. The
server allows for the connection and hands out the IP information that it is
supposed to, but I can not access the network. I can get DNS resolution on
other computers that are on the internal network but I can not access them.
When I do a pathping it dies at the dial-up interface. In the past when I
have been setting this it has been going from the internal to the extrnal
network with two NIC's.

When I configure the Remote Access will only show the LAN networkinterface
and not the dial-up interface that is listed as the Internal interface when
really it is the external interface. From the remote client I can ping the
LAN card by the name of the computer. And I can ping the remote client from
the RRAS server, and when I try to ping the client from an internal PC I get
TTL expired in transit.

The RRAS is a Class A private network and many of our new servers on the
same network. THe old servers on a class B private network.

Any and all help is appreciated.
--
Eric Speake. MCSE
AECI


Bigmaneric97

I have a fair idea about what is happening, but you really haven't
supplied a lot of information about the network config. It sounds like a
straight-forward routing problem.

It appears that you running a routed network (ie you have LAN machines
in more than one IP subnet). If you do, I would put the remote clients in
their own subnet, not share with one of your LAN subnets. Then use normal IP
routing to route between the remotes and the LAN subnets using the VPN
server as a router.

Bigmaneric97 wrote:
> We have installed a new Server 2003 Std SP1 box for Remote Access.
> The server allows for the connection and hands out the IP information
> that it is supposed to, but I can not access the network. I can get
> DNS resolution on other computers that are on the internal network
> but I can not access them. When I do a pathping it dies at the
> dial-up interface. In the past when I have been setting this it has
> been going from the internal to the extrnal network with two NIC's.
>
> When I configure the Remote Access will only show the LAN
> networkinterface and not the dial-up interface that is listed as the
> Internal interface when really it is the external interface. From
> the remote client I can ping the LAN card by the name of the
> computer. And I can ping the remote client from the RRAS server, and
> when I try to ping the client from an internal PC I get TTL expired
> in transit.
>
> The RRAS is a Class A private network and many of our new servers on
> the same network. THe old servers on a class B private network.
>
> Any and all help is appreciated.

Since the question is not really providing the configuration, I wonder, have
you installed the DHCP Relay Agent in RRAS?

I do suspect a routing issue here, but without your configuration that would
be impossible to tell.
--
Regards,

Patrick Boren


"Bigmaneric97" wrote:

> We have installed a new Server 2003 Std SP1 box for Remote Access. The
> server allows for the connection and hands out the IP information that it is
> supposed to, but I can not access the network. I can get DNS resolution on
> other computers that are on the internal network but I can not access them.
> When I do a pathping it dies at the dial-up interface. In the past when I
> have been setting this it has been going from the internal to the extrnal
> network with two NIC's.
>
> When I configure the Remote Access will only show the LAN networkinterface
> and not the dial-up interface that is listed as the Internal interface when
> really it is the external interface. From the remote client I can ping the
> LAN card by the name of the computer. And I can ping the remote client from
> the RRAS server, and when I try to ping the client from an internal PC I get
> TTL expired in transit.
>
> The RRAS is a Class A private network and many of our new servers on the
> same network. THe old servers on a class B private network.
>
> Any and all help is appreciated.
> --
> Eric Speake. MCSE
> AECI