"Not enough memory" error when PCs try to access shared drive on an XP Home PC

Discussion in 'Home Networking' started by Martin Underwood, Oct 17, 2005.

  1. I have three PCs which are netowrked together via a router: XP Home desktop
    (PC1), XP Home laptop (PC2), Win 98 desktop (PC3).

    All of a sudden, the XP laptop (PC2) and Win 98 desktop (PC3) cannot access
    shared drives on the XP desktop (PC1) whereas they used to be able to.

    PC1 can access shared resources on PC2 and PC3, and PC2 and PC3 can access
    resources on each other.

    The symptom of:

    - net use l: \\pc1\c
    - dir \\pc1\c
    - Windows Explorer "map a drive" to \\pc1\c

    is a "not enough memory" (from Win 98) or "not enough server storage is
    available to process this command" (from Win XP) error.

    Looking at a LAN trace, I can see that the Win 98 PC (PC3) makes a Session
    Setup / Tree Connect SMB request, to which PC1 responds Session Setup
    (error) - DOS error 8: Not enough memory.

    PC1's System Event Log reports "The server's configuration parameter
    "irpstacksize" is too small for the server to use a local device. Please
    increase the value of this parameter." but unfortunately the error message
    on MS's site (KB177078) relates to a key
    HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters\IrpStackSize
    that doesn't exist on XP Home - it's probably a W2K or W2K3 Server
    parameter.

    Help!

    I'm wondering if it dates back to when I installed Norton Ghost on Friday. I
    might try uninstalling it again to see if the problem goes away.
     
    Martin Underwood, Oct 17, 2005
    #1
    1. Advertisements

  2. Martin Underwood wrote in message
    43542a69$0$49807$:
    I feel a real idiot. I must have got my pathname wrong in Regedit: when I
    searched again I found the key IrpStackSize. Very embarrassing!

    For whatever reason, the default value of 11 (0x0B) that was present in
    ControlSet001, ControlSet002 and Current ControlSet was no longer
    sufficient. Having increased the value to 14 (0x0E) [*] and restarted the
    Server service (or rebooted PC1), everything's fine.


    [*] The KB recommends increasing it in units of 3 until the problem goes
    away.
     
    Martin Underwood, Oct 18, 2005
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.