![]() We never had this problem with the tz180 IPsec. Just to clarify, they can connect and can work, but when they upload a certain size file we can repeat the error every time. This error only occurs when they attempt to access the drive via SSL VPN. When they users are in the office it works with no issues at all when they are on the local LAN. ![]() Our drive (r:) and is always present under my computer. ![]() I disabled them and it did not fix the issue. However, by default netextender runs it's batch scripts automatically. We do not run any custom scripts on login. I enabled it to test, it did not fix the issue. Initially we did not have tunneling all enabled. SSL VPN router is to our XO (LAN) subnet interface. Then they browse via the drive as they usually do in the office. 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. We don't really use the server, it's mainly just a file server. ![]() They just plug in via Ethernet when they are in the office and browse to the network share drive on a server running SMB2008. These are all individual laptops running Windows 7 64-BIT Pro. Buckle up!!įYI, we never had any of these issues with our old TZ180 IPsec VPN. Thanks for the quick follow up diverseit. 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. 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.ĭoes rebooting and then testing temporarily solve it? What version of SSL-VPN client are you running?
0 Comments
Leave a Reply. |