![]() ![]() If this solution doesn't help, you can try the next solution. After it is finished, you can check if the error “The local device name is already in use” gets fixed. Tip: You need to replace the username and password with the correct username and password in the command before you run it. Type cmd in the Windows 10 search box and right click the best match Command Prompt to select Run as administrator. Here are detailed steps for you to remap the network drive. So you can try the official solution first, which is said to be an effective fix. Microsoft recommends users to remap the Network drive if they encounter the “The local device name is already in use” error. How to solve the Microsoft Windows network the local device name is already in use error? If you don't know how to fix the error on Windows 10/8/7, you can try the following solutions one by one. There is not enough Disk Space on the network server.Some drives have incorrect or missing drive letters.The File and Printer Sharing is disabled.Problems occurred during network drive mapping process.It’s important to know the reasons for the error “The local device name is already in use”, so that you can fix the problem effectively. What Causes “The Local Device Name Is Already in Use” Error Here, I have summarized several major reasons that may cause “The local device name is already in use” error on Windows 10 after analyzing several posts. However, not many people know what causes the error. The error is associated with the network drive mapping feature of some operating systems, including Microsoft Windows. Microsoft Windows Network: The local device name is already in use. When users try to access a mapped drive on their computer, they may receive the following error message on their computer: Check If There Is Enough Space on the Server What Causes “The Local Device Name Is Already in Use” Error.What causes the error? How to fix it? This article from MiniTool will show you how to fix it with some reliable solutions. Setup the Windows DNS server to forward requests for unknown hosts to the router, or directly to your ISP's DNS (or a public one like Google's or OpenDNS or whatever).īy using the Windows DHCP integrated with Windows' DNS server means that you can/will have DNS entries automatically added/updated for any devices that successfully use the DHCP server (ie: your NAS).Īs above, the Windows DNS will try to answer first, and if it doesn't have a record for that host it'll pass it up the DNS server chain.When you try to access a network drive, you may receive the error “the local device name is already in use”.Configure windows DHCP to hand out the Windows server as the primary/only DNS server for clients to use.Configure Windows DHCP to be allowed to update DNS records of the Windows DNS server.The router will get those requests that the Windows DNS doesn't have entries for, and answer with the right IP (if it's a host the router knows about, which the Diskstaiton should be). Setup the Windows DNS server to forward requests for unknown hosts to the router.While this will work, it's a bad idea, as this will greatly slow down your domain logins while it tries to find the Domain Controller (usually quickly found via a DNS lookup). Set your PC to use the router as its DNS.Therefor any machine that requests a name lookup for the "Diskstation" host from the Window DNS server isn't going to get an address returned.You Windows DNS server is not setup to forward unknown requests to the router.You have no record in your Windows DNS server for the "Diskstation" host.Your PC is using the Windows server as its DNS server.Anyone using the router as their DNS server will have those host names resolved.Your router is aware of the host names of the devices that requested DHCP from it, and it adds those host names to its internal name (DNS) records.Your DHCP is being handed out by your router, and in those DHCP settings it's giving out itself as the DNS server for clients to use.Your "Diskstation" NAS is using DHCP to get it's IP.Ok, based on what you've said here's my guess/suggestions. ![]()
0 Comments
Leave a Reply. |