Is the windows L2TP VPN just slow to connect or can I speed it up somehow?

Was using SonicWall global connect for the VPN for WFH users and from the time they enter their password to connection is about 10 seconds.

But this method requires them to log into the laptop first, then connect, which means they don’t get startup policies and they don’t get the icons for common desktop shortcuts.

If I enable the L2TP connection before they sign in to windows it takes up to a minute and a half to establish the connection, and drops the link as it trains.

Actual performance on the two tunnels is close enough to equal that it doesn’t matter much which is used.

Is there a method to connect to the VPN before signing into Windows that isn’t so slow to connect?

L2TP for remote/end-user VPN fails a Concept FMEA.

But it should take milliseconds to establish a connection not seconds.
Something is timing out.

PS It’s always DNS.

OpenVPN desktop client for Windows has “Autoconnect on Windows startup” option

If I enable the L2TP connection before they sign in to windows it takes up to a minute and a half to establish the connection

That could be the time taken to fully connect to all domain services “as if they were in the office” given a higher-RTT, lower-BW connection. Check what kind of profile you have given them (hint: desktop shortcuts) etc.

It is difficult to say anything because your report is typically vague., for example I had a look here and there are several different SonicWall VPN products and it is not quite clear which ones you are using (probably GVC in either SSL or IPSEC modes).

Do you hard set the protocol to use in the client?

Which logs would catch that? I don’t see anything that jumps out at me.

Once connected there is no lag, it is always only on connection, and I get the exact same delay on a 15 connection as a 150 connection.

So does the Sonic Wall client and the Cisco client. I think OP should look at that - seeing as they already have Sonic Wall appliance.

GVC 5.0 (4.x has a horrible bug that kills internet throughput even when you don’t have the vpn on)

Method to create the connection (you have to hunt for it, Microsoft moved things around a bit)

  • Control Panel
  • Network and Internet
  • Network and Sharing Center
  • Set up a new connection or network
  • Connect to a workplace (bottom option)
  • Create a new connection
  • Use my internet connection
  • [Enter address and destination name]
    Check the "allow other people to use this connection box

Under adapter settings

  • Properties of created VPN adapter
  • Security tab
  • Type of VPN: Layer 2 Tunneling with IPsex
    • Advanced Settings / Use preshared key
  • Data encryption: require encryption
  • Allow these protocols: Microsoft CHAP Version 2

The Netextender SSL client is even worse.