Samba Unix mapping

[Kusuma Sashidhar]

Hi,

I have installed samba on hp-unix. i have a share created as below :

[VSS]
path = /global/VSS
browseable = no
create mode = 775
writeable = yes
comment = VSS
guest ok = yes

- /global/VSS has 664 kind of permission
- owner is abc and group is users
- i have user1, user2 belonging to group users
- i have created user.map containing
user1 = winuser1
user2 = winuser2

I thought this is enough for winuser1 to write to /global/VSS. What have I missed? winuser1 gets read permission but not write.

Please help.

Regards,
Kusuma

[Darren Prior]

Hi,

Have you checked with smbstatus to see if your users are authenticating, or appearing as guests? It's worth looking through the logs too.

Please remember to assign points to those that have helped - it allows others to determine useful responses.

regards,

Darren.

[Kusuma Sashidhar]

Hi Darren,

u were right. i checked smbstatus, it is authenticating as guest.

What should i do now?

will definitely submit points.

Thanks in advance,
Kusuma

[Darren Prior · Accepted solution]

Hi,

Which security method are you using? You will need to look through the log for your client PC to see what's happening when it tries to authenticate. As the user is appearing as a guest that shows that the authentication is failing.

Chapter 6 of Using Samba - the O'Reilly book can be very useful in these circumstances. This book is also available on your system if you have CIFS/9000 installed. Either use SWAT http::901 or search through the dirs for the files.

regards,

Darren.

[Mark Greene_1]

"winuser1 gets read permission but not write"

It appears your are really only authenticating as "guest", which gives you read-only, based on the 664 settings of the directory.

You can confirm this by pointing your broswer at http://:901/status and looking to see what user samba thinks it's connected with.

You may need to refine your authentication method.

mark

[Kusuma Sashidhar]

Thanks everyone. It worked.

Problem was i had said guesk = yes. so, by default all the users who have diff. unix and windows ids were connecting as guest instead of prompting for username and passwds.

Regards,
Kusuma

[Kusuma Sashidhar]

Thankyou. the problem is solved as i have mentioned in my previous thread.

Regards,
Kusuma