Re: RRAS VPN &NAT

Tech-Archive recommends: Fix windows errors by optimizing your registry

That is what normally happens by default. Are the remote users
getting IP addresses in the same IP subnet as the LAN machines? If they are,
it normally just works. The RRAS server acts as a proxy for the remotes on
the LAN. This sometimes fails in a switched LAN. Some switches don't handle
proxy ARP in the same way as hubs.

If the remotes are using a different IP subnet, you need to route the
traffic through the RRAS server.

Note that if you want to use names rather than IP addresses, the remote
clients may need extra info to resolve names of LAN machines.


> Gerry wrote:
> I hope you don't mind me contacting you. I have the opposite problem
> to you, I infact want to set up RAS to allow VPN clients access to
> all the network resources. At the moment they can only access the
> server with VPN/RAS.
>
> I would really appreciate if you could advise me on what I need to do
> to allow VPN clients full access to Lan.
>
> "edisonrus" wrote:
>
>> Setting up Win3k RRAS VPN & NAT. Only want to access information on
>> the RRAS server itself and will not be accessing resources on any
>> other node in the workgroup. (No domain, it's a small operation.)
>> Internet access is through a Linksys Broadband Router (DSL) I've
>> configured port forwarding on the router for PPTP 1723 and IP 47
>> to the Internal IP address on the RRAS Server. The RASS server's
>> default gateway is pointed to the router. Plan on using the
>> Router's DHCP for clients IP address. (will only be two clients)
>> Disabled all other port entries on the RRAS (L2TP etc) Using RRAS
>> authenication and the default access policy.
>>
>> On the clients the (WIN XP) the firwalls are disabled at the
>> moment. I want to enable the firewall. Are there any port execptions
>> to configure on the clients? Also will uncheck Use Default Gateway
>> on remote Network on the client side.
>>
>> Will this work?? Any advice? Any tips are most welcomed.
>>
>> Thanks ~e


.

Relevant Pages

  • Re: Remote Clients Connect Via VPN But are not accessible
    ... If the remotes are using IP addresses in the same subnet as the LAN ... you should be able to access them just like LAN clients. ... That's how it works when the remote accesses a LAN ...
    (microsoft.public.win2000.ras_routing)
  • Re: 2003 SP1 RRAS problem
    ... > and remotes clients and the remote RRAS SP1 server). ... > LAN IP Address 192.168.1.50/24 ... > Out of the local RRAS server Internet NIC - OK ...
    (microsoft.public.win2000.ras_routing)
  • Re: Inconsistent subnet mask assigned for VPN connection in RRAS
    ... gateway (when the "Use default gateway on remote network" checkbox is ... clients are unable to access server resources ... A remote client does not get its network config from DHCP. ... You should allocate a specific subnet to your remotes and route that network to your existing network through the RRAS server. ...
    (microsoft.public.windows.server.networking)
  • Re: SBS2003 Clients will not remote
    ... Lost my first reply--Yes the rww works well within the local network ... and terminal services so connectivity within lan works great. ... All the pertinent ports have been forwarded and remote desktop ... >> set up on clients and users added to remote list. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot ping VPN clients
    ... the basic IP routing rules to route between the remote subnet and the LAN ... So the first essential is that IP routing is enabled on the RRAS server. ... it to every machine on the LAN which the remote clients need to contact. ...
    (microsoft.public.windows.server.networking)