Drive letter mapping - wrong label?

Discussion in 'Misc Discussion' started by zdevilinside, Oct 5, 2020.

  1. zdevilinside

    zdevilinside Active Member

    upload_2020-10-5_14-49-35.png

    Whenever I map a drive to S: or U:, I get the wrong label brought across. The way I am mapping things is like this:

    \\192.168.7.12\Music Videos\ with it set as S: but the share comes up as "4k Movies and TV".
    \\192.168.7.12\Data with it set to U: but it comes out as "3D_Movies".

    I have unmapped, remapped without fixing it.

    I have tried Net Use as documented here:
    https://tompai.pro/computers/tip-unmap-disconnect-network-drive-via-command-line-cmd/

    This is what I get:
    upload_2020-10-5_14-53-30.png
    Microsoft's regedit suggestion doesn't apply - the key doesn't exist:
    https://support.microsoft.com/en-us...explorer-may-retain-the-name-of-a-disconnecte

    Nor does this work:
    https://superuser.com/questions/198499/change-network-drive-label-by-command-line

    Any suggestions?
     
  2. 57331

    57331 Guest

    I don't really know that much about network drives and such, but have you tried checking and resetting the drive labels in the Synology DiskStation Manager and checking the directory trees using WinDirStat?
     
  3. Ghost

    Ghost Forum Crapolator

    Shoot at this point I need a Tut on how to do a network share, been like 10 years since I set up a cross over setup, yep old way, but today new tech, and all the stuff I have I could use a good server in home hehe, any chance of doin a simple run through to give the steps, I would appreciate it, OR a good tut from a youtube etc.. be fine, but the answer to your Q is, I remember that you have to allow for sharing on the source, then set the PC using that drive up to access that drive? very vague memory, but that was with a crossover Ethernet type config.
     
  4. zdevilinside

    zdevilinside Active Member

    Yes, I have. Nothing worked.
     
  5. zdevilinside

    zdevilinside Active Member

    It seems to have worked itself out. It was a real pain in the rear. :)

    Now, if I could only get Arris to update the firmware on their mAX mesh routers so I can use something other than the 192.168.7.0/24 subnet....
     

Share This Page