Re: Unable to access private network from the VPN (NAT)

Are you sure you are actually connecting by VPN? The symptoms you
describe fit the case when you are connecting directly through the Internet!

If you connect by VPN, your client should be receiving a private IP
address. Its connection to the server should be through the "virtual"
interface of the server. Any port forwarding settings on the server should
have no effect on this connection. The VPN traffic comes through the
"public" interface encrypted and encapsulated and is not seen by that
interface.

"Linh" <Linh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:996258F3-F8E4-4813-906B-1099206896F3@xxxxxxxxxxxxxxxx
> I'm sorry I guess I was unclear. I'm unable to access the machines on the
> private interface. I'm unable to ping them. However if I forward ports
> to
> these server then i'm able to connect to 192.168.1.machinIP
>
> I would like open access to all machines...
>
> thanks!
>
> "Scott Harding" wrote:
>
>> This is typically because of misconfigured DNS/WINS settings. They won't
>> be
>> able to browse through Network neighborhood but should be able to access
>> resources by name.
>>
>> --
>> Scott Harding
>> MCSE, MCSA, A+, Network+
>> Microsoft MVP - Windows NT Server
>>
>> "Linh" <Linh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:174AF13F-9D3A-40E2-A292-B3E6F8BC1A73@xxxxxxxxxxxxxxxx
>> >I have users successfully connecting to the VPN through my public, they
>> >are
>> > able to access both interfaces on the VPN server however they are
>> > unable
>> > to
>> > access any of the machines on the private network. Within the Windows
>> > 2003
>> > VPN setup I was able to forward ports to specific machines and have the
>> > VPN
>> > users access that but ideally I would like to give the users
>> > unrestricted
>> > access to the private network. Is this possible if so how? Private
>> > network
>> > is 192.168.1.0/24
>>
>>
>>


.

Relevant Pages

  • Re: Please Help Site-To-Site without ISA
    ... You can configure more than one site to site VPN connection on the ... You set up a new demand-dial interface and configure a new site to ... public IP of the VPN server at the second site on the front. ... to router connection. ...
    (microsoft.public.windows.server.networking)
  • Re: Unable to access private network from the VPN (NAT)
    ... Port forwarding/filtering is a completely ... why does the server have two interfaces in the same IP ... This extends the VPN ... The first interface is ...
    (microsoft.public.win2000.ras_routing)
  • Re: problem with VPN running on static IP address
    ... I'm interested in what you said about being able to access the vpn server ... through the "virtual" interface. ... I've gotten the vpn to connect, but looking at the routes it gives me I ... It is similar to a RAS connection, ...
    (microsoft.public.windows.server.networking)
  • Re: RWW via VPN only partially working
    ... RWW or a straight RDC session (without connecting the hard drives ... VPN also exacts some additional connection "overhead", ... external NIC if you have 2 NICs in the SBS server). ... Then, RWW ...
    (microsoft.public.windows.server.sbs)
  • Re: Please Help Site-To-Site without ISA
    ... The VPN traffic must go out through the default gateway. ... NICs in the server if they all connect to the Linksys. ... "dialup" type connection and at the demand-dial interface for a router to ... router connection. ...
    (microsoft.public.windows.server.networking)
Loading