Hello all,

I have a server which I had samba working on Suse 10.1 . I upgraded it to 10.2 and things got changed and moved and so it didn't really matter that samba wasn't working.
However, now I upgrade to 10.3 and I've installed some new hard drives in it. I really need samba to work on it. I have the basics up and running I can see the box from my windows box but I can't write to it. Others who don't have my username can't read the folders, even when I log in with my username and password?!?!?

How can I tell samba that my username on the windows box is the same as the NIS username. Any ideas would be great.

Currenly I think samba is seeing my windows box as everyone else, cus when I change flags from 775 to 770 I can't read the folder anymore.

Cheers,

I have gone round and round this track quite a few times, and eventually stub my toe on the inconvenient fact that Samba does not use the Linux password file (or shadow passwords) to validate logons. Instead, it uses a parallel data set in /etc/samba/smbpasswd. To further confuse things, it uses a file named /etc/samba/smbusers to map various SMB logon names onto Linux logon names before consulting its private password file. All this is done for some obscure but probably defensible reasons having to do with system-wide security, but it sure does make it hard to debug things in any straightforward way.

There is a pretty good tutorial on how to debug a new installation from both sides here: http://us3.samba.org/samba/docs/man/...n/install.html
starting with "List Shares".

Thank you.

I'm looking through it now