Solved

The Local Device Name is Already In Use Sonicwall SSL VPN, netextender, can't browse network

Posted on 2014-01-13
21
3,994 Views
Last Modified: 2014-05-20
We just switched from a TZ180 IPsec vpn to an NSA 2400 ssl vpn and our remote users are getting a windows alert when uploading certain files to the server. The Local Device Name Is Already In Use. Then the user can no longer browse the server. See below and attached image. The netextender logs show no errors or events but for the user to gain access again to the server they must disconnect and reconnect via netextender and they are good to go until they attempt to upload something again. Just for a reference, we had a fresh install machine that was just reformatted and we they get the same Windows Alert.
 
Windows Alert
We have tried contacting Sonicwall & a private company that setup the NSA 2400 and they can't figure it out. We have tried remapping drives, accessing via shortcuts only, everything we can think of and we can't figured it out. Any suggestions out there?
0
Comment
Question by:bmbiss14
  • 13
  • 8
21 Comments
 
LVL 24

Expert Comment

by:diverseit
Comment Utility
Hi bmbiss14,

What version of SSL-VPN client are you running?
Are you in Tunnel All mode?
What routes do you have setup?

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.

Does rebooting and then testing temporarily solve it?

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.

Is the computer also trying to run a logon script that would make a network connection for one that is already there?

For 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.

Also check the logon scripts within the SonicWALL and/or the NetExtender client...they are set as batch scripts.

An easy way to test this out and hopefully solve the problem (assuming you have a login script running) is to:

1. Open the Windows Explorer
 2. Tools / Disconnect Network Drive
 3. Note all the drive connections you have (just in case there isn't a login script)
 4. Remove them one at a time
 5. Log off and back on again
Let me know how it goes!
0
 

Author Comment

by:bmbiss14
Comment Utility
Thanks for the quick follow up diverseit. Buckle up!!

FYI, 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 are not apart of a domain. 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. I map them manually. 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. The upload file size is 15MB. We never had this problem with the tz180 IPsec. Just as a double check, we removed all drive info, also from the registry, and tried to browse by manually entering the drive path window explorer and the it did not fix the issue. Again, there were no drives mapped on the machine, but we still received the error. We also installed netexender on a brand new pc and we receive the same issue when uploading a file to the server.

We have tried remapping the drive with a different letter as well, this did not fix the issue.
0
 

Author Comment

by:bmbiss14
Comment Utility
Also, I ran a continuous ping to the server and when the windows alert "local device name already in use" pops up, the ping says "request time out". No events show in the Netextender log, the user must disconnect and reconnect via netextender to get back on the server.

Just to clarify, The error we are receiving is the same error we get if we are not connected to the network at all. This seems to be backing up the theory that we are losing the connection to server, shown by the status time out via ping.
0
 
LVL 24

Accepted Solution

by:
diverseit earned 500 total points
Comment Utility
Just to clarify, The error we are receiving is the same error we get if we are not connected to the network at all.
What do you mean by this? Is this to say that when there is no Internet connection and you try to connect the VPN-SSL you get this error?

Make sure your SonicOS is current. Have you configured your MTU value for the network, here's how to figure your specific MTU value: http://www.experts-exchange.com/A_12615.html

Either the local drive letter is used by a USB mass storage device or else it is remembered from a previous session. Run the following commands just once to fix the problem:
net use * /delete
net use /persistent:no

Open in new window

I'd also suggest to follow these following troubleshooting steps and check if this helps to fix the issue on your computer.

If the system is not on Domain then you may perform clean boot to check if something is stepping on explorer or the stack.

Putting your system in clean boot state helps in identifying if any third party applications or startup items are causing the issue. If yes, you may have to contact the program manufacturer for any updates or uninstall and re-install the program.

Refer the following Microsoft KB article for more information on how to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7:
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7 http://support.microsoft.com/kb/929135

Note: After troubleshooting, make sure to put the computer to start as usual as mentioned in Step 7 in the above KB article.

Let me know how it goes!
0
 

Author Comment

by:bmbiss14
Comment Utility
What do you mean by this? Is this to say that when there is no Internet connection and you try to connect the VPN-SSL you get this error?
.

To clarifty, if I turn on my machine without connecting the internet and without starting the ssl vpn client, my mapped drive shows a red x. When I click on the mapped drive it pops up with that error. It DOES NOT say something like, you are not connected to internet, which I would expect. Instead it gives me the local device name is in use. I already tried removing old names via net use and clean boot mode. Did not fix the issue.

-Thanks..
0
 

Author Comment

by:bmbiss14
Comment Utility
I really don't think it has anything to do with drive names in use to be honest. I have tried it with no drives at all on a fresh machine and I get the error. I am leaning towards and MTU issue. However, on the NSA2400 we have fragment packets enabled and the default mtu is 1500. We DO NOT have "do not fragment" checked in the NSA2400. If it is an MTU setting, why didn't we have this issue with IPsec? We can answer that later FYI, I need to fix this asap.

The other thing that bothers me, if it is the MTU, do I need to adjust it for every user on every machine or should I reduce the MTU size via the NSA SSL VPN settings and that should fix the problem globally?
0
 

Author Comment

by:bmbiss14
Comment Utility
I just lowered the MTU setting on the NSA device and on the remote clients network interfaces to 1492 (per Verizon FIOS recommendations) and it did not fix the error.
0
 
LVL 24

Expert Comment

by:diverseit
Comment Utility
RE: MTU it is done on the SonicWALL WAN setting....that does the rest. Ideally you would want to the the entire network...but that gets ridiculous and the overall gain is not worth it so when people talk about MTU it's specifically on the WAN which will pass that through the VPN etc. Follow this article to get the exact MTU setting its the only way to do it...you can't always solely rely on a type of connection warrants x method. Again, here is the guide: http:/A_12615-Unstable-Slow-Performing-Networks-or-VPNs-just-go-grocery-shopping.html

When I suggested MTU it was specifically when you said "Local Device Name Is Already In Use. Then the user can no longer browse the server." I was not saying necessarily that it would resolve your drive letter issue as that is different.

Did you run the command?

Did you try Clean Boot?
0
 

Author Comment

by:bmbiss14
Comment Utility
I tried adjusting the MTU, at no point do we lose packets. Packet loss is always 0%.
0
 
LVL 24

Expert Comment

by:diverseit
Comment Utility
OK good!

Did you run the command?

Did you try Clean Boot?
0
Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

 

Author Comment

by:bmbiss14
Comment Utility
Tried both, did not resolve the issue.

I should mention again, I tried this on a fresh os install machine and I get the same issue on 3 separate laptops.
0
 
LVL 24

Expert Comment

by:diverseit
Comment Utility
This is bizarre and to clarify all are not on a domain? These fresh OS installs have nothing configured...straight windows defaults?

What AV are you using?

Does this occur in Safe Mode with Networking?
0
 

Author Comment

by:bmbiss14
Comment Utility
AV is Microsoft security essentials. Have not tried it in safe mode with networking. Here is the kicker, we have been using IPsec via a TZ180 for 4.5 years. We just swapped out the units and went to SSL, now this. Very strange. I dont' know what else to do here.
0
 

Author Comment

by:bmbiss14
Comment Utility
Here is another tidbit, the NSA2400 doesn't always show the person being disconnected.
I will refresh in my user log and it says they are connected even though they are not.
0
 

Author Comment

by:bmbiss14
Comment Utility
firmware for a hale mary?
0
 
LVL 24

Expert Comment

by:diverseit
Comment Utility
In my second paragraph in comment (http:#a39781873) I said make sure the SonicOS is current.

What firmware version are you running? If available update it and re-test. If the problem still persists we should open a bug report possible with SonicWALL as this is not normal...I have tons of clients running SSL-VPN all day long with no issues.

A feasible workaround might be to setup VPN client via GVC. It is stable and establishes a VPN connection. There is really no difference in function except with dealing with Macs.

Let me know how if goes!
0
 

Assisted Solution

by:bmbiss14
bmbiss14 earned 0 total points
Comment Utility
Thanks for the follow up. My firmware is current. However, I meant trying to upgrade to an early release. Here is what happened last night. I have never restarted the NSA2400. So I did so from the admin page. When it restarted, I tried to login and it said my username was invalid. I proceeded to login from a remote machine using the SSL VPN to access the network share and that worked. Something clearly was off. I tried to login the admin page multiple times and it never recognized the username. So, from safe mode, I upgraded to the most current early release firmware ( SonicOS Enhanced 5.9.0.3-117o) and reset everything up from scratch. Lord willing, this has appeared to fix the issue. As soon I restarted and it wouldn't let me login the admin, that's a flag to me. Something was confused. Thoughts?
0
 

Author Comment

by:bmbiss14
Comment Utility
Quick question...what does this command do?

net use * /delete
net use /persistent:no
0
 
LVL 24

Expert Comment

by:diverseit
Comment Utility
The fist line command removes all mapped drives and devices. There are two kinds of device names: disk drives (that is, D: through Z:) and printers (that is, LPT1: through LPT3:). The asterisk (*) is used instead of a specific device name to remove the next available device name (basically it's a wildcard). You can shorten this switch to /d if you like.

The second line command controls the persistence of connections created with the net use command. Choosing "no" limits the life of this connection to this session. You can shorten this switch to /p if you like.
0
 

Author Comment

by:bmbiss14
Comment Utility
Very quick help and he gave me a lot of options to help resolve the issue. It ended up being the firmware in the end. Thanks for your help and persistence.
0
 
LVL 24

Expert Comment

by:diverseit
Comment Utility
I'm glad I could help...thanks for the points!
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

This article offers some helpful and general tips for safe browsing and online shopping. It offers simple and manageable procedures that help to ensure the safety of one's personal information and the security of any devices.
Data center, now-a-days, is referred as the home of all the advanced technologies. In-fact, most of the businesses are now establishing their entire organizational structure around the IT capabilities.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

5 Experts available now in Live!

Get 1:1 Help Now