Automatic VPN Type setting doesn't work in XP



I am currently upgrading our remote access VPN from PPTP to L2TP/IPSEC but I
have run into a problem with the clients.

By default the "Type of VPN" setting in a VPN connection is set to Automatic
on the built in XP VPN client. My understanding is that when Automatic is set
the system should attempt an L2TP/IPSEC connection first then if that fails
attempt a PPTP connection. However whenever I try it always makes a PPTP
connection.

If I change the conenction settings to specify L2TP/IPSEC instead of
Automatic the conenction is made ok so I know that L2TP/IPSEC connections are
working.

I have tried disabling PPTP connections on the 2003 RRAS sevrer but then VPN
clients with Automatic set fail to connect.

Is there any way to force XP clients set as Automatic to try L2TP/IPSEC
conenctions first?
.



Relevant Pages

  • Cisco VPN 3005 error
    ... Windows XP clients using PPTP. ... thier dhcp ip address given out by the vpn. ... Session started on tunnel 1.1.1.1 ... Session Type: PPTP ...
    (comp.dcom.sys.cisco)
  • Access denied to shares
    ... No one accessing our network remotely via PPTP or VPN. ... >and the red question marks as you describe. ... >>the share later Win9x clients get access denied and have ...
    (microsoft.public.win2000.networking)
  • Re: Zertifikate und Smartcards
    ... VPN über L2TP/IPsec einrichten. ... z.Zt. stellen wir nur VPN per PPTP her. ... > von Gemplus auch noch ein CSP dazu kaufen, doch das ist wohl für jeden PC ...
    (microsoft.public.de.german.isaserver)
  • CRL Checking - L2TP/IPSec and XP
    ... Does anyone know if XP clients perform CRL checking over a L2TP/IPSec ... I am setting up a vpn using XP clients, ... gateways and certificates. ...
    (microsoft.public.windows.server.security)
  • Re: CRL Checking - L2TP/IPSec and XP
    ... > Does anyone know if XP clients perform CRL checking over a L2TP/IPSec ... > I am setting up a vpn using XP clients, ... > gateways and certificates. ...
    (microsoft.public.windows.server.security)

Loading