mmmmm, thanks!!! feel kinda silly now.

using fstab is what i normally use in slackware, but i guess that after 2 days after installing suse makes one lazy and easily start trusting all the automagick buttons.

simply mounting the drive works like a charm!!!!!!!

any idea how to place a mounted folder in "remote:/" , no clue where to find "the remote" location, and this would make it easy for the user i'm setting this up for.

much obliged!!!!!

dear all,

glad to say i can answer my own question here.
what i did is the following.
i made a mountpoint in fstab that will mount a share on the server on "/mnt/shareonserver" on boot for the user

then i made a connection to "shareonserver" with Knetattach and marked "create an icon for this remote folder"

i will not use this connection however, only the icon!! since when accessing the share through here leaves me with openoffice not being able to open files on the server.

since the location this link points to can not be altered directly i went to
/home/user/.kde/share/apps/remoteview
where there's a nice little icon called "shareonserver.desktop"
a simple right click on this icon and change the URL to "/mnt/shareonserver/"

and voila! problem solved!!

I know mounting the drive is a quick good fix, BUT I understand it shouldn't be like that forever, and I belive there are bug reports on openoffice.org to fix it in the next release or whenever.

i wonder,

since i only encountered this problem so far with the 2 only not-native-kde-apps OpenOffice and The Gimp in the SuSe desktop, if its not a Kde problem, or maybe a combination of both.

after browsing around for this problem i think (correct me if i'm wrong)
it might be an issue of office not supporting the KIOslaves, or the other way around ofcourse depending on your vieuw.

don't know if there's a way around this using a different protocol, meaning it would be a SuSe issue.

i'm not that experienced with either SuSe or Kde, and was luckily enough able to figure (more or less by accident) out the quick and dirty solution mentioned in the post above when installing a desktop for a user (my boss)who's completely computer illiterate. and therefore would like to know if there's someone able to find an easier and more elegant fix to this problem.

I had this problem as well. I solved it by installing nfs-common package. But I am using Debian Etch, I am not sure if it is the same in Suse.

More information in this thread The separate packages are mentioned here.

(I am a bit puzzeled though, shouldn't nfs-common be installed whenever nfs-client is being installed?)

jlinkels

BerlinBadger, you are so the man! Worked like a charm, thanks!!

Great fix. I had the same problem, but was from a Netware 6.x system to openSuse workstations.

thanks