Window 10 Mapped Drive Reconnection Issue.


  1. Posts : 34
    Windows 10 Pro
       #1

    Window 10 Mapped Drive Reconnection Issue.


    I'm on Windows 10 Pro 21H2 (64-bit), installed on an MSI Laptop which I use between home and work.

    At home, my laptop is always on WiFi and I have no issues there.

    At work, I connected the laptop to both the internet and the local server (a Synology DS920+ NAS) via LAN & WiFi.
    The issue starts when I restart my computer (while connected via ethernet cable), and the mapped network drives will not reconnect automatically (stay with a red cross mark on them all), even though when they were mapped (via Windows Explorer) the box to "automatically reconnect" was ticked.

    The are often two error messages I get when I can't access the server:

    The more common one:
    "The device name is already in use"

    I then have to either do another restart and sometimes this makes the mapped network drives accessible.

    The second message I see when the restarts don't work:
    "The remote device or resource won't accept the connection".

    This is sometimes resolved by several restarts, or worse case I have to unmap and re-map the network drives.

    One thing I have tested when the mapped network drives are not accessible via ethernet cable is removing the cable and going over to WiFi, then will become accessible within a minute or two. I do prefer using ethernet when at my desk, only resort to WiFi when I'm in virtual meetings away from my desk.

    It never used to have issues like this in the past, but all I need to check is if there's anything I can do on my computer to minimise the above behaviour.

    Thanks.
      My Computer


  2. Posts : 7,263
    windows 10
       #2

    The problem is to map a drive by name windows has to resolve the name often by NetBIOS which can take 20 mins to kick in. You should be able to resolve by removing the share and remake using the IP that assumes the share has a fixed IP
      My Computer


  3. Posts : 324
    Windows 10 x64 1809 LTSC
       #3

    Samuria said:
    The problem is to map a drive by name windows has to resolve the name often by NetBIOS which can take 20 mins to kick in. You should be able to resolve by removing the share and remake using the IP that assumes the share has a fixed IP
    And who said Windows was slow? 20 minutes. Awesome :)
    I have a login script that maps the drives, waits 3 seconds then maps them again.
    To avoid the "Device in use" issue I have set my registry to not reconnect drives.
    It isn't an elegant solution but I rarely see a red X any more.

    But if using IP addresses is faster I'll definately have to give that a go.

    Great tip!
      My Computers


  4. Posts : 34
    Windows 10 Pro
    Thread Starter
       #4

    Samuria said:
    The problem is to map a drive by name windows has to resolve the name often by NetBIOS which can take 20 mins to kick in. You should be able to resolve by removing the share and remake using the IP that assumes the share has a fixed IP
    @Samurai - Thanks for the response. So in essence what you're saying is remove and recreate all mapped network drives, but rather than use the server name (e.g. \\DINGDONG\\Work) I should rather use the IP address (e.g. \\100.10.0.100\Work)?

    Correct?

    And if so, would renaming the mapped drives (via IP address) afterwards result in the same reconnection issue?
    Or would the IP addresses remain as the primary reconnection?
      My Computer


  5. Posts : 7,263
    windows 10
       #5

    Your right with the connection the best is to create a .cmd file so you can run it at any time using cmdline How to Map Network Drives From the Command Prompt in Windows

    The problem windows doesnt search for a pc it asks the master browser Windows 10 and Master Browser settings
      My Computer


  6. Posts : 613
    Windows 10
       #6

    Make sure that the service 'Link-Layer discovery mapper' is enabled in the services and running and also make sure 'Link-Layer Topology Discovery Responder and Mapper I/O driver are both enabled in the Network adapter options.

    Thats all you need man

    Disabling Offline files can cause problems
      My Computer


  7. Posts : 34
    Windows 10 Pro
    Thread Starter
       #7

    Pluginz said:
    Make sure that the service 'Link-Layer discovery mapper' is enabled in the services and running and also make sure 'Link-Layer Topology Discovery Responder and Mapper I/O driver are both enabled in the Network adapter options.

    Thats all you need man

    Disabling Offline files can cause problems
    @Pluginz - I do have "Link-Layer Topology Discovery Mapper" which is set to "Manual".

    In network adapter settings I have both Link-Layer Topology Discovery Responder & Mapper I/O Driver are both checked, so no need to change these.

    However, I followed the recommendation offered up by @Samurai to map using IP address, and I have not had any mapped reconnection drive issues after any of the restarts I've done since the new re-mapping.

    So I'd say that did the trick.
      My Computer


  8. Posts : 613
    Windows 10
       #8

    Hey well done thats great news. Its great when things work.

    Sorry for giving you basic settings.
      My Computer


 

  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 15:16.
Find Us




Windows 10 Forums