This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 33%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVD%3C/text%3E%3C/svg%3E)
Hello everyone,
For some weeks I am having trouble with Microsoft Windows 10 version 2004, build 19041.508.
Let me explain the case:
Normally on my Windows 10 workstation, I have a manually created share towards a shared folder on another workstation (in this case Windows 7 or XP (XP is needed for some machinery)), let's say \server\share
This used to work without any problems but for a couple of weeks I get the message "The local device name is already in use". When it comes to the settings, nothing has been changed by me.
When I remove the network share, reboot, and recreate the share, it works until I reboot again. Then the same problem occurs. It doesn't matter if I use the NETBIOS name in the share or the IP address, the result is the same.
When I delete the network share, reboot, and make a shortcut on the desktop towards the specific share, it works flawlessly. When I add the network share again, the problem comes back again, and also my shortcut doesn't work anymore.
So long story short, access by network share doesn't work
Access by shortcut (when the share is deleted), works.
When the error occurs, I can ping the machine on which the share is on.
I also did an NSLOOKUP on the specific machine on which the share is on and this turned out fine.
What I've tried:
I have this issue in 3 different cases now, 2 of the cases involves computers within a domain, 1 case within a workgroup. All cases have this issue with Windows 10 2004 in combination with Windows 7 or Windows XP.
It has been working for years without any problems and I can't put my finger on it on where the problem lies.
So currently I am working with the workaround -> adding shortcuts on my desktop.
Some tips or advice would really be appreciated :))
I'm not sure that I fully understand this comment:
I have a manually created share towards a shared folder on another workstation
So on PC1, you have a share, \PC1\Data, that points to a local drive, C:\Data,. Then on PC2, you created another share \PC2\Data2 and instead of pointing it to a local drive+folder on PC2 you pointed it to \PC1\Data???
Is that correct? Why do that?
Or did you mean to say... "I have manually mapped a network drive from my pc to a shared folder on another workstation"? So the D: drive on your workstation points to \PC1\Data, for example?
Hi MotoX80, I ment "I have manually mapped a network drive from my pc to a shared folder on another workstation"? So the D: drive on your workstation points to \PC1\Data, for example?"
I am sorry this was unclear.
Then where do you get the "network share the name already exists" message?
If you map the drive and set it to reconnect at sign-in, then there is no need to remap it,
Before we go further, I would like to confirm the following questions:
This used to work without any problems but for a couple of weeks I get the message "network share the name already exists". When it comes to the settings, nothing has been changed by me.
As MotoX80 said, when and where do you get the "network share the name already exists" message?
What's the result when you run net use command? Please share more details to help us understand your question better.
The share is being created just like your screenshot. As mentioned, when I do that, it works until reboot. When you open Explorer after the reboot and double click on the share, the message "The local device name is already in use", while there is nothing using that device name whatsoever.
Is your PC and the target machine in the same domain?
Are you logging on to your PC with a domain account?
Did you specify a userid+password when you mapped the drive or did you default to using the account that you logged in with?
As CandyLuo requested, what does NET USE show? Run that command from a "normal" command prompt and also from a "run as administrator" command prompt.
Does NET VIEW \target-machine-name show the available shares?
You noted that the problem occurred against Win7+XP. Do you have the same problem mapping a drive to another Win10 machine?
On the target machine, do you see any errors in the security eventlog when you try to access the share?
Sorry about asking so many questions, but it's not obvious what the problem is. You really should replace Win7 and XP machines as they are out of support and are a security risk.
In two cases yes, I use a domain account and in the third case no. An no, I didn't specify a username and password.
When it comes to mapping, shares towards another Windows 10 machine or even Windows server 2016, works without any problems. I know that XP and Windows 7 are not supported anymore but since there is machinery depending it there is no possible way for me to change that at this moment.
On the target machine doesn't show any errors in the eventlogs when I try to access the share.
The NET VIEW \target-machine-name shows the shares. When it comes to NET USE, the result is the same. It works, until reboot.
The weird thing with this issue is that it happens with 3 different customers with different setups. Only thing that is connected is that it involves Windows 10 v2004 and older Operating Systems. One day it works without any problems, the next day it's broken.
Hello,
Do you have another machine on the NetBIOS domain that has a shared folder with the same name? If you share it with a different name do you get the same problem?
Miguel Fra
www.falconitservices.com
There isn't another machine that uses a share with the same name.
I haven't tried another name yet. The problem is, is that the machinery that uses them, depend on certain names. I will try to make a workaround for this and will post the outcome.
I was able to recreate that message. On my laptop I had mapped a drive to a VM that I have. I set it to reconnect, and then rebooted. The VM was not started and I tried to access the drive. In explorer the drive showed with a red X and in a command prompt, it showed as a disconnected drive.
I then started the VM and was able to access the network drive. In the command prompt the status changed to OK. I was also able to use the dir command to view both the drive letter and the UNC path.
On your system, if you issue the same NET and DIR commands, do they work or do you get an error?
I am currently not at the client, but I will check the above as soon as possible and post the results.
In the meantime, thank you for all your efforts, it's much appriciated :)