Hi there, I spent much of yesterday puzzled by a samba setup that just won't do what I expect. This is a new installation of Hardy using the alternate installation to set up raid1, though the Home partition is that from a prior SuSE 10.1 installation. This is not the same as the thread I started earlier in the week however some of the symptoms are similar, and I now realise that issues I have with my home Hardy installation is also similar. My googling shows plenty of people saying they're having problems, lots of responses of "I don't have any problem with mine" or any suggestions to solve are covered by what I have done already, as follows:

1.  Create a few users, add them to a group or 2.
2.  sudo smbpasswd -a <user>
3. Via konqueror right clicking a folder to share > Properties > Share, and follow your nose from there. This is far from being rocket science. (I've also used webmin to try to configure the share but without success at home) 4. Use of chown and chmod (sometimes with -R) to apply various permissions to sub-folders.


Connecting from a couple of XP machines it now gets interesting. From one, there is a refusal to authenticate any user created above when trying to access the share - I get "incorrect password or unknown username for \\machine\share". The only XP user that can connect is my own user - the same username as the first kubuntu user created who gets to use their password for sudo.

From another, I can connect to the share despite that user NOT existing on the linux box! Further, I could browse to sub-folders, open files, where permissions are such that the connecting user is neither the linux/samba user or in the group that owns the folder and permissions are 0700. I'd be very interested in any opinions on what might be causing me to go insane and consider a career change. Is there anything in that old Home folder that might create problems - I would have thought that all the action is in "/" and that, as I mentioned, is fresh.

Thanks for any pointers, to which I will try to follow up on today but it may end up having to be next week.
Roger

Reply via email to