Shared folder permissions issue

[jacktheripper88]

Hi everybody, got a really odd duck of an issue that I can't seem to get fully sorted out.

This is the environment I'm working with:
"Server": Lenovo with windows 7 pro (don't have the specs on me at the moment) that has an extra hard drive that is currently sharing 2 folders out to the network, running the windows firewall.
Client PCs: 2 Desktops running windows 7 Pro, one AIO running windows 10 Pro, and a laptop running windows 10.
Network is a simple setup, an 8 port Startech switch and a Bell Fibre Op modem.

So here is the issues. I have a client that has a stand alone PC acting as a file server, he and a few others have a mapped drive to a folder called "Files". Quiet often throughout the day they get the following message:

"\\SERVER\Files is not accessible. You might not have permission to use this network resource.
Contact the administrator of this server to find out if you have access permissions."

"Not enough server storage is available to process this command."

Now if they try to open access this folder again they might get in or they might receive the same message over again. I have also run a continuous ping test while trying to access this folder and gotten that error, but had 0 packet loss.

So far I have determined the last line from this error is misleading and not actually referring to the available space on the hard drive, the drive in question is 1 TB and is currently only holding about 30-40GBs. The "Server" has simple sharing turned off, password protected sharing is currently turned off for home/work and private networks, the EVERYONE group is added and has full permission and was set to be inherited on all sub-folders and files.

As I mentioned earlier about the storage line being misleading I came across an old forum that discussed that error and mentioned the fix for it was to add an entry to the LanmanServer\Parameters called IRPStackSize. I set the stacksize to 35 just to see if this would correct the issue. But after restarting the "Server" to allow this change to take effect it the issue will go away for a few hours or may not crop up until the next day.

Really not sure what more to do or check. I'm going to run chkdsk on this drive when I get a moment they can do without their files for a little bit.

 

[PliotronX]

Try accessing by IP rather than Netbios name, e.g. \\192.168.1.31\Files and also you might just have to create a user account on the server with the share and punch that in as I've had hit or miss luck with unprotected shares, plus its just prudent.

Edit- nevermind, this is by design:

"
In Windows 7 “Everyone” only includes every user except Guest account of the local system. The system cannot recognize any credentials of other systems. To access shared recourses of the local computer, wherever you access it from, you need to use a valid credential of the local computer.

When you try to setup the shared printer/scanner, it should ask for credentials. Then Windows will remember the credentials so that username and password are not required the next time when you access."

I recommend using FTP for anonymous access rather than allowing 'anonymous' access on SMB because it can effectively allow anonymous logon to the computer...

 

[jacktheripper88]

I may have gotten this sorted out. During my time onsite moving from PC to PC I forgot I hadn't checked the Event Viewer on the server, I found a ton of event ID 2017 and found a registry fixed that solely dealt with this error and have a PC act as a File Server.
It has to do with the fact that by default Windows 7 has a limited amount of resources dedicated for handling this type of traffic, so I changed the following registry entries:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache was changed from 0 to 1
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size was changed from 1 to 3

So far I have connected up to their server and haven't seen that Event ID 2017 srv error anymore. So fingers crossed