Mount error 12 - cannot allocate memory to share printer

[brencam]

Just installed PCLOS on my laptop as a dual boot (with XP). I also have a linux server setup with samba shares server on my printer and on some server directories.

When I boot laptop in XP all the shares are accessible and work correcty. When I boot the laptop in PCLOS and start SMB4 I can see the shared resources, but cannot mount the printer. I am getting a 'Mount error 12 - cannot allocate memory' from  smb4.

I've seen this error reported elsewhere when working with WIndows shares and there apparently is a registry fix for this. However this is not relevant here since my (Samba) shares are running on the Linux server.

Any ideas/suggestions?

Patrick

[Texstar]

Make sure your printer share doesn't have any spaces in the name.

[brencam]

Just checked the share name - no spaces - format is '//HOSTNAME/HL-5250DN-series'. (It's a Brother 5250 model printer). As stated earlier everything works correctly when booted from XP. When I try to mount from PCLOS/smb4 I get the previously mentioned 'Mount 12 error - can't allocate memory'

I'm wondering if  it has a problem with the '-' chars in the share name. Could that be a problem?

Thx for looking.   

[YouCanToo]

Just checked the share name - no spaces - format is '//HOSTNAME/HL-5250DN-series'. (It's a Brother 5250 model printer). As stated earlier everything works correctly when booted from XP. When I try to mount from PCLOS/smb4 I get the previously mentioned 'Mount 12 error - can't allocate memory'

I'm wondering if  it has a problem with the '-' chars in the share name. Could that be a problem?

Thx for looking.   

I think that you are correct with the "-" being the issue

[djohnston]

Found the following here:  http://linux.derkeiler.com/Newsgroups/comp.os.linux.networking/2006-10/msg00629.html

Check the Event Log on the Windows machine that fails to allow it's share
to be mounted under System. Look for a red X, and the word Error. The
Source is Srv. The error will be:

The server's configuration parameter "irpstacksize" is too small for the
server to use a local device. Please increase the value of this
parameter.

If you have this error on the Windows machine that fails to have it's
share mounted, then do the following...

This key in the system registry must be modifed or created:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer
\Parameters\IRPStackSize

If the key is there, increase it a bit to say 15 or 18. If the key does
not exist, as in my case, create a new DWORD Valute. Name it
IRPStackSize. Double click on it to edit the value, put a check on the
Decimal radio button for the Base so that you can see the parameter value
as a decimal value and not a hexidecimal value. Give the new key a value
of 15 and reboot. If that is not enough, raise it a litte to let's say 18
and then reboot again. The problem is solved. Go mount your samba shares.

I'd check the Windows host first.

[brencam]

@djohnston - Sorry but this is an all Linux setup that I'm testng. If you read my initial post carefully  you'll see that the server and printer are running Linux - so Windows is irrelevant here.

Whille I can access my Samba shares, I can't mount the printer.