Home › Forums › OS X Server and Client Discussion › File Serving › 2 windows clients, >150 samba connections?

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • February 19, 2004 at 8:47 pm #357430
    option8
    Participant

    i have 10ish mac users and 2 windows users connected to a 10.3 server. the macs are connecting via AFP, and the mac users have local/netinfo user accounts on the server. the windows users are authenticating through our NT domain, and connecting via smb.

    the two windows (one on 2000 and one on XP) users are somehow generating upwards of 150 active samba connections, which grinds the server to a shuddering halt (which is why i’ve limited the samba connections to 50 now). much as i enjoy seeing the CPU graph hovering near 100…

    anyhoo, the server itself is set as a “domain member” of the NT domain (no, we’re not up to active directory on the windows side yet) and is registering with the WINS server. per joel’s recommendation, i have turned on strict locking on the share in question, and turned off oplocks, but the situation remains – the longer the windows clients are connected, the more zombie connections are created, and thus more swap and cpu is eaten up.

    has anyone else seen this behavior in samba before? i used to run samba 2ish on a linux box with the same set of mac and windows clients (the macs connecting via smb as well, then) and never had this particular problem come up. i’m hoping i can pin it on the NT domain somehow, so i can expedite its replacement with active directory/ldap, but any ideas would be greatly appreciated at this point.

    March 17, 2004 at 5:19 pm #357618
    schandor
    Participant

    I found this in a Computer World article. Hopefully it helps you out.

    “If you do host the user homes on a machine other than the PDC, there is another bug that quickly becomes obvious. It’s in the implementation of Samba, where the server won’t drop connections, meaning any user file activity will open another connection. I had 17 machines generate more than 200 connections in under an hour, effectively hanging up my machine. There are two solutions to this issue: The first is to edit the smb.conf file on the file server and add the following line near the beginning of the file (without the quotes): “dead time = 10″. This lets the server drop unused connections after 10 minutes. ”

    Here is the link to the entire article.
    [url]http://www.computerworld.com/softwaretopics/os/macos/story/0,10801,90699,00.html?f=x253[/url]

    March 17, 2004 at 6:17 pm #357619
    option8
    Participant

    ah ha! i knew i wasn’t the only one…

    and this part of the article –

    The other solution I found was in the Windows settings for the file server. It’s completely counterintuitive to Windows structure but works in this case. I changed the machine from being a Windows domain member server to a stand-alone machine. This has the effect of forcing the server to use OD authentication instead of NT authentication, which in this implementation is the source of the problem.

    – is what i ended up doing. i added the 2 windows users as local/netinfo users and they were able to log in. there’s still some oddity with one of them, though, but i’ve managed to get him logged in as guest, so everything’s at least working now.

    i’m curious as to whether the 10.3.3 server update fixed any of these issues.

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Comments are closed

Copyright © 2025 AFP548. All Rights Reserved.