Samba and HPUX10.20

[Nick D'Angelo]

Sure thing.

both the smbd and nmbd are running and in fact, I have re-started them after every change.

From unix, I can grep nmbd but not smbd.

In the workgroup, I have entered the unix hostname so that it will stand out and the netbios name I have the same unix hostname.

the first share that I was playing with is /tmp.
the path: /tmp
Guest account: nobody
valid users: three userids
admin users: mine and my backup one
read only: yes
guest ok: yes
hosts allow: blank
hosts deny: blank
short preserve case: no
browseable: yes
available: yes
dos filetime resolution: yes

[Nick D'Angelo]

Do I have to 'Join' the NT domain?

[Mark Vollmers]

Nick-

I'm not sure about the workgroup name. Here's how we have it set up. We have the domain name of X, of which we have member (for lack of a better term) servers. These include the unix server (A), our windows server (B, C, D) and each NT or Xp computer (E-M). All of these show up in the network neighboorhood. in the workgroup, I have put in X (domain name). It should match up with whatever your pc has as the workgroup in the network window.

as far as processes, it looks like an smbd process is started each time a share is successfully linked up. If I have /tmp mapped to the v: drive of 5 machines, then there should be 5 smbd processes, but not before. as long as it says that it is running in swat, then you should be okay there.

let's see, what else? have you configured tcp/ip? do you have DNS or WINS configured to match up with the system (for us, the IP points to server B, which is our main server).

Lastly, try mapping the drive, cause they don't always show up. map it to a letter as \\server\tmp. it will either not work (not found), map up (validating the user logged in in windows to the smbpasswd file) or ask for a login. Don't worry, we'll get you going sooner or later. :)

Mark

ps: I found the O'Reilly book extremely helpful for configuring, and you can either get a hard copy or look at it online.

[Nick D'Angelo]

Getting there I think. I really appreciate your help.

I made a change as it was pointing to the wrong WINS server.

When I try to map to \\ip.add.0.0\tmp, it says.

The account is not authorized to log in from this station.

[Nick D'Angelo]

Hello again.

Well I can browse to it via the network places/neighbourhood.

I can access the shares, but the users can not yet.

I am guessing that i need to create an smbpasswd for each user, but where will they authenticate, Unix or WIndows?

Thank you plenty.

[Mark Vollmers]

almost there. the first thing I'd try would be to make a share and enable guest access and try to map it up on some computer. once you get one to work, you can set up specific users and restrict the shares. what I did was to add an entry in smbpasswd for each user (I thought that I saw that you can do this for each user in /etc/passwd with one command, but I can't find it anywhere. maybe I imagined it). Use the unix user name for this. the user name for both windows and unix must be the same for samba, though. if they're not, however, you can fix that. I made an alias file that relates the two (also works for groups). for me, my unix is vollmers and windows mvollmers, so I set the one to be an alias for the other. the file was called users.map, and I put in in the same directory as the smb.conf file (I suppose it doesn't matter). There is a option in the global config for a username map that you can point to that file. Give that a go and see what happens.

Mark

[Nick D'Angelo]

Points to everyone and especially Mark V. Bonus points to you.

I am up and running and administration is an absolute breeze.

The last issue to deal with is the password/account/alias file business.

I am interested in the following:

I think it would be easiest if the users use their windows account and password.

What would be the best solution this way?

I will also look at the O'Reilly book.

Thanks again.

[Mark Vollmers]

Nick-

glad to hear that you've got things up and running. you can use windows logins by mapping an alias to them (create a users.map file with unix name(s) = windows name(s). however, to use windows passwords as well(assuming that the users have not set one equal to the other), you might want to have a look at domain level security or server level security. both of these should allow you to let the windows server handle the authentication. Sorry I can't give you more info, but I've got user-level myself, but it looks to be straight-forward. Good luck!

Mark