Samba problems

[Tim Medford]

I have been running samba on an hpux 11.0 server for years without any problems. We are using samba v1.9.17p4. We use a Windows2000 domain controller and have a number of windows clients who connect to the HPUX server via samba. We don't do anything fancy in terms of authentication, people are simply prompted for their unix userid and password each morning when they connect. This is ok with us.

I've recently installed HPUX 11i on a new server and am having loads of trouble getting samba to work. The version of samba that came with 11i is 2.2.3a. I copied our original smb.conf file over. The samba processes start fine, but I cannot connect to anything from windows. I use explorer to map a drive and I keep getting a login dialog...I supply my unix userid and password but it won't accept it.

With this newer version of Samba am I required to validate users against the domain controller and setup that whole smbpasswd database? I'd really rather keep it simple. If we have to login each morning it is no problem.

If you have any ideas, please let me know.

Thanks,
Tim

[John Poff · Accepted solution]

Hi Tim,

It's been so long since I messed with version 1.x of Samba that I don't remember what it does for login validation.

As for the 2.2.3a version, you'll probably need to setup the smbpasswd file. You don't have to validate against your domain controller; that is a separate program [winbind]. Take a look at the mksmbpasswd.sh script. It takes your /etc/passwd as standard input and writes out the smbpasswd file as standard output. Once you have that made, you'll need to enable the accounts in Samba. Then, you'll need to set their passwords in the smbpasswd file. You'll use the 'smbpasswd' command in Samba to enable the Samba accounts and set the passwords. After you have done that, you should be at the same functional level as you are with the old version of Samba. Your users will be prompted for their Unix login and password when they map a share.

Also, you might want to run 'testparm'. It will run a sanity check on your smb.conf file. That should alert you to anything that might need to be changed in the smb.conf file due to moving to the newer version.

JP

[Michael Burbury]

Hi all,

The new version of Samba comes with "swat" a web based admin console.

By defaul it installs on port 901.
in /etc/services:
swat 901/tcp

So, point your browser to:

http://youserverip:901/

Look at ALL the configuration options as the newer version has many more options that you will need to complete.

After adding in everything you need, click on the button to re-start your samba sever for the changes to take effect.

One thing I noticed was for some reason Samba really needs the "guest" unix account to exist (even though I don't use or specify it anywhere?? mystery to me but wouldn't work without it).

[Steven E. Protter]

Your best long term bet Tim is to install the latest samba for 11.00 on the samba 1 machine. Then assuming compatiple data structure and smb.conf as indicated above you should be close to resolution.

Here is a link to download the depots.

https://payment.ecommerce.hp.com/cgi-bin/swdepot_parser.cgi/cgi/try.pl?productNumber=B8725AA&date=

Having the most current December 2003 quality pack wouldn't hurt with any other outstanding issues.

I have samba running quite nicely in a mixed load and UX version environment(11.00 and 11.11). I now do all my patch downloads straight from my desktop browser to a samba shared drive on one workstation. Thats a pretty hefty load enivronment seeing that I'm the biggest bandwidth user in the Corporation most months(my volume being hp.com makes managment feel the bulk of web volume is business related, hee hee).