Does Leopard limit the number the users that can connect to a shared folder? (like XP does?). I hope not, or I hope I can change. I bought a new MacMini to use as a file server in an XP lab, it seems like after 10 or so connections, no one else can get on. This never happened under Tiger. Thoughts?
iBook 14 1.33, eMac 800 superdrive, iBook 12 500, and so many more....,
Mac OS X (10.4.6)
I'll start to answer my own question. Yes, as AFP, 10 user limit. SMB, no.
I had turned on SMB but don't know which protocal was in use. I just turned off AFP and will check if a whole class can get on at once or not in a little while. I don't know squat about networking.
Question is (sorry to be vague) how can I restore my ability to have unlimited connections (at least about 30) like I had in Tiger. I think SMB was unlimited which is how I'm connecting, at least on the Mini I turned off AFP and turned on only SMB. A student who can't connect will be able to as soon as another student gets off.
I can't swear how I had it set up in Tiger, that computer is gone, this is new, I put Leopard on it but can go back to Tiger although I have no idea if Leopard is involved.
Here's more details. 28 HPs running XP, all with wireless cards, wireless router DSL, no file server.
MacMini, wireless too. Made own Location on Mini to be able to put into the right workgroup. All seems to work fine except the user limit.
I poked around a bit and I have no idea if it is relevant (it might be since each connected user generates an additional smbd process), but I found this line:<pre>
max smbd processes = 10</pre>
It was in "/private/var/run/smb.conf". It doesn't appear to be editable (the file is refreshed if it is), and connections are refused if the file is locked. Editing "/private/etc/smb.conf" doesn't seem to help - the copy in "/var/run" always shows "10". It has to be getting the value from somewhere though...
But to reiterate, I don't know if that line is relevant. Hopefully somebody more familiar with smb configuration could shed some light...
Thanks, the other solution maybe to install Unix of some sort on a partition and boot into that for file sharing. I've not done this and have no real knowledge of Linux and all that, might be fun to learn. Could I share folders out to multiple users running some flavor of unix?
I'm afraid that's way beyond me, but I suspect it might be possible to get samba from the source and install it in OS X so you wouldn't have to use Linux. Maybe through something like "fink" or "macports" or something. I really don't know what I'm talking about. Perhaps you could ask in the unix section... who knows, maybe someone over there would even know how to configure the built-in smb in OS X to get rid of the "max smbd processes" limit (if that is what is actually responsible)...
Try editing the file:
/System/Library/CoreServices/SmbFileServer.bundle/Resources/DesktopDefaults.plis t
The '
MaxClients' property is set to an integer value of "10" in the "Desktop" version of the file ("100" for the server version), and editing the number definitely caused a corresponding change in the "/private/var/run/smb.conf" file.
While I have no way of testing the effects of increasing the value on the smb server (I don't have anywhere near 10 clients to test with), modifying it downward definitely lowered the limit of the number of connected users, with the characteristic that a rejected user could successfully connect once someone else logged out first.
It is a .plist file, so I suppose '
defaults' could be used to edit it, but since it is a system file, definitely make a backup, and I would suggest editing it by hand.
Certainly worth a try although I confess I don't know what you mean by using "default" to edit the file, I'll go looking. Not a hacker here, button pusher, not button editor....yet.
The command line utility '
/usr/bin/defaults' is very useful for editing .plist files - for example, a simple one-line command could be used to change the '
MacClients' setting above.
However, when used for .plist files other than user preference files, it also has the effect of changing the format and permissions of the target file, and while it shouldn't affect the file's function, and while format and permissions can be adjusted afterwards, after all that hassle, editing it manually is probably easier. And not going through the hassle might not be ideal for system files.
One particular advantage of the '
defaults' command is that it will generally write in the correct format (unlike an inexperienced user with a text editor for example). However, more than once, I have seen '
defaults' completely erase a .plist file. This isn't an issue with preference files because they are usually regenerated once they are deleted, but the same can't be said for system configuration files.
So maybe I shouldn't have mentioned it - it probably confused the issue - but there are many examples on the web of people going ahead and using '
defaults' on system files and I thought it important to make the distinction clear. I suppose that if the file is properly backed up first, it wouldn't matter either way.
Well, this is way over my head, got so far as to copy the bundle over to another machine, downloaded TextMate, and am lost.
Where can I go for a crash course in this? Is it as easy as editing said file and dumping it back on the Mini? Provided you know HOW?
..."
Is it as easy as editing said file and dumping it back on the Mini? Provided you know HOW?"...
Pretty much, provided the permissions are corrected if necessary (running "repair permissions" in "Disk Utility" afterward should take care of that).
Ok, try it this way: In "Finder", navigate through "/System" > "Library" > "CoreServices", and control-click on the "SmbFileServer.bundle", choosing "Show Package Contents" from the contextual menu. Then, in the new window, click "Resources" (an alias to "Versions" > "A" > "Resources"). In that folder, there should be two files. The one relevant to this thread is called "DesktopDefaults.plist" - drag it while holding the "Option" key (this should make a copy), into a folder somewhere for safekeeping - this will be your backup in case something goes wrong so make sure the contents are intact.
Now, after all the things I said earlier about not using the '
defaults' command, I'm going to suggest doing just that. It wouldn't be my first choice for modifying that file under normal circumstances, but for giving instructions over the internet, it's tough to beat the precision of a "Terminal" command.
So assuming you have your backup copy and verifed that it is the same as the original, log in to an "admin" account, launch "/Applications" > "Utilities" > "Terminal.app" and enter these commands:<pre style="overflow:auto; padding: 5px; width: 500px ; font-size: 10px; border:1">sudo /usr/bin/defaults write /System/Library/CoreServices/SmbFileServer.bundle/Versions/A/Resources/DesktopD efaults MaxClients -int 50
sudo /usr/bin/plutil -convert xml1 /System/Library/CoreServices/SmbFileServer.bundle/Versions/A/Resources/DesktopD efaults.plist
sudo /bin/chmod 644 /System/Library/CoreServices/SmbFileServer.bundle/Versions/A/Resources/DesktopD efaults.plist</pre>
When a password is requested, enter the "admin" password. For security reasons, the keystrokes won't be displayed as you type, so just press the "enter" or "return" key after you are finished. A limit of "50" was used in the example, but that can be adjusted as required (including using "10" to set it back to t he original value).
Edit: Before starting, turn off SMB in the "Sharing" pref pane.
Super, I'll give it a try tomorrow. No worries, I backed up what data is on there (not much yet) and I'll have at it. Can't hurt anything. Thanks for taking the time.