Samba Installation

Need assistance installing Samba on AIX 5200-10 with a host name of banora.

Downloaded samba-3.0.4.0.bff off the Bull Freeware site
and installed it with smit okay.

Am using the IBM Redbook SG24-6004-00 Samba Installation, Configuration, and Sizing Guide July 2000 based on ver 2.0.6 as this is the only detailed AIX/Samba installation guide I could find.

The book says to test the installation, which failed.

I did the following.
# find / -name smbclient
/usr/local/samba/bin/smbclient

# /usr/local/samba/bin/smbclient -L banora
Error connecting to 192.168.0.144 (A remote host refused an attempted connect
operation.)
Connection to banora failed

# ping 192.168.0.1
PING 192.168.0.1: (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp seq=O ttl=64 time=l ms
64 bytes from 192.168.0.1: icmp=seq=l ttl=64 time=l ms
64 bytes from 192.168.0.1: icmp seq=2 ttl=64 time=l ms
192.168.0.1 PING Statistics 3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1/1/1 ms

# ping 192.168.0.144
PING 192.168.0.144: (192.168.0.144): 56 data bytes
64 bytes from 192.168.0.144: icmp_seq=O ttl=255 time=O ms
64 bytes from 192.168.0.144: icmp_seq=l ttl=255 time=O ms
64 bytes from 192.168.0.144: icmp seq=2 ttl=255 time=O ms
192.168.0.144 PING Statistics 3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms

The /etc/samba/smb.conf and /usr/local/samba/lib/smb.conf files are as follows.

[global]
workgroup = OPEN SOURCE
server string = Samba 3.0.4.0
security = user
encrypt passwords = Yes
smb passwd file = /var/samba/private/smbpasswd
log file = /usr/local/samba/var/log.%m
mangle case = Yes
[homes]
force user = %U
read only = No
hosts allow = 129.183.
[printers]
comment = All Printers
path = /usr/spool/samba
printable = Yes
browseable = No
[public]
path = /tmp
guest ok = Yes

The Redbook says that inetd.conf should include smbd, nmbd, and SWAT entries with the SWAT entry to be uncommented. I can find none of the entries in inetd.conf.

Using Seamonkey I ran http://banora:901 but nothing came up in 5 minutes. I suppose this is because of no SWAT entry in smb.conf

Have a series of AIX and Windows machines on a P2P network and was looking to use Samba to communicate between them.

Would appreciate some help to get the samba-3.0.4.0.bff installation up and running.

Cannot proceed to chapter 3 Basic Configuration as cannot get SWAT up and running.

Thanks

Sorry forgot to add testparm results

# /usr/local/samba/bin/testparm
Load smb config files from /usr/local/samba/lib/smb.conf
Processing section" [homes]"
Processing section" [printers]"
Processing section" [public]"
Loaded services file OK.
Server role: ROLE STANDALONE
Press enter to see a dump of your service definitions

Regards

add "swat 901/tcp" to /etc/services
add "swat stream tcp nowait.400 root /usr/local/bin/swat.sh swat"
refresh -s inetd
Now browse to http://banora:901
Use swat to start services or:
Start smbd by entering "/usr/local/samba/sbin/smbd -D"
Start nmbd by entering "/usr/local/samba/sbin/nmbd -D"
Now try smbclient

Pritchard thanks for reply.
However I could not get your instructions to work.
Your reply gave me clues to search web

Did this as you asked
add "swat 901/tcp" to /etc/services

The next line of yours was added to /etc/inetd.conf not
/etc/services.
add "swat stream tcp nowait.400 root /usr/local/bin/swat.sh swat"
Now tried #refresh -s inetd and got
0513-095 The request for subsystem refresh was completely unsuccessful.

One web page said to be sure inetd path was correct.
#find / -name swat and got 2 hits in my conputer
/usr/local/samba/sbin/swat
/usr/local/samba/swat

So I tried these lines in /etc/inetd.conf
"swat stream tcp nowait.400 root /usr/local/samba/sbin/swat.sh swat" and
"swat stream tcp nowait.400 root /usr/local/samba/swat.sh swat" but
keep getting the 0513-095 error.

All the articles I saw never mentioned " swat.sh swat " they all said " swat swat " so I tried these lines in /etc/inetd.conf

"swat stream tcp nowait.400 root /usr/local/samba/sbin/swat swat" and
"swat stream tcp nowait.400 root /usr/local/samba/swat swat"
"swat stream tcp nowait.400 root /usr/local/bin/swat swat"
but still keep getting the 0513-095 error.

Would appreciate further help.

Regards

My bad. I missed the /etc/inetd.conf and the correct path to swat. I was running a swat.sh script that set the LIBPATH due to a unique install of Samba. I no longer need that and have corrected it in the /etc/inetd.conf.

Looking at your "find / -name swat" output it appears that swat is /usr/local/samba/sbin/swat. See if swat will start from the command line without errors by entering "/usr/local/samba/sbin/swat".

Based on your reply and my errors I would revise my procedure to read:

add "swat 901/tcp" to /etc/services
add "swat stream tcp nowait.400 root /usr/local/samba/sbin/swat swat" to /etc/inetd.conf
refresh -s inetd
Now browse to http://banora:901
Use swat to start services or:
Start smbd by entering "/usr/local/samba/sbin/smbd -D"
Start nmbd by entering "/usr/local/samba/sbin/nmbd -D"
Now try smbclient

BTW did smbd or nmbd start without error?

Prichard. your help really appreciated.
Here is what happened

(1) add "swat 901/tcp" to /etc/services Done

(2) add "swat stream tcp nowait.400 root /usr/local/samba/sbin/swat swat" to /etc/inetd.conf Done

(3) refresh -s inetd Got message was successful

(4) Now browse to http://banora:901
Using Seamonkey got " Failed to connect. The connection was refused when attempting to contact banora:901. Though the site seems valid...etc etc etc "
Was able to connect to Google, IBM so connection is good.

(5)Use swat to start services or: Did (6) and (7) next

(6)Start smbd by entering "/usr/local/samba/sbin/smbd -D"
did this and it jumped to # so presume okay ?

(7)Start nmbd by entering "/usr/local/samba/sbin/nmbd -D"
did this and it jumped to # so presume okay ?

(8)Now try smbclient
Did #find / -name smbclient and got
/usr/local/samba/bin/smbclient
so entered
#/usr/local/samba/bin/smbclient -L banora
Password: here entered root
session setup failed : NT_STATUS_LOGON_FAILURE

(9)BTW did smbd or nmbd start without error?
See (6) and (7) above. Is this what you meant ?

Regards

Prichard hunting around web saw suggestions that

(a)#shutdown -Fr should be done after /etc/services and /etc/inetd.conf changes.
Did that and
#/usr/local/samba/bin/smbclient -L banora
now gives
" error connecting to 192.168.0.144 ( A remote host refused an attempted connect operation.) Connection to banora failed "

Browsing to http://banora:901 still fails.

(b)Looking at my /etc/inetd.conf a majority of the entries have " tcp6 " instead of " tcp " in that line
"swat stream tcp nowait.400 root /usr/local/samba/sbin/swat swat" and seen varied use on web re tcp or tcp6 .

(c) Some say "swat 901/tcp" to /etc/services should be in numerical order whereas I added it to end of file.

(d) Seen suggestions these two lines should be in in /etc/inetd also

netbios-ns dgram udp wait root /usr/local/samba/sbin/smbd smbd

netbios-ssn stream tcp nowait root /usr/local/samba/sbin/smbd smbd

Have not tried (b) (c) or (d).
Awaiting your reply.
Thanks

Getting the prompt back after entering smbd and nmbd usually means they started. Enter "ps -ef|grep mbd" and you should see them running. Also have you created an smb.conf? If not, I don't think smbd will start. Of course if you want to use swat to create an smb.conf then you need to resolve your swat problems first.

Adding them to /etc/inetd.conf is just another way of starting them. In fact I like that way since inetd starts them when that service is requested by a user. Use the way that makes most sense to you.

Rebooting is ok but it just tests to see if a samba start up occurs after a reboot. Good thing to test on a production machine.

I'm confused as to the host name of your AIX box. Is it banora? Is its ip address 192.168.0.144? Determine the ip address of your AIX box with "ifconfig -a". Then use a browser other than IE to browse to that ipaddress:901.

What are the logs telling you in /usr/local/samba/var?

Prichard. Thanks for the time you are spending on this with me.
Sorry to give you so much reading. Answers to your questions are in the print outs below.

Well I found I had more than one inetd file and when I put the swat entry and the two netbios-ns and netbios-ssn lines in both #/usr/local/samba/bin/smbclient -L banora sprang to life as you can see below.
The aix5.2 machine all this is happening on is host banora 192.168.0.144.
In the smbclient printout below GIGI is my XP machine in the P2P network and Printer is a HP4500N on the P2P network connected via cat5 cable to the Switch/Hub like GIGI and banora are.

#/usr/local/samba/bin/testparm also looks good as per below.

The only thing not working is http://banora:901 which I put into seamonkey on banora and cannot get that Samba configuration page to come up.
Have a W2K machine on P2P network with Firefox and it did not work in this. GIGI/XP runs IE7 but it did not work on this either. Tried http://banora:901, http://banora and http://192.168.0.144 on both W2K and XP.

This http://banora:901 seems to be bound up with the " swat 901/tcp " entry I put in /etc/services . As you can see below there is another 3 " services " items in the computer.

(a) /usr /lpp/bos. net/inst_ root/ etc/services This looks exactly the same as /etc/services
(b) /usr /websm/codebase/com/ibm/websm/ apps/wsmperf/services Services here is a directory
(c) /etc/security/services This has a few port/tcp lines

Should the line " swat 901/tcp " go into the services file in (a) and (c) above. Did not want to fiddle with files.

Thanks

PS Note there are also two smb.conf files, both the same content as set out below.

Print outs for your perusal

# find / -name inetd.conf
/usr/lpp/bos.net/inst_ root/etc/inetd.conf
/etc/inetd.conf
# find / -name smb.conf
/usr/local/samba/lib/smb.conf
/etc/samba/smb.conf .
# find / -name smbd
/usr/local/samba/sbin/smbd
# find / -name nmbd
/usr/local/samba/sbin/nmbd
# find / -name swat
/usr/local/samba/sbin/swat
/usr/local/samba/swat
# find / -name services
/usr /lpp/bos. net/inst_ root/ etc/services
/usr /websm/codebase/com/ibm/websm/ apps/wsmperf/services
/etc/security/services
/etc/services
# find / -name smbclient
/usr/local/samba/bin/smbclient
# /usr/local/samba/bin/smbclient -L banora
Password:
Anonymous login successful
Domain=[OPEN SOURCE] OS=[Unix] Server=[Samba 3.0.4]
Sharename Type Comment
homes Disk
public Disk
IPC$ IPC IPC Service (Samba 3.0.4.0)
ADMIN$ IPC IPC Service (Samba 3.0.4.0)
pc14500dup Printer
psdup Printer
Anonymous login successful
Domain=[OPEN SOURCE] OS=[Unix] Server=[Samba 3.0.4]
Server Comment
BANORA Samba 3.0.4.0
Workgroup Master
OPEN SOURCE BANORA
WORKGROUP GIGI
# find / -name testparm
/usr/local/samba/bin/testparm
# /usr/local/samba/bin/testparm
Load smb config files from /usr/local/samba/lib/smb.conf
Processing section" [homes]"
Processing section" [printers]"
Processing section" [public]"
Loaded services file OK.
Server role: ROLE_ STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
workgroup = OPEN SOURCE
server string = Samba 3.0.4.0
smb passwd file = /var/samba/private/smbpasswd
log file = /usr/local/samba/var/log.%m
mangle case = Yes
[homes]
force user = %U
read only = No
hosts allow = 129.183.
[printers]
comment = All Printers
path = /usr/spool/samba
printable = Yes
browseable = No
[public]
path = /tmp
guest ok = Yes
# ifconfig -a
enD: flags=4e080863,80<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROU
PRT, 64BIT, PSEG,CHAIN>
inet 192.168.0.144 netmask OxffffffOO broadcast 192.168.0.255
100: flags=e08084b<UP, BROADCAST, LOOPBACK,RUNNING, SIMPLEX, MULTI CAST,GROUPRT,64
BIT>
inet 127.0.0.1 netmask OxffOOOOOO broadcast 127.255.255.255
inet6 : :1/0
tcp_ sendspace 65536 tcp recvspace 65536
# hostname
banora
#

log.banora is empty

log.192.168.0.144 is empty

log.nmbd
[2008/04/09 11:36:41, 0] nmbd/nmbd.c:main(664)
Netbios nameserver version 3.0.4 started.
Copyright Andrew Tridgell and the Samba Team 1994-2004
~fO08/O4/09 11:42:27, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(39
*****
Samba name server BANORA is now a local master browser for workgroup OPEN S
OURCE on subnet 192.168.0.144
*****
[2008/04/09 12:02:57, 0] nmbd/nmbd.c:terminate(54)
Got SIGTERM: going down...
[2008/04/10 12:50:09, 0] nmbd/nmbd.c:main(664)
Netbios nameserver version 3.0.4 started.
Copyright Andrew Tridgell and the Samba Team 1994-2004
~fO08/O4/10 12:55:58, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(39
*****
Samba name server BANORA is now a local master browser for workgroup OPEN S
OURCE on subnet 192.168.0.144
*****
[2008/04/10 12:56:00, 0] nmbd/nmbd. c: terminate (54)
Got SIGTERM: going down...
[2008/04/10 15:14:13, 0] nmbd/nmbd.c:main(664)
Netbios nameserver version 3.0.4 started.
Copyright Andrew Tridgell and the Samba Team 1994-2004
[2008/04/10 15:19:56, 0] nmbd/nmbd_become_lmb.c:become local master stage2(39
6) - - -
*****
Samba name server BANORA is now a local master browser for workgroup OPEN S
OURCE on subnet 192.168.0.144
*****
log,smbd
[2008/04/09 11:35:44, 0] smbd/server.c:main(757)
smbd version 3.0.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2008/04/10 12:39:23, 0] smbd/server.c:main(757)
smbd version 3.0.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2008/04/10 12:43:00, 0] smbd/server.c:main(757)
smbd version 3.0.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2008/04/10 12:43:02, 0] smbd/server.c:main(757)
smbd version 3.0.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2008/04/10 15:28:19, 0] smbd/server.c:main(757)
smbd version 3.0.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2008/04/10 15:28:23, 0] smbd/server.c:main(757)
smbd version 3.0.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004

swat 901/tcp goes into /etc/services

grep 901 /etc/services and make sure some other service is not using 901. Also enter "ypcat services |grep 901" if you are running NIS, making sure there is not some other service using 901.

One can administer samba without swat. It is just a convenience.

Can you ping 192.168.0.144 from Windows PC? On your Windows PC what does nslookup 192.168.0.144 return?

Looking at the logs smbd is running. Have you browsed to 192.168.0.144\public from your Windows PC?

Prichard replies to you questions.
(1)#grep 901 /etc/services
nimsh 3901/tcp
nimsh 3901/udp
swat 901/tcp

(2)#ypcat services |grep 901
ypcat 1831-142 the domainname has not been set on this machine.

(3) " One can administer samba without swat. It is just a convenience. "
Really needed for a newbie. Books advise not to try and edit smb.conf manually.

(4)Can you ping 192.168.0.144 from Windows PC?
Microsoft windows XP [version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>ping 192.168.0.144
pinging 192.168.0.144 witn 32 bytes of data:
Reply from 192.168.0.144: bytes=32 time<lms TTL=255
Reply from 192.168.0.144: bytes=32 time<lms TTL=255
Reply from 192.168.0.144: bytes=32 time<lms TTL=255
Reply from 192.168.0.144: bytes=32 time<lms TTL=255
ping statistics for 192.168.0.144:
Packets: sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = Oms, Maximum = Oms, Average = Oms

Ping from banora back to XP
# ping 192.168.0.130
PING 192.168.0.130: (192.168.0.130): 56 data bytes
64 bytes from 192.168.0.130: icmp seq=O ttl=128 time=O ms
64 bytes from 192.168.0.130: icmp-seq=l ttl=128 time=O ms
64 bytes from 192.168.0.130: icmp-seq=2 ttl=128 time=O ms
64 bytes from 192.168.0.130: icmp-seq=3 ttl=128 time=O ms
AC -
192.168.0.130 PING Statistics 4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms

(5)On your Windows PC what does nslookup 192.168.0.144 return?

C:\>nslookup 192.168.0.144
*** Can't find server name for address 203.49.70.20: Non-existent domain
server: sy-dns04.tmns.net.au
Address: 139.134.2.190
*** sy-dns04.tmns.net.au can't find 192.168.0.144: Non-existent domain

nslookup on banora back to XP
# nslookup 192.168.0.130
Server: sy-dns03.tmns.net.au
Address: 139.134.5.51
*** sy-dns03.tmns.net.au can't find 192.168.0.130:Non-existent host/domain

(6)Have you browsed to 192.168.0.144\public from your Windows PC?
Tried 192.168.0.144\public and http://192.168.0.144\public in XP/IE7 and W2K/Firefox with no luck.

(7)Looking at the logs smbd is running.
# lssrc -a
Subsystem Group PID Status
syslogd ras 10578 active
sendmail mail 10836 active
portmap portmap 8342 active
inetd tcpip 8786 active
snmpd tcpip 9034 active
hostmibd tcpip 9292 active
snmpmibd tcpip 9550 active
aixmibd tcpip 9808 active
muxatmd tcpip 14448 active
biod nfs 14706 active
rpc.statd nfs 13934 active
rpc.lockd nfs 13178 active
qdaemon spooler 12982 active
writesrv spooler 10350 active
ctrmc rsct 4948 active
IBM.ServiceRM rsct rm 14202 active
IBM.ERRM rsct-rm 5522 active
IBM.CSMAgentRM rsct=rm 13688 active
IBM.AuditRM rsct rm 16274 active
Ipd spooler inoperative
clvrnd inoperative
LUMlmd lumls inoperative
LUMgdb lumls inoperative
Truncated a couple of dozen more inoperatives off list for brevity.

Prichard I am just trying to to transfer files across my P2P network. I orignally tried sendmail with attatchments and that was a disaster. Got lost in a myriad of permission's denied using ftp and telnet. Now Samba is not as simple as the books make out.
A guy has suggested WinAxe on my XP machine.
Open to suggestions.
Pity as with your help I felt I was nearly there with Samba.

Prichard. Found some more items on further web reading. Dangerous I know, but you comments appreciated.

I do not think some files are running.

Remember I said that running the commands below the screen just jumped to # and you said this signifies they are running.
#ps -ef | grep smbd
#ps -ef | grep nmbd
#ps -ef | grep swat
In Samba in 24 Hours a reply like
root 29054 1 0 15:53 ? 00:00:00 /usr/local/samba/sbin/smbd -D
should be received to show smdb is running.

In a Redbook is said to see the server is started and listening on the SWAT port 901 run
#netstat -an | grep 901 giving a reply like
tcp4 0 0 .901 *. LISTEN
I do not get a reply it just jumps to #

Regards

I don't know Samba all too good, but doesn't the part marked bold look like the wrong network? Just guessing....

bakunin

I think bakunin found the main problem. Here is some things to think about:

Lets work on the Samba problem first and then Swat.

From your earlier posts you have put smbd and nmbd in /etc/inetd.conf. That means they will be started when needed. Also your smbclient worked, that tells me samba is most likely working fine. The log.smb also indicates samba is working.

What I'm seeing in your email is that your "browsing" understanding and syntax is not quite right.

One way to test samba is to open Windows explorer and use the syntax, now don't flip the slash directions: \\192.168.0.144

Another way to test samba is to open Internet Explorer and type file://192.168.0.144 Again, do not flip the slash directions.

What are your results?

I will be unavailable for the next week. I will check when I get back on 4/21

" One way to test samba is to open Windows explorer and use the syntax, now don't flip the slash directions: \\192.168.0.144 "

On XP, password window opens.
Put in root, and as I do not use a password clicked ok and XP altered password window to user BANORA/root.
Leaving password blank click ok and window stays there waiting for password.
Altered user to banora/root and it jumps back to BANORA/root.
Alter user to banora and it jumps back to BANORA/root

"Another way to test samba is to open Internet Explorer and type file://192.168.0.144 Again, do not flip the slash directions "

Same thing happened here as above.

W2K with Firefox did nothing ie no password Window.

I think all the above is happening because neither client, XP and W2K, has been set up as per the RedBook.

Bakunin is probably right re those 129.183 entries.
I must get into SWAT and fix up that configuration file.
The RedBooks say http://banora:901 must be working before setting up the clients.

Perhaps my router settings are fouling this up ?

Anyway I have altered that many files and settings in AIX5.2 am going to wipe it out and start again with the IBM Samba 2.2.7-4 which is a later version than the Bull one I was using.
Uninstalled Bull Samba in smit, but all the old bull ( pardon the pun ) I put in the various files was not deleted. hence the reinstall of AIX 5.2.

A new leaf, stay tuned.

Have a good trip.

Things have fared better on the new install of AIX 5200-09 on banora 192.168.0.144.
The IBM version of Samba 2.2.7-4 does not set up a smb.conf so I used the old one
with two modifications listed below in { .... } brackets.

[global]
workgroup = OPEN SOURCE
server string = Samba 3.0.4.0 { altered ver to 2.2.7-4 }
security = user
encrypt passwords = Yes
smb passwd file = /var/samba/private/smbpasswd
{ altered to: smb passwd file = /usr/bin/smbpasswd }
{ refer to #find / -name smbpasswd below }
log file = /usr/local/samba/var/log.%m
mangle case = Yes

[homes]
force user = %U
read only = No
hosts allow = 129.183.

[printers]
comment = All Printers
path = /usr/spool/samba
printable = Yes
browseable = No

[public]
path = /tmp
guest ok = Yes

The command # /usr/bin/smbclient -L banora seems to work better

added interface ip=192.168.0.144 bcast=192.168.0.255 nmask=255.255.255.0
Password:
Anonymous login successful
Domain=[OPEN SOURCE] OS=[Unix] Server=[Samba 2.2.7]
Sharename Type Comment

homes Disk
public Disk
IPC$ IPC IPC Service (Samba 2.2.7-4)
ADMIN$ Disk IPC Service (Samba 2.2.7-4)
hp4500duppcl Printer

Server Comment

Workgroup Master

The command #/usr/bin/testparm | pg seems to work well also

Load smb congig files from /etc/smb.conf
Processing section "[homes]"
Processing section "[printers]"
Precessing section "[public]"
Loaded services file OK.

Now to http://banora:901 in Seamonkey
Up pops a password box.
banora has only one user root who does not use a password
Log on to computer is always root and password left blank.
In the Seamonkey password box as a result of http://banora:901 I put in root as
user and leave the password box empty. Get 401 Bad Authorisation username or password incorrect.

I then tried this to set up user root without a password in smb.conf

# smbpasswd -a root
enter new smb password:
retype new smb password:
getsmbfilepwent: malformed password entry (no :slight_smile:
getsmbfilepwent: malformed password entry (no :slight_smile:
getsmbfilepwent: malformed password entry (no :slight_smile:
getsmbfilepwent: malformed password entry (no :slight_smile:
getsmbfilepwent: malformed password entry (no :slight_smile:
add smbfilepwd entry: unable to open file.
Failed to add entry for user root.
Failed to modify password entry for user root
#
I tried to give user root a password as admin123 but still got this error.

Reading the web I think http://banora:901 to get into SWAT needs an association
between /etc/passwd and /etc/smbpasswd.
Here is my hunt on banora

# find / -name passwd
/usr/bin/passwd
/etc/passwd
/etc/security/passwd

# find / -name smbpasswd
/opt/freeware/bin/smbpasswd
/usr/bin/smbpasswd

# ls -l /etc/passwd
-rw-r--r-- 1 root security 526 Apr 13 11:22 /etc/passwd

# ls -l /usr/bin/smbpasswd
lrwxrwxrwx 1 root system 32 Apr 12 16:22 /usr/bin/smbpasswd
-> . ./../opt/freeware/bin/smbpasswd
#

Three questions please

(1) Is the password association matter stopping the http://banora:901 password
window in Seamonkey from working, using user root without a password ?

(2) Is the password path alteration I made in smb.conf okay ?

(3) The path in smb.conf " /usr/local/samba/var/log.%m " does not exist. There is
no file called log.%m in the computer. Does this matter ?

Regards

Don't know where those smilies came from.
Lines should have read

getsmbfilepwent: malformed password entry (no :slight_smile:

Smiley gremlin

Line should have read at end

(no, then a space, then a semi colon )

Discovered by pure accident that root MUST have a password for http://banora:901 to work on opening SWAT.
Am now at the SWAT configuration screen which has a Wizard button which is not covered in my Redbook manuals.
Will hunt this down on how to fill it out.
Thanks Prichard for all your help and patience in getting me this far with Samba.

Regards