vockleya
I’ve had some similar issues making samba writeable from various windows clients. We are running a variety on our network XP, Win7, win2k3 server however we were not concerned with security as it we are on a closed network so we made the share wide open. You could work with making it open and write to it (you may already be there) then lock it down afterwards.
I suspect that not all the contents of the file below are required however this is what works for us and we moved on to the next issue:
Quote:
[ global]
workgroup = WORKGROUP
netbios name = server
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\L\profiles\.msprofile
logon home = \\L\U\.9xprofile
logon drive = P:
usershare allow guests = Yes
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s/bin/false %m$
domain logons = No
domain master = No
client signing = yes
server signing = yes
[file-share-1]
comment = software
inherit ads = Yes
path = /Shared-1
local writable = yes
guest ok = yes
|
With the file above we are able to access the share from the following:
- Standalone Xp workstations
- XP workstations on our win2K3 forest
- XP workstations on our win2K7 forest
Win2k3 Servers on our 2K3 forest
If we want to access the share from standalone windows 7 workstations we needed to either add the line under global settings “security = share” which broke the workstations above or change the local security policy under the local security policy
- "Microsoft Network Client - Digitally sign communications if server agrees set to - disabled"
