If you work for a large organization, buying VPN Tracker for your Mac VPN Connectivity needs, should be a no-brainer. But for those of you who work for smaller companies who question a lot of expenses, and you have Mac computers, then Lobotomo’s free IPSecuritas VPN Client may be for you. If it works out for you, I do encourage you click their Donate button and give what you can. It took me quite awhile to finally get IPSecuritas working with the latest SonicWALL firewall I’ve been connecting to, an NSA 3600. The firmware version on the SonicWALL I’m using is SonicOS Enhanced 6.2.2.2-19n. Your settings may differ if you are using a different SonicWALL or a different firmware version – but things should be similar, in the same classes of firewalls. And the IPSecuritas version I’m using is V4.6.1. And a somewhat unrelated blog post on Connecting a Mac to a SonicWALL via LT2PĪll of the above are somewhat old articles, often referencing much older versions of SonicOS firmware or the IPSecuritas client itself.Sean LaBrie’s article on Configuring IPSecuritas for Use with a SonicWall TZ190 Enhanced.a blog post by kleetus on SonicWALL enhanced firmware.wimpog’s blog reply on SonicWALL NSA 2400 VPN.The basic IPSecuritas to SonicWALL V3 guide.I credit the following guides, for getting me started: I read several guides, and tried countless combinations of settings. Most of the above articles attempt to explain their settings by describing the settings/options to select. And the problem is, with older versions of the firmware or IPSecuritas client, some of the settings/options have changed and it’s a bit difficult to understand some of what is described. I’m going to show you the setup primary via screenshots. With some descriptions only going into detail about options that may differ on your setups. Keep in mind that what worked for me, may not work for you. Plus, you really need to have administrative access to your SonicWALL, or know the I.T. person who does, who can help you sort this out. On this page, click the Edit link to the right of WAN GlobalVPN. See below:Įnsure your settings are the same as below: VPN > SETTINGS > ADVANCED TAB See below:Ĭhange the “Shared Secret” from yourpresharedkey to a key that you choose. The error "Local device name is already in use" simply means that you are trying to map a network connection with a drive letter that already is assigned to some local device.Set your Advanced tab options as per below. Is the computer also trying to run a logon script that would make a network connection for one that is already there?įor example, if a drive letter is mapped through the Windows Explorer, and then the same drive letter is trying to be mapped through a logon script, you can get the same error.Īlso check the logon scripts within the SonicWALL and/or the NetExtender client.they are set as batch scripts.Īn easy way to test this out and hopefully solve the problem (assuming you have a login script running) is to: You need to have your network administrator see what drive letters are trying to be mapped, which local device already has one of those letters assigned, and give it a different local drive letter. Thanks for the quick follow up diverseit. Buckle up!!įYI, we never had any of these issues with our old TZ180 IPsec VPN. These are all individual laptops running Windows 7 64-BIT Pro. They just plug in via Ethernet when they are in the office and browse to the network share drive on a server running SMB2008. We don't really use the server, it's mainly just a file server. Netextender version: 7.0.196 (we were on a version of 6 and I updated hoping it would fix the issue, it did not) When the remote users access the VPN, they startup netextender on their machines and login. Then they browse via the drive as they usually do in the office. SSL VPN router is to our XO (LAN) subnet interface. Initially we did not have tunneling all enabled. I enabled it to test, it did not fix the issue. We do not run any custom scripts on login. However, by default netextender runs it's batch scripts automatically. I disabled them and it did not fix the issue. Our drive (r:) and is always present under my computer. When they users are in the office it works with no issues at all when they are on the local LAN. This error only occurs when they attempt to access the drive via SSL VPN. Just to clarify, they can connect and can work, but when they upload a certain size file we can repeat the error every time. We never had this problem with the tz180 IPsec.
0 Comments
Leave a Reply. |