none
Access to Shared folders on Windows-7-64 bit, from Win-Xp-SP3, are lost ........AFTER A WHILE

    Question

  • 0) This is a business, with a domain type login.

    1) Restart Windows-7pro-64-bit (IP address is static on this computer   WIRED LAN)

    2) Shared folders on the Windows-7pro-64-bit computer are accessible FROM a Windows-Xp-SP3 computer.

    3) Later in the same day, \\computername is not accessible.    ERROR RESPONSE IS " You might not have permission to use this network resource. Contact the administrator of the server to find out if you have access permissions. The specified server cannot perform the requested operation".    (ALL ACCESS IS LOST    FROM    XP-SP3 COMPUTERS) (WINDOWS-7pro-32-bit COMPUTERS CAN STILL ACCESS THE SHARED FOLDERS on Windows-7pro-64-bit )

    3a) Windows-7pro-64-bit computer can still access the Windows-XP-SP3 computers over the network. (But not the reverse)

    4) RESTART the Windows-7pro-64-bit computer.

    5) Windows-XP-SP3 computers can now access the Windows-7pro-64-bit shared folders.

    6) Sometime later in the day, all access is lost to the shared folders on the Windows-7pro-64-bit computer. ( AND THE CYCLE STARTS OVER AGAIN)(WINDOWS-7pro-32-bit COMPUTERS CAN STILL ACCESS THE SHARED FOLDERS)

    7) No changes to the settings of the shared permissions are made during this time period. A simple restart gets the sharing to work normally again.

    8) Windows-7pro-32-bit never has a problem connecting TO the shared folders anywhere, on any OS.

       Windows-7pro-64-bit never has a problem connecting TO the shared folders anywhere, on any OS.

    9) Possible related EVENT VIEWER ERROR MESSAGE  "Source: srv   EventID=2017  The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations."

    10) Computer has 12 GB of ram  and  18418MB  Virtual memory.

    11) Motherboard is "ASUS P6T WS Professional"

    12) Network adapter is the integrated "Realtek PCIE GBE Family controller"  driver version 7.3.522.2009; PowerManagement is turned OFF on this adapter.  Second network adapter on this motherboard is DISABLED.

    13) Software run during the day is;   ProEngineer Wildfire 3 64 bit;  Delcam Powermill 2010 64 bit; Outlook 2003; Trend Micro Worry-Free Business Security Advanced; Internet Explorer 8.

    14) Automatic updates have been ON since the Windows 7 install and the computer has internet access.

    15) XP mode was installed in the past. It is now UN-INSTALLED.

     

    Wednesday, September 15, 2010 1:56 PM

Answers

  • Hi,

     

    While the issue occurs, can you access the shared folder via \\IPAddress\Shared_Folder?

     

    Based on my understanding, you encounter the following problems:

     

    Symptoms:

     

    A Windows 7 based machine running as file server and share files with client machine running XP. System experience an error as Event ID 2017 saying that “The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations”. But restarting server service can temporarily solve the problem. And this problem occurs everyday.

     

    Cause:

    nonpaged pool value not enough for acting as server

     

    Resolution:

     

    Please change the following registry keys to let Windows XP know that Windows 7 64bit computer is used as a file server:


    1. Find HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache and set it to 1
    2. Find HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size and set it to 3
    3. Add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\MaxNonpagedMemoryUsage and set to 0xFFFFFFFF

    Now see if the problem get resolved.

     

    Best Regards

    Dale


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Friday, September 17, 2010 6:46 AM
    Moderator

All replies

  • Hi,

     

    While the issue occurs, can you access the shared folder via \\IPAddress\Shared_Folder?

     

    Based on my understanding, you encounter the following problems:

     

    Symptoms:

     

    A Windows 7 based machine running as file server and share files with client machine running XP. System experience an error as Event ID 2017 saying that “The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations”. But restarting server service can temporarily solve the problem. And this problem occurs everyday.

     

    Cause:

    nonpaged pool value not enough for acting as server

     

    Resolution:

     

    Please change the following registry keys to let Windows XP know that Windows 7 64bit computer is used as a file server:


    1. Find HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache and set it to 1
    2. Find HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size and set it to 3
    3. Add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\MaxNonpagedMemoryUsage and set to 0xFFFFFFFF

    Now see if the problem get resolved.

     

    Best Regards

    Dale


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Friday, September 17, 2010 6:46 AM
    Moderator
  • I made these changes today, 9-22-2010, and will let you know the results.

    I assumed that you wanted these edits on the windows-7pro-64bit computer!

    I also hope you saw, that a windows-7pro-32bit computer never has a problem getting files from the windows-7pro-64bit computer. I can always get access to shared files in the 64bit from the 32 bit. Why does the windows-7-32bit always work?????

    Wednesday, September 22, 2010 7:52 PM
  • As to the question

    "While the issue occurs, can you access the shared folder via \\IPAddress\Shared_Folder? "

    THE ANSWER IS    NO

    Wednesday, September 22, 2010 7:54 PM
  • I have not experienced the problem since making these changes. Something is apparently different between the 64bit version of Windows-7, and the 32bit version. The 32bit version does not need these edits; it has not ever failed.
    Friday, October 01, 2010 7:04 PM
  • Thanks for the Help .. I was stuck several hours in  this problem . It get solved now . Is this problem occur only in 64bit system ?? Because we have  many windows 7 (32 bit) machines even with lower memory( i.e 2GB) than the problematic one ( which has 4Gb) ,  but never faced things like this  earlier .

    Another question is what is nonpaged pool value exactly ?

    Thanks once again for your tips.

    Thursday, January 20, 2011 11:41 AM
  • 1. do these changes get made on the xp machine or the windows 7 machine

    2. My problem is the reverse, the server/pc is my XP machine and my windows 7 machine can't see it

    Wednesday, February 02, 2011 4:14 PM
  • Hi,

    I have an similar issue:

    when \\ComputerName\share fails i can access \\IPaddress\share, but after a while it also fails with \\IPaddress\share.

    it only happens with one share, access is denied to \\ComputerName\share1 but i can access \\ComputerName\share2;

    it happened when the share was on a Vista Pro machine, and continues to happen now with an windows 2008 r2 fondation.

    restarting the server doesn't restore access - restarting xp client restores access until it happens again.

    nothing in the event viewer;


    • Edited by NTavares Monday, June 18, 2012 11:25 AM
    Monday, June 18, 2012 10:57 AM
  • I also get a lot event ID 2017 and 2019 when I write a large file (several gigabytes) to a shared folder from a Linux PC.

    The server is running Windows 7 Professional SP1 x64, up to date.

    I happens each time a few seconds after the copy started.

    Is this a bug? After all writing a file to a shared folder is not some special circumstance, it is a basic operation, and today every second file is over a gigabyte.

    Regards,

    David

    Sunday, September 16, 2012 4:32 PM
  • HI,

    i had this share issue from windows xp sp3, so i planned to change registry settings in windows 7 64bit pc, successfully changed for first two regsitry keys but following MaxNonpagedMemoryUsage word cant find in the parameter section (stucked here).

    So, how do i proceed now?

    Regards,

    Vinay

    Monday, April 01, 2013 7:13 AM
  • The fix as posed by Dale Qiao worked perfectly to correct the problem for me.

    The problem only occurred when trying to access Win7-64 from WinXP-32 computers.

    The registry fix is applied to the Win7-64 machine.

    You can restart the 'Server' service and this will put the changes into effect and you can test immediately.

    Monday, April 29, 2013 3:55 AM
  • Just an additional note on this.  I was experiencing a similar issue on my Win7 32-bit box accessing shares from XP virtual machines being hosted on the same box.  I applied the registry fixes above and have not experienced the issue again.  If it matters, it is a 64-bit box, but running Win7 32-bit OS as a workstation in a development environment.

    Monday, October 07, 2013 12:27 PM