On Tue 05 Dec, gary.stainburn@ringways.co.uk wrote:
It's not a case of thinking 'down' to your level, it's merely a case of perspective.
For this example, I would leave out both entries. From the smb.conf that you included I cannot see why you would get a username/password dialog unless smbd didn't know what user to log you in as.
Well - neither could I - although I wasn't as surprised as you!
Try adding 'guest account = nobody' in the [global] section and 'user = nobody' in the [test] section. Then see what happens.
'user=nobody'? I assumed that this meant that there was nobody who was a guest - and therefore no one could log on as guest. This would appear to be incorrect? ..however, user=nobody does appear to allow everyone to connect to that share, as well as to their home directory - assuming they use their LINUX username and password - and have encrypted entries in the smbpasswd file. I notice that there is a command 'update encrypted' for use in global section of smb.conf which will update their encrypted password after they have connected once to a share (impossible if they require encrypted passwords to do that in the first place). Is there a way to duplicate the entire passwd file into smbpasswd file and do the encryption for everyone in one go? ..still I getting there. Many thinks again. -- Alan Davies Head of Computing Birkenhead School