I'm trying to figure out if there's any way to have multiple virtual servers on the same machine, each server having different shares. Barring running multiple smbd processes, I don't see a way. Is there one? Thanks! -Ken
On Thursday 23 September 2004 07:00, Ken D'Ambrosio wrote:> I'm trying to figure out if there's any way to have multiple virtual > servers on the same machine, each server having different shares. > Barring running multiple smbd processes, I don't see a way. Is there one?Yes! It can be done. You must create one master server configuration. It will create the master server as seen in the Windows networking browser. In its smb.conf file you will have something like: [global] ... workgroup = BIGBIRDS netbios name = ALBATROS netbios aliases = CRANE MUGABIRD ... include = /etc/samba/smb.%L.conf Then for each alias (CRANE and MUGABIRD) you would create an /etc/samba/smb.'name'.conf file like: /etc/samba/smb.crane.conf: --------------------------------- [global] netbios name = CRANE .... [share1] ... /etc/samba.smb.mugabird.conf: ------------------------------------- [global] ... netbios name = MUGABIRD ... [share2] ... I hope that is clear enough. - John T. -- John H Terpstra Samba-Team Member Phone: +1 (650) 580-8668 Author: The Official Samba-3 HOWTO & Reference Guide, ISBN: 0131453556 Samba-3 by Example, ISBN: 0131472216 Hardening Linux, ISBN: 0072254971 OpenLDAP by Example, ISBN: 0131488732 Other books in production.
> > Maybe you know yet another trick - is in possible to arrange > > so that when someone connects to \\box\share, samba ignores > > login username and validates user with: > > > > login=share > > password=<user-supplied password> ? > > > > This will allow poor souls from Win9x boxes (which as you know > > are unable to supply usernames, only passwords) to supply username > > as a share name. Whatever I try with [default] and/or [homes] section, > > I can't achieve this... > > No so! Install the appropriate Windows Network driver on Win9X, and get it to > log onto the domain. Then set the registry setting using the policy editor so > that no user can log on without prior validation. This definitively solves > your problem. A samba hack is entirely the wrong approach.Yes, win9x uses local user name of the logged-in user for all subsequent network logins, AFAIK. This will work if all other machines on the network are domain members. However, if that user subsequently wants to log in to another samba box which is _not_ a member of the domain and does not allow this user to log in with that username, [s]he will see a password prompt *only*, whereas user sitting on NT box will see a prompt with both username *and* password. Or am I missing another way to log into such samba box? -- vda