Win7 shared, Win7 access is normal, but XP occasionally encounters this problem, waiting to continue to observe.
Http://blog.sina.com.cn/s/blog_79c0eb8701016ajg.html
Always encounter Win7 file sharing error prompt is generally "insufficient storage space to handle this command"
And then the network share won't open. To reopen the server service you need to restart
Although the reliability of the CIFS share of Windows has always been no hope, but the frequent break or just depressed
Today I searched a few articles according to modify their own system as if a little effect is being observed ...
Phenomenon
Client prompt "Insufficient storage space to process this command"
Server-side logs
"The server cannot be allocated through the system non-paged share because the shared area is currently empty. ”
"The server cannot be allocated through a system non-paged share because the server has reached the configured limit for non-page sharing allocations. ”
Modify 2 Locations
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\largesystemcache
LargeSystemCache modified to 1
Hklm\system\currentcontrolset\services\lanmanserver\parameters\size
Size modified to 3
Official explanation of key value action
LargeSystemCache
Determines whether the system maintains a standard size or a large size file system cache, and influences how often the S Ystem writes changed pages to disk.
0
Establishes a standard size File-system cache of approximately 8 MB. The system allows changed pages to remain in physical memory until the number of available pages drops to approximately 1, This setting are recommended for servers running applications the do their own memory caching, such as Microsoft SQL Server, and for applications this perform best with ample memory, such as Internet information Services.
1
Establishes a large system cache working set the can expand to physical memory, minus 4 MB, if needed. The system allows changed pages to remain in physical memory until the number of available pages drops to approximately 25 0. This setting are recommended for the most computers running Windows, Server on large networks.
In a nutshell, this is about the balance between the FS cache and the system's paging, as it relates to the file system.
For applications such as databases, this value is not recommended because the cache is managed by the app itself
For home now we have a lot of memory so I personally think everyone should be set to 1 so improve performance
Of course, I personally think it doesn't matter if I share it with the Internet.
Explanation of the second value
Size entry (which is in the Hklm\system\currentcontrolset\services\lanmanserver\parameters subkey)
Option setting
Minimize Memory used 1
Balance 2
Maximize data throughput for file sharing 3
Maximize data throughput for network applications 3
This value may be the official lazy did not write the specific mechanism also may be I did not find in summary only the recommended configuration method
No detailed explanation
In addition, we also recommend that you modify a value
Hkey_local_machine\system\currentcontrolset\services\lanmanserver\parameters\irpstacksize
I looked at this value and filesystem Driver about it. I don't think it has anything to do with this, so I didn't move this value.
========= Turn ============
Http://technet.microsoft.com/en-us/library/cc976153.aspx
LargeSystemCache
http://answers.microsoft.com/zh-hans/windows/forum/windows_7-networking/Server cannot/ 77653be4-7548-e011-8dfc-68b599b31bf5?msgid=3a306f75-a44e-e011-8dfc-68b599b31bf5
The server cannot be allocated through a system non-paged share because the server has reached the configured limit for non-page share allocations.
http://blog.csdn.net/ufojoan/article/details/7608716
The server cannot be allocated through a system non-paged share because the server has reached the configured limit for non-page share allocations.
http://support.microsoft.com/kb/232271
How to optimize Windows NT Server usage Registry