Problem with Windows shares


  1. Posts : 1,680
    X
       #1

    Problem with Windows shares


    I have three computers at home, with shares mounted as shown here.

    In general, I can use any computer and can "see" the drives of the other computers.
    For example, from computer #1 I can:
    -- Use DOS cmd, and type Y: to get to C: on computer #3
    -- Use Cygwin bash, and type cd Y:/ to get to C: on computer #3
    -- Use Start > Run Y:/ to open an Explorer window to C: on computer #3

    All three methods used to work properly from all three computers ... until recently.
    Now I have a problem with computer #2 only.
    There I can still use bash to do cd Y:/ to get to C: on computer #3 ... or cd T:/ or cd U:/ ... etc.
    But DOS Y: fails
    And Start > Run Y:/ fails ... or T:/ or U:/ ... etc.
    The Start > Run method produces this error:

    How can Y: be unavailable? The bash shell can see Y: just fine!
      My Computer


  2. Posts : 9,789
    Mac OS Catalina
       #2

    Why are you using Cygwin to connect to network drives and also are you trying to get to each computer or a NAS. Bash is used for Linux not Windows. Really need more information.
      My Computer


  3. Posts : 1,680
    X
    Thread Starter
       #3

    Cygwin is Red Hat's emulation of Linux running on Windows. There are others, but I like Cygwin. It works well.

    The shares are for sharing files.
    As I said, bash from computer #2 can "see" all the shares. But Windows explorer cannot. And DOS/cmd cannot.
    I don't know why it stopped working, and only stopped on this box, not the others.

    What other information are you needing?
      My Computer


  4. Posts : 9,789
    Mac OS Catalina
       #4

    Everyone knows what Cygwin is and no it is not just Redhat that created it, nor is it for emulation of Linux. Again are these shares on each computer and also what command in what is not Dos, but just a Command Window. If they are Windows Fat32 partitions, they should show up in windows if you have not blocked services for Smb/CIFS.
      My Computer


  5. Posts : 1,680
    X
    Thread Starter
       #5

    Yes, Red Hat owns Cygwin ... for more than decade.
    Yes, it emulates Linux. And quite well.
    Yes, bash runs on Windows. It, too, works quite well.
    Yes, these are Windows shares. Clue: the thread is titled "Problem with Windows shares".
    No, there's no NAS here.
    Everything is NTFS. There's no FAT32 here.
    What commands am I using, you ask? That was plainly stated in bold italics in the first post.

    I'm not looking for arguments. Just answers.
    Anyway I found the answer at Location Is Not Available When Copying Moving with Mapped Network Drive - Tech Journey
    It calls for adding this to the registry:
    Code:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
    "EnableLinkedConnections"=dword:00000001
    It works.
    Last edited by margrave55; 14 Jun 2017 at 05:48.
      My Computer


  6. Posts : 1,680
    X
    Thread Starter
       #6

    This happened again. A different laptop, but the same problem. And the same solution:
    Code:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
    "EnableLinkedConnections"=dword:00000001
      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 06:32.
Find Us




Windows 10 Forums