Normally I would guess that the issue would be to do with permissions.
Check what the default directory/file permissions are for Samba and if necessary define them explicitly in the relevant [share].
Also check what the linux permissions are on the relevant directories.
If both of these look ok, then your problem probably is a linux client issue (if all the other Windows clients' behaviour is ok).
Have you checked the Samba logs? Have you tried increasing the logging detail?
Could be smb4k - I've never used it. Have you tried mounting the remote Samba share manually:
/bin/mount -t smbfs -o username=<Samba user>,password=<password> //server/Share /local_dir
If you do that and then try editing a file in /local_dir does it have the same behaviour?
It could also be to do with mapping UNIX stuff to Windows - if you run
on the server it should list all your settings including the defaults so you can
have a trawl through the Samba docs to see what's necessary.
It looks as though you are running Samba servers on both machines - have you tried turning the server off on the client
temporarily to see if that affects anything?
I am using smb4k as a Samba front end to avoid frustration with Konqueror bugs
I've had issues with Konqueror and the Network Browsing icon in SuSE since 9.1. However, it only affects browsing
and although that can be a pain you can still get to where you want to with an explicit Location entry like:
which on my system prompts for a Samba username and password.
The other thing I would auggest is looking on the samba.org site - there are very good How-to's and example
documents that cover pretty much all the issues.