[Samba] Samba in a Win2000 / NT Enterprise

Blanchard, Michael MBlanchard at grandaire.com
Mon Mar 11 11:28:04 GMT 2002


On that server I'm running 2.4.7 (stock redhat) My servers don't have a
heavy load yet, so that could be a difference.  I've ran 2.4.19-pre2-ac3
on another server with good results, I don't know if it will fix your
issues, but it could be worth a shot.  2.4.18 has been solid here too.
Did you compile it or install the rpm?  If you compile it, maybe try the
rpm?  (I'm not a samba guru, but I learn every day) Good luck!  I'll
help as best I can.  You might also want to look at using ext3 (not
related to samba) as it would help with fsck's you have to go through.
Migration to ext3 is relatively painless, just make sure to update your
bootdisks with a kernel that supports it.


-----Original Message-----
From: Noel Kelly (VPN) [mailto:nkelly at tarsus.co.uk] 
Sent: Monday, March 11, 2002 2:10 PM
To: Blanchard, Michael; samba at lists.samba.org
Subject: Re: [Samba] Samba in a Win2000 / NT Enterprise


Michael,

Are you running a 2.4 kernel ?  I am have had numerous problems with
winbindd dying under 2.2.20.  Also, on Friday I had two separate
incidents of unkillable smbd processes left on the our Samba 2.2.3a
servers after the Win2000 clients crashed.  These are nasty as they
prevent the disk being unmounted and one is left with no option but to
reboot and let fsck do its stuff on remount.  Having to reboot both our
main servers on Friday afternoon in these circumstances is not
impressing the hoi poloi.

I was rather hoping these unkillables had gone away with 2.2.3a as they
were so constant in 2.2.2 that they almost scuttled the whole Samba
migration. Perhaps the 2.4 kernel's improved file system management
might smooth these over.

Thanks,
Noel



----- Original Message -----
From: "Blanchard, Michael" <MBlanchard at grandaire.com>
To: <samba at lists.samba.org>
Sent: Friday, March 08, 2002 6:47 PM
Subject: [Samba] Samba in a Win2000 / NT Enterprise


> Winbind has been in use here for almost a month and I've had no 
> problem. I would suggest first off upgrading to 2.2.3.  Just do an rpm

> -e samba-client and samba-common first so you clear up the 
> dependencies. Then go to samba.org and read the documentation for 
> winbind.  It's actually pretty easy to do, and has been working really

> well over here. There isn't anything as cool as sitting in front of a 
> linux computer and logging in with "ops+username" :)  You have to add 
> about 7 lines of winbind-specific stuff into you smb.conf file, but 
> that's all availible on the samba.org webpage.
>
> -----Original Message-----
> From: Chris Sarris [mailto:Chrissarris at hotmail.com]
> Sent: Friday, March 08, 2002 12:37 PM
> To: samba at lists.samba.org
> Subject: [Samba] Samba in a Win2000 / NT Enterprise
>
>
> Hello,
> I am currently integrating 20 workstations and 5 Servers (all Dell
> Products) running Red Hat 7.2 (2.4.7-10) into a Windows 2000 / NT 
> Enterprise network of about 2,000 users.
>
> I have been using a Samba server (version 2.2.1) with 
> "security=domain" so that any user with a W2K domain logon can access 
> the Samba file server.
>
> However, I want to move into full integration and set up all Logins to

> Redhat (wether Gnome or KDE) to authenticate on the W2K corporate 
> domain and recieve back a security access tolken so that I can have a 
> unified logon point and then access shares or printer on any W2K 
> computer in the domain that I have rights to access.
>
> I have considered the Pam_smb module but it only seems to query the 
> W2K corporate domain for a successful username / password logon. 
> However, that means anyone of the 2,000 members in our Corporate 
> Domain could log on to our boxes instead of the group of 20 that I 
> want to give access to. But inaddition to that... I don't think that 
> the Pam_smb passes back
> *any* kind of security or access tolken so that I can access other
> domain shares.
>
> I think Winbind is my answer, but it seems like it has not been 
> released in a stable manner yet.
>
> What do you suggest?
> thanks for your help,
> Chris
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>





More information about the samba mailing list