When i run a Windows executable from a windows machine that is located on a Mapped Drive on my Linux box (SuSE 11) i get a temp file created thats impossible to delete from a Windows machine! It can only be deleted from the Linux box logged in as root.
Why is this and how can i resolve this issue, why is the temp file created and why is it not automatically deleted when the Win executable finnishes its job?
I don’t want hundreds of temp files to periodically delete!
Can you please post the contents of your samba config file, smb.conf, and also the ownership and permissions on the Suse directory that is shared from Linux (e.g. do ls -l /path etc)
[global]
workgroup = MSHOME
name resolve order = bcast host lmhosts wins
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
logon path = \%L\profiles.msprofile
logon home = \%L%U.9xprofile
logon drive = P:
usershare allow guests = No
domain logons = Yes
domain master = Yes
security = user
winbind gid = 10000-20000
winbind uid = 10000-20000
netbios name = DevilsBackBone
passdb backend = smbpasswd:/etc/samba/smbpasswd
include = /etc/samba/dhcp.conf
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
local master = Yes
os level = 65
preferred master = Yes
[network]
comment = NetworkShare
inherit acls = Yes
path = /network/
read only = No
guest ok = yes
[netlogon]
comment = Network Logon Service
path = /network/
write list = root
guest ok = no
read only = yes
Owner and Permissions:
drwxrwxrwx 3 root root 4096 date time network
from the Linux command prompt Temp files created are named as follows filename.exe:Zone.Identifier:$DATA with the ownership nobody nobody with permissions -rwxr–r–
Viewing the contents of the mapped drive from a windows machine using Windows Explorer the temp file names are very different, the one above is named AUZ538~V and is unreadable and connot be found or deleted!
All other files have the same ownership and permissions all are read writable by anybody, anybody can add / delete and read write to the mapped drive
Suggest you backup smb.conf first so you can retrieve the situation if it blows up. Then try this:
[network]
comment = NetworkShare #inherit acls = Yes
force user = root
path = /network/
read only = No
guest ok = yes
Forcing root is a diagnostic thing (temporary). If it improves, we would change that, but use it to see if it does improve. And clean our the temp files and see if they then correct themselves.
and this, assuming that you don’t want Suse to be a domain controller (don’t change it if I assume wrongly):
[global]
workgroup = MSHOME
name resolve order = bcast host lmhosts wins
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
usershare allow guests = No
security = user
netbios name = DevilsBackBone
passdb backend = smbpasswd:/etc/samba/smbpasswd
local master = Yes
os level = 65
preferred master = Yes
Good practice suggests to take the ownership of the directory away from root. Suppose you have a user called “foogirl”. Make the directory /network and all it’s files to be owner=foogirl, group=users. Directory permissions world writable.
Leave the inherit acls commented out or remove it
Change force user = root to force user = foogirl
Add foogirl to the Samba user database with this command:
smbpasswd -a foogirl
Reboot and try again.
If problems persist then please explain what this means:
I did manage to get a prompt for UserName and PassWord and gave up because i could get it to work for either WinVista or WinXP but not both
Plus: which way did you structure [global] in smb.conf?
Plus: which version of Suse are you using
Plus: what is the output from the console command rpm -qa samba where * means wild card
I’d like a little help here please. If this is your first visit, you might want to take the time to read through this page inspired to look this up thank you…
I’d like a little help here please. If this is your first visit, you might want to take the time to read through this page inspired to look this up thank you…
:):)
