windows xp sharing error: Not enough server storage is available to process this command.

problem

windows xp - cannot load a shared folder from a xp terminal… getting this error message:
---------------------------
hpcom03
---------------------------
\\hpcom03\testeveryone 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.

---------------------------
192.168.0.30
---------------------------
Δεν είναι δυνατή η πρόσβαση στο \\192.168.0.30\101025_maria_argo. Μπορεί να μην έχετε δικαίωμα να χρησιμοποιήσετε αυτόν τον πόρο δικτύου. Επικοινωνήστε με τον διαχειριστή αυτού του διακομιστή για να διαπιστώσετε εάν έχετε δικαίωμα πρόσβασης.  
Δεν υπάρχει αρκετός διαθέσιμος χώρος στο διακομιστή για την εκτέλεση αυτής της εντολής.
---------------------------

solution:

Error types:

    * Network
    * Networking
Error messages:
    * Not enough server storage is available to process this command.
    * Not enough memory to complete transaction. Close some applications and retry.
These error messages on a computer, which we will call computer A, can indicate the IRPStackSize bug on the other machine, the server that has the share, which we will call computer B. Go to that other computer, B, open the event log, and check for event ID 2011. If this is present, it is a strong indication for this particular bug. The two computers again:
   1. The computer trying to access a share on the other computer over the network, displays the error message, "Not enough …". Let's call this one the client.
   2. The server where the share is, needs to have its IRPStackSize parameter increased. Let's call this one the server, even if it is just a desktop computer.
    To repair it, you have to set or increase the IRPStackSize parameter in the registry on the server where the share is, i.e. on computer B.
    There are many reports (below), indicating that a value of 15 is not enough, and only values in the range of 16 to 25 solved the problem.
    The most successful values used to be 16 and 18, but recently we have more reports of 20 and more. If you want to solve the problem quickly, try 20.
    It is not quite clear whether higher values incur any cost in terms of memory usage or performance, but it is conceivable that they don't. If so, then we probably should just set the value to its maximum of 50 and forget about it.
    And don't forget to reboot after each change, because only that makes the new value effective. Thanks to everybody who tested and reported!
    Please add a comment below to report which value you used to make it work. If you find the time to experiment, please report the lowest value that worked. Please try also to set it back to a lower value and recheck whether that indeed makes it fail. Reboot after each change.

Here is the offending registry value:
    HKEY_LOCAL_MACHINE
     \SYSTEM
      \CurrentControlSet
       \Services
        \LanmanServer
         \Parameters
    IRPStackSize DWORD 0x0000000f (15)

to update  from registry file, just create a .reg file with the follow lines this will apply the value 18(decimal)
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters]
"IRPStackSize"=dword:00000012

Check for the presence of the value named IRPStackSize. If it doesn't exist, create it as type DWORD and make sure you have the capitalization absolutely correct (5 upper case, 7 lower case characters), because the system strangely seems to depend on that. Make sure also that you haven't by mistake added a leading or trailing space as described in this comment below.

With base set to decimal, enter the value 16 or higher. 15 is the default, so entering 15 should have the same effect as removing that value altogether. My problem solved with 18.

Reboot the computer!