Map Network Drive issue


  1. Posts : 2
    Window 10
       #1

    Map Network Drive issue


    I have three NAS units attached to my LAN.

    Their names differ only in the first letter.

    I Map network drives for example

    NET USE A: \\Aserver\x /Persistent:Yes
    NET USE B: \\Bserver\x /Persistent:Yes

    or by the Map Network Drive in the GUI

    This is all OK.

    However, when opening the File Explorer "My Computer" the mapped drives often show the Same server.

    (NET VIEW displays correctly)

    Worse, there seem to be no way from the GUI to determine that actual mapping,.

    Properties does not reveal the mapping and indeed the entire name is editable.

    I have a suspicion that Win 10 actually changed one of the mappings and caused immense trouble. No documentation, sorry.

    I am aware of the other nuisance of drives failing to reconnect.

    All this started when I commissioned a new laptop.

    Version 10.0.18362 Build 18362
      My Computer

  2. hsehestedt's Avatar
    Posts : 2,148
    Windows 10 Pro, 20H2
       #2

    Welcome to TenForums!

    Just to make sure I understand correctly, are you saying that A: and B: are both mapped to the same server even though you issued a NET USE to map A: to one NAS device and B: to another device?

    In all my years using Windows, I have yet to see that happen on its own.

    What happens when you disconnect those NAS devices and reconnect them again?

    Also, any chance of posting a screenshot of what you are seeing in File Explorer? Click on "This PC" so that we can see the connected network drives as in the below example:

    Map Network Drive issue-image1.jpg
      My Computers

  3. Samuria's Avatar
    Posts : 6,051
    windows 10
       #3

    A & b are reserved for floppy drives try different drive letter
      My Computer

  4. hsehestedt's Avatar
    Posts : 2,148
    Windows 10 Pro, 20H2
       #4

    Actually, that is no longer true...

    Map Network Drive issue-image2.jpg
      My Computers


  5. Posts : 2
    Window 10
    Thread Starter
       #5

    NAS Connections


    Hi.

    Yes, I should have taken a screen dump but I was chasing a silly problem.

    I use Robocopy to mirror really vital stuff from one NAS to another.

    File Explorer lied about the mapping and I ended up creating a whole new mirror where it was not intended.

    I'll try to reproduce the problem, but it might not be for some time.

    Oh! and I use A: & B: because I have no connected floppies.

    I've been in computing for a L-O-N-G time and it is inconsistencies that get my dander up.
      My Computer

  6. hsehestedt's Avatar
    Posts : 2,148
    Windows 10 Pro, 20H2
       #6

    Thanks for the clarification. Here's a suggestion:

    Since you are using robocopy to mirror one NAS to the other, why not simply dispense with any drive letter references at all?

    You could simply specify UNC paths like this:

    Code:
    robocopy \\Aserver\x \\Bserver\x /mir
      My Computers

  7. Berton's Avatar
    Posts : 10,530
    Win10 Pro Versions 2004 and 2009/20H2, Win10 Pro IP_Dev, Win10 Home 1909
       #7

    I have 2 NAS drives connected via Ethernet cables to my Router, no Server involved. No problem Mapping the Public folder on both drives from within File Explorer on any computer Wired or Wireless/Wi-Fi. And I used File and Printer Sharing turned on and no switches on any command.

    Historically Windows used to start the mapping/lettering of Network drives at Z: working back up the alphabet as needed, not so much in Win10.

    I keep drive A: available and Legacy USB active in the BIOS as I have some USB floppy drives for use when a client "finds" the disks left over from older computers.
      My Computers

  8. jimbo45's Avatar
    Posts : 10,484
    Windows / Linux : Arch Linux
       #8

    Berton said:
    I have 2 NAS drives connected via Ethernet cables to my Router, no Server involved. No problem Mapping the Public folder on both drives from within File Explorer on any computer Wired or Wireless/Wi-Fi. And I used File and Printer Sharing turned on and no switches on any command.

    Historically Windows used to start the mapping/lettering of Network drives at Z: working back up the alphabet as needed, not so much in Win10.

    I keep drive A: available and Legacy USB active in the BIOS as I have some USB floppy drives for use when a client "finds" the disks left over from older computers.
    Hi there

    Connect Network drive defaults to starting at "Z" and working backwards but using the drop down in file explorer you can assign it to any unused letter

    Map Network Drive issue-screenshot_20200124_083646.png


    Cheers
    jimbo
      My Computer

  9. Berton's Avatar
    Posts : 10,530
    Win10 Pro Versions 2004 and 2009/20H2, Win10 Pro IP_Dev, Win10 Home 1909
       #9

    No question, no problem here.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 12:13.
Find Us




Windows 10 Forums