topic Re: Multiple password server in samba in Operating System - HP-UX

Multiple password server in samba

PVR — Mon, 23 Aug 2004 09:51:15 GMT

Hi Champs

I want to give authorization from users of two different domains to HP Unix samba server.

Can I specify multiple password servers in the "password server" option"

Thanks !!

Re: Multiple password server in samba

Franky_1 — Mon, 23 Aug 2004 09:59:04 GMT

Hi,

you can specify a list of comma separated servers
For example

password server = ,

Regards

Franky

Re: Multiple password server in samba

Franky_1 — Mon, 23 Aug 2004 10:00:23 GMT

Hi,

you can specify a list of comma separated servers
For example

password server = ,

(Server1 could be a PDC and Server2 a BDC for example)

Regards

Franky

Re: Multiple password server in samba

Jeff_Traigle — Mon, 23 Aug 2004 10:02:03 GMT

Don't think so. Multiple entries in the "password server" entry are intended for redundancy only according to the smb.conf man page. (i.e. If the first DC in list isn't responding, the next one is tried.)

Re: Multiple password server in samba

Sundar_7 — Mon, 23 Aug 2004 12:38:16 GMT

hmm I doubt it. As mentioned above, multiple password servers in the smb.conf file is meant for load balancing and to prevent single point of failure.

But if your domains are trusted, you could give it a try. Try both security=domain and security=server options.

Re: Multiple password server in samba

eric roseme — Mon, 23 Aug 2004 12:51:19 GMT

It's true that the "password server" smb.conf parm allows multiple entries for redundancy only. But your question about "password server" implies that you were inquiring about the ability to join multiple domains from one server, which you cannot do. When you join a domain, your encrypted domain trust password is written to /var/opt/samba/private/secrets.tdb. You cannot have two domain passwords in the tdb, or two secrets.tdb files (in case you were thinking about using smb.conf includes).

However, that is not your only option.

If your Samba logon domain is trusted by the other domain, your Samba pass-through authentication for the trusting user will be validated, assuming that you have local UNIX users set up. Samba 3.0 with winbind has better trusting and mapping than 2.2, but 2.2. will work too.

Also, you can use "user" security on your Samba server and not join either domain. Then you will authenticate each user share access with the local Samba server authentication (probably smbpasswd, but on 3.0 you can specify other password tdb backends with the passdb smb.conf parm).

Eric