Re: [NTISP] RAS client can't see network?

Terry Bomersbach ( (no email) )
Tue, 9 Feb 1999 20:59:43 -0600

With RAS, you need to edit the registry and add a value for RASArp under
parameters for DisableOtherSrcPackets.

-----Original Message-----
From: Darryl Harvey <darryl@myemail.com.au>
To: ntisp@iea-software.com <ntisp@iea-software.com>
Date: Tuesday, February 09, 1999 4:39 PM
Subject: [NTISP] RAS client can't see network?

>I have added a RAS client to my Server so I can do remote admin.
>
>I have a modem on COM1: and it seems to work ok..
>
>I dial in via a remote client, I get authorisedand the connection is up.
>
>Problem is, I cannot ping the server or the server cannot ping the client.
>I am enabling "Access whole network" so I should have access to the server
>and the rest of my network..
>
>THe IP in use n the etehrnet is 192.168.0.1 and the RAS client gets
>assigned 192.168.1.2, IP forwarding is on..
>
>
>Should this work this way ???? Am I missing something?
>
>Darryl
>
>
>
>
>For more information about this list, including removal,
>see this url: http://www.iea-software.com/maillist.html

For more information about this list, including removal,
see this url: http://www.iea-software.com/maillist.html