Can't map network share, but I can access it


  1. Posts : 7
    Windows 10
       #1

    Can't map network share, but I can access it


    I'm new to Windows 10 network shares and mapping, so please be kind!

    I have a SAMBA network share on a WD NAS drive, with login credentials, named "bobloblaw". I am trying to access it from my laptop running Windows 10 Pro v. 1909, via WiFi, on the local network.

    I can access it from my laptop by typing "\\bobloblaw" in the File Explorer. This then becomes "> Network > bobloblaw", I can see the various folders in the window below, and "bobloblaw" appears at the bottom of the navigation pane under "Network."

    But I can't access it by pointing and clicking in the File Explorer, or from e.g. Word's "Save" dialog. And I can't map it either:
    • File Explorer: When I double-click on Network in the navigation pane, then bobloblaw in the righthand window, it opens a browser window with HTTP access to the NAS control panel, instead of opening the NAS itself.
    • Application save dialog: When I click Browse, then Network, all I see is my computer. I don't see the NAS (or anything else on the network) at all.
    • Map drive: When I try to map the drive, enter "\\bobloblaw", and enter my credentials, I get an error message saying "Windows cannot access \\bobloblaw: Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose." When I click Diagnose, it thinks for a bit and then says, "Troubleshooting couldn't identify the problem."


    I believe all the relevant services are running: Function Discovery Provider Host, Function Discovery Resource Publication, SSDP Discovery, and UPnP Device Host. A search yields a number of documents explaining how to activate network discovery, but not what to do when that doesn't work; and how to map a drive, but not what to do when the usual instructions don't work; etc.

    Where do I go from there? Any advice appreciated.
      My Computer


  2. Posts : 6,979
    windows 10
       #2

    When you connect you need to connect to a share not the drive is \\pc1 is the PC not a share a share is \\pc1\accounts if it's saying it can't find it use the IP not name is \\192.168.1.12\sharename
      My Computer


  3. Posts : 12,486
    Win10 Version 21H2 Pro and Home, Win11 Pro
       #3

    I use 2 NAS drives connected by cable to my Router and if the drives are seen in File Explorer I can Map the Public folder on either or both using both Wired computers and Wireless/Wi-Fi computers. Public (\\WDMYCLOUD2)
      My Computers


  4. Posts : 7
    Windows 10
    Thread Starter
       #4

    Thank you, Samuria. That was the bit I was missing. Works just fine connecting to \\bobloblaw\share1.

    As a note for anyone else who is trying to figure this out, I actually have two shares on the same drive, accessed using the same credentials. But Windows apparently (Google it) won't let you do that, so I have to access one by drive name (\\bobloblaw\share1) and the other by IP address (\\192.168.xxx.xxx\share2).
      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 01:21.
Find Us




Windows 10 Forums