[SOLVED] Samba password problem with 'nobody'

[doktor5000]

Hi,

I use a Mageia computer as a samba server, with version 1 it worked beautifully, but now that I have automatically upgraded to version 2 I get a strange error.

I can still browse the network shares, I can read the current files, and create new ones and new directories from a windows computer, but I can not delete them, not even the ones I have just created, when I try to I get a error saying that I need "Backup\nobody permissions" to do it.

'Backup' being the name of the computer and every user is forced into being 'nobody'

I haven't changed anything in the config file, so I guess it must be some change in the way Samba treats permissions. Anyone knows what it could be?

Thanks.

[wintpe]

I dont know the reason for your problem, but explaining how samba links userid's may help you uncover the issue.

when a windows box connects to a samba share, it attempts to connect to it using the username on the windows host.

when samba gets that username , it attempts to map it to a unix account of the same name.

this is because a UID in windows looks more like a certificate, and a uid in unix is a number up to 65536 or maybe greater on newer linux systems.

to do that mapping it normaly needs to authenicate the user so does the user exist in the smbpasswd file

so the question is if you connect to the share and copy a file to it exactly what userid is the file created as.

if its nobody, then your userid is not being mapped.

has the smbpasswd file been wiped out.

do the users of your windows hosts have unix uid's/accounts .

regards peter

[fandom]

Whatever the problem was, changing the password backend from smbpasswd to tdbsam fixed it.

Thanks

[isadora]

Very nice fandom.
Please, be so kind to mark the topic solved.
Please edit your initial message by prefixing [SOLVED] at the beginning of the message-title.
Thanks in advance, and see ya!!!