I have a Suse Linux server running samba (13.2) . It has worked fine for years for both Mac and Windows. No problems reading or writing the files. Now I bought a Linux notebook, also Suse Linux (13.2) . I can access the samba shares, I can copy files (from server to notebook and back) but I can’t open them. I have to copy file to disk, work on it, and then copy back to server. It can’t be a rights problem because because user (me) does not experience any of this when working from Mac or Windows, only from Linux client. Is there any adjustment I must make on Linux client to eliminate this problem?
On 2015-08-24 19:56, nananenburi wrote:
>
> I have a Suse Linux server running samba (13.2) . It has worked fine for
> years for both Mac and Windows. No problems reading or writing the
> files. Now I bought a Linux notebook, also Suse Linux (13.2) . I can
> access the samba shares, I can copy files (from server to notebook and
> back) but I can’t open them. I have to copy file to disk, work on it,
> and then copy back to server.
Open with what?
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)