samba - Apr 2004 - Viewing Properties of file marks it Read-Only?

I've got CIFS/9000 (rebadged SAMBA 2.2.3a) running under HP-UX 11.11 using
the below configuration.

If I use Windows Explorer to right-click on any file (in the SAMBA Share)
and view its Properties, the Unix privileges get changed from
"-rwxrwxr-x"
to "-rwxr--r--" essentially making it Read-Only!!  Even if I don't
change
anything and click CANCEL on the dialogue box?

This behavior is certainly unexpected and has already burned me once, as I
unknowingly changed a file to Read-Only while users were writing to it!!  Is
there some additional setting change I can make to the config to stop this
from happening?

TIA

Alan Walters
Director of I.T.
Royce Medical


# Samba config file created using SWAT
# from AWalters (192.168.100.16)
# Date: 2004/04/23 09:53:58

# Global parameters
[global]
	workgroup = INFOSYS
	netbios name = ROYCEM2K
	server string = Samba Server
	interfaces = 192.168.101.1
	security = SHARE
	encrypt passwords = Yes
	syslog = 0
	log file = /var/opt/samba/log.%m
	max log size = 1000
	local master = No
	wins server = 192.168.100.8
	read only = No
	hosts allow = 192.168.100.0/255.255.252.0
	short preserve case = No
	dos filetime resolution = Yes

[M2KApps]
	comment = Manage-2000 Applications
	path = /roi
	valid users = awalters
	admin users = awalters
	hosts allow = 192.168.100.16

Hallo Alan Walters, 
> 
> If I use Windows Explorer to right-click on any file (in the SAMBA Share)
> and view its Properties, the Unix privileges get changed from
"-rwxrwxr-x"
> to "-rwxr--r--" essentially making it Read-Only!!  Even if I
don't change
> anything and click CANCEL on the dialogue box?
> 
> 
> [M2KApps]
> 	comment = Manage-2000 Applications
> 	path = /roi
> 	valid users = awalters
> 	admin users = awalters
> 	hosts allow = 192.168.100.16
Maybe a Problem with the umask of user root of your system ?

man smb.conf
     admin users (S)
         This  is  a list of users who will be granted
	 administrative privileges on the share.
         This means that they will do all file
	 operations as the super-user (root).

So i thing the a umask (022 or so ?) of root should be the Cause of your
Failure.

Greetings
Thomas