
POSTED: Oct 5, 2005 4:30 AM (GMT)
Succesfull access by one samba client and creation of empty files on the share by the second client suggest that the problem might not be samba-related. According to my experience samba upgrades without some tweaking of the configuration sometimes leads to authorization failures on the SERVER side, but I never experiensed problems on the CLIENT side.
I’m not familiar with suse installations, but maybe you’ll take a look at the mechanism of the client access to the shared directory - smbclient, smbmount, some Gnome or KDE helper?
BR,
Petko














