Topic: Samba 2.2.3a

[Serge Chelli]

Hi,

I need to upgrade my sme 5.1.2 with samba 2.2.3a.
My problem is that samba 2.2.3a exists only for redhat 7.2.

When I try to upgrade with the command :

  rpm -Uvh samba*.i386.rpm

I get the message :

error: failed dependencies:
        libreadline.so.4   is needed by samba-2.2.3a-20020206

What can I do ?

Thanks

Serge

[Boris]

I did it (upgrade to Samba 2.2.3a) with "--nodeps" option. It still works. SME has readline-4... package already installed, its just not exactly the same version.
Boris.
P.S.
I even asked on this Phorum how to make it use existing NT domain for accounts authentication, but that thread, died with no results

[Greg Zartman]

I've been working on rolling Samba 2.2.3a into an RPM for SME 5.1.2, but have run into a few problems building the RPM on my SME test box.  I'll continue to see if I can raise some interest in this with the other SME developers that have successfully build RPMS on SME.  Samba 2.2.3a is a really good upgrade as it provides support for backup domain controllers.  

Regards,

Greg Zartman

[Boris]

Being able to use SME as a resource server or BDC will open door for it into bigger enterprises where NT domain structure already exist. First as a "file server" appliance, as an application server of specific task (Workgroup Fax server for example), departmental Dial-in, or VPN point. If you don’t need users shell access or e-mail accounts on SME I don’t see why samba permissions still need to be tied to local accounts. Why limit it to Small and Medium Emterprise, then (as an appliance server for now) it can be used much wider.
Hope to see some time this as an options while configuring SME server.

[Patrick Basile]

Hey guys,

First, since one of my clients uses SME 5.x as a Windows PDC I am always looking for more Samba functionality.  Could one of you let me know how to upgrade to 2.2.3a on a 5.1.x server?  (Steps 1 through XX would be great if possible.)

Second,  since you guys obviously work with Samba and have some more in-depth knowledge I'm thinking you might have an answer for this weird problem.  I am running Win2k Pro systems joined to the SME 5.x "domain", and all the domain users have local admin rights on their systems (!!!! woah !!!!)  This is a real problem.  I didn't do anything special, except that this system was 'upgraded' from 4.1.2.  The strange thing is that under 4.1.2 this was not a problem.

When I try to remove the domain users group from the local admin group on the Win2k systems I get the following error:

=======================================================
Local Users and Groups (Window)

The folowing error occurred while attempting to save properties for group Administrators on computer BENTCREEK006:

"A member could not be added to or removed from the local group because the member does not exist."


This group is listed in Users and in Administrators on the local machine:
THEBRIDGES\unix_group.2147483404
=======================================================

Any ideas why this is happening, and how I can fix it?  Anyone else ever see this strange behavior?  Thanks.

Regards,
Patrick

[guestHH]

Hi Patrick,

Just a quick reply;

Search the dev-info mailing lists. This issue was discussed here.

http://www.mail-archive.com/devinfo%40lists.e-smith.org/

Good luck.

Reagrds,
guestHH

[Serge Chelli]

Hi,

I hust try to install samba 2.2.3a and I get many error messages :

rpm -Uvh --nodeps samba*.i386.rpm

file /etc/samba/smb.conf from install of samba-2.2.3a-20020206 conflicts
with file from package samba-common-2.2.2-6
file /usr/bin/make_printerdef from install of samba-2.2.3a-20020206
conflicts with file from package samba-common-2.2.2-6
file /usr/bin/make_smbcodepage from install of samba-2.2.3a-20020206
conflicts with file from package samba-common-2.2.2-6
file /usr/bin/smbpasswd from install of samba-2.2.3a-20020206 conflicts with
file from package samba-common-2.2.2-6
file /usr/bin/testparm from install of samba-2.2.3a-20020206 conflicts with
file from package samba-common-2.2.2-6
file /usr/bin/testprns from install of samba-2.2.3a-20020206 conflicts with
file from package samba-common-2.2.2-6
file /usr/share/man/man1/make_smbcodepage.1.gz from install of
samba-2.2.3a-20020206 conflicts with file from package samba-common-2.2.2-6
file /usr/share/man/man1/testparm.1.gz from install of samba-2.2.3a-20020206
conflicts with file from package samba-common-2.2.2-6
file /usr/share/man/man1/testprns.1.gz from install of samba-2.2.3a-20020206
conflicts with file from package samba-common-2.2.2-6
file /usr/share/man/man5/lmhosts.5.gz from install of samba-2.2.3a-20020206
conflicts with file from package samba-common-2.2.2-6
file /usr/share/man/man5/smb.conf.5.gz from install of samba-2.2.3a-20020206
conflicts with file from package samba-common-2.2.2-6
file /usr/share/man/man8/smbpasswd.8.gz from install of
samba-2.2.3a-20020206 co

What is the good way to do it ?

Thanks
--
Serge Chelli
www.aceinformatique.com

[Boris]

rpm -Uvh --nodeps --force samba*.i386.rpm

[Serge Chelli]

All is ok now, Thank you.

I nedd to install samba 2.2.3a for test purpose, and there is still lock problem with win2k client.

I will inform the samba team.

Thanks again.

Serge

[Greg Zartman]

Patrick,

The current BDC implementation in Samba will only work on a pure Samba network.  That is, you can't use a Samba machine to act as a BDC for a Win PDC.  Based on how Samba implements BDC functionality, I'm not sure this will change in the near furture.

Regards,

Greg Zartman

[Boris]

According to samba release annoncement for vers. 2.2.3 and 2.2.2
it should be possible (with proper configuration) to use NT domain for authentication if not as BDC, but at least as a "member server"

"New daemon included - winbindd
------------------------------
 
Samba 2.2.2 is the first release to include the winbind daemon.
This code allows UNIX systems that implement the name service
switch (nss) to be entered into a Windows NT/2000 domain and
use the Domain controller for all user and group enumeration.
 
This allows a Samba server added to a Windows domain to serve
file and print services with *NO* local users needed in /etc/passwd
and /etc/group - all users and groups are read directly from the
Windows domain controller. In addition with pam_winbind which allows
a PAM enabled UNIX system to use a Windows domain for authentication
service this allows single sign on and account control across
UNIX and Windows systems."

[Alejandro Lengua]

Hi!
I just have been wondering how did your customer to
make SME 5.x work as a PDC...

Is this a right out of the box configuration?

[Patrick Basile]

Greg (and others),

I'm curious how your experiences with Samba 2.2.3a are going?  Also, would someone point out the process of taking SME 5.1.2 from 2.2.2 to 2.2.3a please?  Greg - any chance you have a package for this process?

One of the things I'm looking for is increased functionality when applying and managing ACL and security in the Windoze model - especially under Win2k.  I hope that 2.2.3a has some better functionality in this area, as I have seen some strange Win2k client behavior when running SME V5 with 2.2.2 as a PDC.

Thanks,
Patrick

[kitkat]

Greg,

Can you have a NT BDC with the SME so both share account?

Thanks

-Kit

[John Gray]

Hello Boris

Are you running 5.1.2 e-smith?

If so, did you have any problems upgrading Samba, or was it pretty straight forward?
Any chance of a short how-to-do-it?

Thanks

John