> Thanks Matt,
> I have some more comments:
> > > Server: HP-UX 10.20, samba 2.0.3
> > > Clients: NT 4.0 w/ SP3
> > > I have configured samba to share the home directories, plus several hard
> > > drives where users also have read/write access. I have setup smbpasswd
> > > file using the "convert /etc/passwd" script. I also have a map file to
> > > correlate the NT usernames to Unix usernames. From Network Neighbor
> > > user's can access their home directory with no problems. However, as
> > > soon as they pick another displayed share folder NT responds with "The
> > > network name cannot be found." Another message is "No network provider
> > > accepted the given network path.". What is this?
> > > From a command prompt, the net use x: \\sail\/ responds with "System
> > > error 67 has occurred". (sail is the samba configured HP).
> > You want to share the root directory? It is listed as a share in smb.conf?
> > Not a good idea, I think.
> I agree, but I get the same message on any of the shared directories, except
> for [homes].
> > > My workaround was to enable Wide Links and make symbolic links from the
> > > user's home directories to the hard drives. It's not how I want to keep
> > > it, but....
> > Is "Wide Links" the same as "follow symlinks"?
> Yes.
> > I do this all the time, works OK. Saves a lot work trying to list shares
> > and the user can map to just one drive letter and still get to their
> > files and folders on filesystems not in their home directory. Will work
> > with NFS mounted filesystems too.
> Yea it works OK, but I'd like to know why there's a difference. It also
> affects some applications config files, but I can adjust them to look at the
> homes directory, which is equivalent to the current user's home directory.
I believe the way samba works on the homes share is to create a share using
the entry in /etc/passwd (on the UNIX side, if you are using NIS samba should
look in the NIS passwd file). Samba is doing this for you, no need to specify
the path in smb.conf. It works because the user name is the same in UNIX and
samba or you have mapped the samba login name to the UNIX login name.
> > > What makes the 'built-in' [homes] share different than any other shares
> > > I'm trying to create?
> > This shares the user's home directory to that user, doesn't share home
> > directories not belonging to that user. But you can still use a symbolic
> > link in UNIX to allow the user to chdir to another users home directory,
> > if it works in UNIX should work in Windows using Samba.
> Again, I'd like to know why [homes] works. I didn't even have it in the shares
> originally and then I added it to test it out. And then it worked, but only
> that particular share. I don't like it when the s/w isn't consistent.
> > > I've also noticed in the log files that it will report "couldn't find
> > > service disk3" when '/disk3' is the share.
> > What is in the [disk3] entry in the smb.conf? What are the hpux
> > permissions and owner/group for /disk3?
> members of those groups. I have it set to as close to 'default' as possible.
> Trying to eliminate variations.
You may need writeable = yes, but first lets make sure that browsing works.
On a share like this, which is probably not owned by any of the users,
samba uses the guest account for browsing. Do you have a guest account set up
in hp-ux for this purpose? Don't use user "nobody", it will not work right.
If you have an annoymous ftp account you can use that. Otherwise, create
a guest login on hp-ux, then specify that as your guest account in smb.conf
Example /etc/passwd entry:
pcguest:*:501:201::/home/pcguest:/usr/bin/false
Once you get browsing to work, you may not need writeable as I am assuming
that the users in eng and mkt have subdirectories under /disk3 that belong
to them. Or there are subdirectories with "rwx" for everyone or perhaps
even that /disk3 itself is "rwx" for everyone. Or you want read only.
Now of course UNIX will not allow "pcguest" to browse a share that has no
"r-x" permissions for everyone...Also, on shares that are mapped to a
particular owner, such as [homes], the guest account is not used for
browsing.
Hope this answers your questions.
--
Matt Alderson GIS Specialist . Arizona Game and Fish Department
voice-mail: (602) 789-3610 . Phoenix, AZ 85023 U.S.A.
by