Windows 10: 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!

:)

 

Problem with folder shares in WIndows 10 - too many connections

Hi

I did. I got answer that this is by design. If that it true, I see a huge class action law suite on the horizon....

 

Problem with folder shares in WIndows 10 - too many connections

We have a small network of 10 PCs. The users connect to an application via Citrix. In addition some data is written to a local computer which has Pervasive SQL database (we call it our "server"). This is done for very short periods of time . All PCs and
the servers ran WIn7 Pro without a problem.

Recently we upgraded the workstations to Windows 10 Pro PCs. We first left the old "server" with WIn 7 , and saw that all was running fine. We then replaced it with a WIn 10 Pro PC. and here is the problem:

After several minutes of working, the users cannot connect to the "server" with an error that there are too many connections to the shared folder.

The limit in WIn 7/10 is 20 concurrent users. We only have 10 PCs.

I checked under Computer Management > Shared Folder > Sessions and I see there is a big difference between Win7 and Win10:

In Win7 the users appears temporarily in the sessions list and disappear, so there are only 4-5 at a time. In WIn 10 , every user that uses the database is listed indefinitely. They also appear numerous time in the list, which very quickly reach the 20
mark. The only way to remove a user is to reboot the "server".

I checked it on other Win 10 networks, and the behavior is the same.

I don't know of any way to change this behavior of Win 10 sharing.

Is there a way to have it share as Windows 7?

Thanks

Moved From:

• Windows
  
• /
• Windows 10
  
• /
• Network & internet
  

 

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.

 

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?

 

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.

 

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[/quote] It works.

 

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[/quote]