Please help me!!! I ready configure a UTM with a L2TP/IPSEC VPN Server and create a user to access it, but when i trying to connect to my VPN the connection fails. I'm stressful, I don't can connect me, I don't know what's happening I trying connect with the native cliente of Mac OS X Snow Leopard and Windows XP and Seven.
Unfortuantly the change to get this working for Microsoft and possible Apple clientes did not make it into 4.0.6.
What is working is the UTM device as a L2TP client talking to a UTM L2TP server.
I am hoping this change for Microsoft cleints gets into 4.0.7, but if it too big a change, it will be held off to ensure general IPSec stability.Message was edited by: Ross Camm on 1/24/10 11:27:15 PM GMT+10:00
Ok, thanks you, but then how could connect to my vpn. I need a specific client or that I do to connect to my vpn or will need install a previous firmware.
If you are looking at connecting a single PC in a road warrior type scenario then PPTP would be best as the standard Windows PPTP VPN client will work well with this.
If you are trying to connection two LAN, 2 x UTM devices connected via IPSec would be the preferred option in this case.
Thanks but I already have a PPTP VPN, but I want to raise up the security level of my vpn so I want to use L2TP/IPSEC to my vpn server instead PPTP.
We hope to expect to have this running for our version 5 firmware.
If you ensure your pptp passwords are complex, the security is greatly enhanced.
Ok, thanks, but now I have other question, the connection problem in the VPN through L2TP/IPSEC is in the UTM firmware?
I really need a L2TP/IPSEC VPN, because my users want to work under L2TP/IPSEC not PPTP.
Yes, it is a feature lacking from the firmware.
The firmware supports UTM to UTM L2TP, but the Microsoft implementation is still to come.
Ok, thanks very much, you've very helped me, but I have other questions?
The first is: Can I use a previous firmware to solve this problem?
Is very important for me to use L2TP/IPSEC in my VPN.
The second is: When leaves the new firmware?
Version 3 firmware supported Microsoft's native client as long as long as there was no NAT in the path between the client and server.
When NAT traversal was implemented by Microsoft ( XP SP2 ), it did not work with many other vendors equipment.
We were hoping to at least have the same functionaility in version 4 by now, and more, but since it involved some heavey changes to the IPSec code, it has not made it to a production production release yet.
Currently the main client we work with is Openswan...which is what we use on the UTM devices.
The shrew client is becoming more popular I have noticed among users for IPSec road warrior VPN connections.
I know development are aggressively coding in preparation for the next release, of which the latest publically available is 4.5 beta, available at our downloads page.
Download the new ePolicy Orchestrator (ePO) Support Center Extension which simplifies ePO management and provides support resources directly in the console. Learn more about ePO Support Center