I am using KDE 4.8 and I have set up access with a network 'folder' - smb:// 192.168.xx.xx/USB_Readyshare (the router naming convention) and it works fine,
with total access to ALL files, videos,photos etc,etc. with no problems. I have used exactly the same system (smb:// ip .. etc) with opensuse, Kubuntu and even
Mageia, (which uses the similar 'drakx' system to PCLinux) and I am able to access all files and open the relevant LO files with LibreOffice.
I have been able to mount the USB through the router, and (of course) when it's directly connected. I have also added the IP as a share in fstab, but these actions didn't change anything, LO would not open the LO files!
The question then becomes, 'why is there a problem with LO through PCLinux, but no difficulties using LO and the same method with other OS's'?
I do think that this is not a 'hardware' (connection) issue it seems like a "PCLinux linked with LibreOffice" software issue and I am surprised that no other similar
cases have occurred.
In KDE (specifically), using the "smb://" protocol does not "mount" the share...it uses a "kioslave" to transfer the data, and if an application (such as LO) doesn't use the kioslave to handle communication, it won't be able to access it. There are work-arounds that other distros might use, such as "gvfs" (developed from the Gnome project), that uses fusefs and creates a "hidden" mount "on-the-fly". PCLinuxOS doesn't do that "by default" (that isn't to say the software is unavailable and can't be setup...just that is isn't the "out-of-the-box" default).
A better (application agnostic) approach is to actually mount the drive into the local filesystem (using "mount.cifs" from a command line; or modifying the "fstab" file; or using "pcc" to create the config files and mount it; or using "smb4k" to browse and mount the drive). Which approach you want to use may depend on your level of comfort, so ask for opinions.
Personally, I like the command line, so I would open a "knosole" and use the following:
mount.cifs3 //path/to/network/share /path/to/local/directory
where //path/to/network/share may be an IP address or hostname followed by the share name, such as:
and /path/to/local/directory would be a directory you've previously created, such as:
or any other local directory you wish. After that, everything on that share will be available inside that directory to every application or utility you have installed...
Depending on the security settings on your share, you might need to supply username and/or password, also. That would look like this:
mount.cifs3 //path/to/network/share /path/to/local/directory -o user=username,pass=password