With Samba (CIFS) after 16 smbd process no one else can connect.

[Shawn Miller_2]

After I have 16 smbd processes running I get from the windows side either this error, "No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.", or the error, "Windows cannot find the network path. Verify that the network is correct and the destination computer is not busy or turned off...."

The problems go away once the count is under 16. Any suggestions.

[Mel Burslan]

in your samba/cifs configuration file, do you see a directive like this :

max connections = 16

try increasing it to whatever value and stop and start samba.

[Shawn Miller_2]

I have looked at a couple configuration files and saw not parameter of;
max connections. It would not make much sense for a default to be so low but that does not mean it isn't. Either way if you can tell me what that particular configuration file is called and where it is located I would appreciate it.

[Patrick Wallek]

This should be in your smb.conf file. According to the man page for smb.conf (from HP's CIFS client distribution) the default is supposed to be 'max connections = 0' which means unlimited connections.

If the parameter is not in your smb.conf file, add it and then stop / restart Samba to make sure it gets activated.

The line should look like:

max connections = 0

or if you want some limited number rather than unlimited:

max connections = 50

[eric roseme]

Also check your kernel tunables:

nflocks
nfiles
nprocs

If they are at system defaults, you will run out of file locks and other stuff, but usually file locks will hit first around 20 users or so. If you have other processes on the system using locks, then you could hit it at 16.

See the admin guide chapter 12 for correct settings:

http://www.docs.hp.com/en/B8725-90101/B8725-90101.pdf

Eric Roseme
Hewlett-Packard