Hi Todd,
Thank you for your reply. I have not yet tested disabling this feature,
although I do have a bit more information about this issue.
The current setup of the Windows VPN is using PPTP. The application is
making a windows system call to the vpn client for the ip address. I am lead
to believe that since PPTP is layer 2 this is the reason this problem exists.
If I use L2TP with IPSEC on a Cisco VPN w/ Cisco VPN client the application
runs fine. I am lead to believe the reason why this implementation works is
becuase of IPSEC and the fact that it is layer 3. The system call now gets
back the correct IP address and the issue is works.
I will attempt to disable the option for the default gateway on remote
network for the PPTP VPN and let you know the results.
Please let me know if you have any feedback on the IPSEC workaround. I hear
that IPSEC is somewhat broken on XP SP2 VPN client but I have no concrete
evidence to support this claim.
Cheers.
"Todd J Heron" wrote:
> Are you enabling the option to use the default gateway on remote network in
> VPN client dial-up properties?
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
> "AKing" <(E-Mail Removed)> wrote in message
> news:3BC1443A-8352-4E3C-9FC1-(E-Mail Removed)...
> Hi,
>
> I am having a big issue with Windows VPN. I am connecting from Client to
> Windows VPN Server (RAS). The problem is that in the VPN environment the
> VPN
> Client PC is using 2 IP addresses, one for the network adapter itself and
> another virtual IP address that is assigned when connected to the VPN. The
> problem is that the network adapter IP address is being relayed to an
> application server, this causes an issue as the application server does not
> know how to get back to the client.
>
> Is there anyway to force the VPN to only use the virtual IP address assigned
> by the VPN server?
>
> Cheers!
>
>
|