[NTLUG:Discuss] (no subject)

[Michael Patrick]

On Wed, Jul 24, 2002 at 10:22:47PM -0500, Wayne Dahl wrote:
> Hi all,
> 
> Now, I have made sure the inetd.conf file has netbios set up for port 139 
> for tcp and port 137 for udp.  I have also set up the workgroup in the 
> smb.conf file and set up the allowed hosts from the dhcp list on my 
> router.  What am I doing wrong?  I know I have to be missing something, but 
> it eludes me.
> 

I was having this issue at home... here is my config now and it works.  What seems to have done the trick was the adding of a guest account with a blank password.

With the below config I can browse to the BTVS workgroup and then into the WILLOW server and see the RAID share.  Note that I cannot access the RAID share because the guest account doesn't have rights there (guest ok = no is default).

Note that if I remove the "guest account = guest" option then I cannot browse to the server or even the workgroup.

# Samba config file created using SWAT
# from 192.168.0.100 (192.168.0.100)
# Date: 2002/07/25 04:24:50

# Global parameters
[global]
	workgroup = BTVS
	netbios name = WILLOW
	server string = Willow
	encrypt passwords = Yes
	map to guest = Bad User
	username map = /data/SMB/etc/smb.map
	lanman auth = No
	log level = 2
	log file = /data/SMB/var/log.%m
	os level = 255
	preferred master = True
	domain master = True
	guest account = guest

[RAID]
	comment = The storage area
	path = /data/SMB/storage
	read only = No

************************************************************
*  DISCLAIMER: A guest account with a blank password could *
*  be troublesome to the worrying type.  Setting the       *
*  shell to /sbin/nologin (or OS equiv) would probably be  *
*  good                                                    *
************************************************************

> Also, I'd like to have the Samba server start on startup.  What would I add 
> to make it do so?  Would that be an entry in the initrd.conf file?
>

you would  put the samba startup file (samba.sh.sample) in /etc/init.d and then link it into the right run levels (/sbin/setup is the easy way if running RH).

Michael