Hello

I can't get smbd to run, the log files show:
[2003/08/18 13:49:51, 0] lib/util_sock.cpen_socket_in(804)
bind failed on port 139 socket_addr = 0.0.0.0.
Error = Address already in use

Where do I start looking and is the 0.0.0.0 ip relevant to the problem and where is the config for the daemon as this bdoes not appear to be a smb.conf issue.

Kind regards Richard

It looks like samba is already running. Try 'smbcontrol ping 1' or '/etc/rc.d/init.d/smb status'. The 0.0.0.0 IP is correct, and corresponds to all interfaces. See the output of 'netstat -pan' for more insight. You can also use 'testparm' to verify your smb.conf settings. Try using '/etc/rc.d/init.d/smb restart' also.

Good luck

Thanks for that
smbcontol ping 1 returns: couldnt resolve message type 1.
smbcontol ping works in that it provides a usage message but the syntaxes it suggests also return usage messages.
status returns: dead.
Testparm is ok.
rcsmb stop returns a message that includes a warning that the daemon is not running
rcsmb start or rcsmb restart returns:
starting samba classic SMB daemon

Regards Richard

woops the last line rcsmb start or restart also includes the failed advice

Okay, do '/etc/rc.d/init.d/smb stop'. Then do a 'netstat -pan | grep 139'. The last item in the listing should be the PID of the process that is holding port 139 open. You should be able to use 'kill -9 PIDNUMBERHERE' to stop the process. You could also use 'lsof -i' to see what processes are holding what ports open on your machine.

Doh!
VMware had it. It never occured to me.

Could you answer one last thing for me. I'm setting up a linux server at work but wish the machines to use a fat drive which is mounted into the /home directory with smb.conf share:
[fatdrive]
comment = mainbin
path = /home/fatdisk
browseable = yes
writeable = yes
guest ok = yes
public = yes

As I wish to map the network drive on the users pc's I thought that the above would just give carte blanche access but though I can access as a user with my login I do not neccessarily want to set up user accounts (at this stage) for those accessing.
The scenario is a number of users linking to a database and pim backend. Why does the fact that it is browseable writeable and guest ok not just allow free access.
I know the security issues but that is something I will address later as I gradually migrate other systems.

Thanks for your time.
Richard

You are dealing with several layers of permissions here. guest ok allows guests to get to the machine, but doesn't nessasarily grant them read or write access to the folder. You need to be aware that somehow your smbusers map to unix users and those unix users need to have specific permissions to the file system before you can get access using Samba.

An excellent book is McGrawHill's "Samba Unix & NT Internetworking" and will clearly explain how samba wonderfully handles all the millions of conversions between the unix and NT worlds...

Thanks for your help. just to let you know I did get sorted I made security = share (rather users which I have always set up to) and the network drive maps seamlessly on the pc's without requiring logins etc.
Richard