• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Need some Samba help

screw3d

Diamond Member
I can map my home dir on a FreeBSD machine to a Windows drive. I can see files, move them around or create new files, save them etc. on Explorer.

I just can't copy a file from Windows to the box via the mapped drive. It will just create a 0 byte file, asks me to confirm overwriting the 0 byte file, and throws an error message saying that "Access is denied".

I can, however, create a new empty file on the BSD box, open that file in Windows, paste text in it and save it.

Help?
 
try chmod 777 dirname on BSD...

if that works, then it was permissions related. Make sure the samba user has the right permissions in smb.conf AND in the file system.
 
No, it's definitely not file system permissions related

I have a 'writable = true' (or something like that) in my smb.conf.. is that what you're talking about?
 
Originally posted by: screw3d
No, it's definitely not file system permissions related

I have a 'writable = true' (or something like that) in my smb.conf.. is that what you're talking about?

No. If the user that smbd runs under does not have write permissions to the directory it is trying to write to, the write will fail. His test would eliminate this as an issue. My method would be looking at the logs instead. His is probably more newbie friendly. 😉

I think that was nweaver's point anyhow. 🙂
 
Originally posted by: n0cmonkey
Originally posted by: screw3d
No, it's definitely not file system permissions related

I have a 'writable = true' (or something like that) in my smb.conf.. is that what you're talking about?

No. If the user that smbd runs under does not have write permissions to the directory it is trying to write to, the write will fail. His test would eliminate this as an issue. My method would be looking at the logs instead. His is probably more newbie friendly. 😉

I think that was nweaver's point anyhow. 🙂

chmod -R 777 / is the answer to it all.......

yeah, I usually just hit logs...sometimes I'll bump the log level. tail -f is one of the greatest tools for troubleshooting 😀
 
I just realized that it's actually working, but only fails on TortoiseCVS-enabled files. Anyone seen this before?
 
Back
Top