Bug 154796 - kio_nfs cannot browse/display nfs shares on the LAN
Summary: kio_nfs cannot browse/display nfs shares on the LAN
Status: RESOLVED DUPLICATE of bug 75757
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: nfs (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-29 06:57 UTC by Adrian Jadic
Modified: 2012-07-19 18:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
eeePC screenshot of konqueror (48.01 KB, image/png)
2007-12-29 07:07 UTC, Adrian Jadic
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Jadic 2007-12-29 06:57:03 UTC
Version:            (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
OS:                Linux

I am not sure if this is a bug or a work-in-progress but it certainly makes no sense to me even after spending all day scrambling through forums and bug reports...
I use Kubuntu 7.10 on my fileserver as well as my clients around the house (laptops)

When calling the nfs: kioslave in Konqueror (on a client PC) my logic would expect to see a tree of available shares listed by IP address or Host names same like one does when using smb:/ .

Instead I get: "no hostname specified". Yes, I do have NFS shares configured on my server (etc/exports)
Furthermore, when I specify the host by IP addres like: nfs://IPaddress I get some other error about authentication.

Only when I configure my shares with option "insecure" I am able to browse them with the kio_nfs.

I have purchased recently the hot, new eeePC which has KDE under a (mini) Xandros distro. It also uses Konqueror as a file manager and as seen in the attached screenshot it can browse NFS shares as well as samba shares "out-of-the-box" even WITHOUT enabling the "insecure" option on the server side.

My friend uses OpenSUSE and his Konqueror behaves the same like my Kubuntu one therefore I don't think that it's just me...

Attachment link:
http://metricus.dyndns.org:8080
Comment 1 Adrian Jadic 2007-12-29 07:07:42 UTC
Created attachment 22746 [details]
eeePC screenshot of konqueror
Comment 2 Bruno Friedmann 2010-07-26 18:48:23 UTC
Sorry to wake this old monster :
kde4.4.4 actually doesn't allow to browse nfs server
with dolphin or konqueror using the nfs:/ protocol

I see those error on the server
mountd[5188]: refused mount request from 192.168.50.100 for /tmp (/tmp): illegal port 56116

opensuse 11.3 / kde 4.4.4 / nfs serveur in v3 & v4 : only tcp

everything works nicely when mounting the share by traditionnal way
Comment 3 Martin Koller 2011-07-25 11:41:14 UTC
can confirm with KDE 4.6.5, openSuse 11.3
Comment 4 Bruno Friedmann 2011-07-25 11:53:45 UTC
Wouah, I've pretty much forget that one :D

Ok confirmed as not working with 4.7-rc2 
konqueror/dolphin said there's an error.

In the nfs server log I found that
Jul 25 13:47:52 yoda rpc.mountd[4910]: refused mount request from 192.168.103.131 for /media/backup1t/mirror (/media/backup1t/mirror): illegal port 45431
Jul 25 13:47:52 yoda rpc.mountd[4910]: refused mount request from 192.168.103.131 for /media/sysrescuecd (/media/sysrescuecd): illegal port 45431

There's another unvisible error here, the request mount should have been made by ipv6 protocol and not ipv4 

when I used the mount described in /etc/fstab
yoda:/srv/mirror     /ioda/mirror    nfs             noauto,defaults,soft,rw,posix,noatime,nodiratime,mountproto=tcp6 0 0

everything works ... 

The nfs server didn't used nfsv4 nor gssapi not kerberos, it's a simple nfsv3
Comment 5 Martin Koller 2012-07-18 05:23:06 UTC
This is the same problem as in bug 75757
I assume the problem simply is that kio_nfs runs under a non-root user therefore the originating port is > 1024 (or something like that).
Workaround from other bugreport: Add the option "insecure" to your /etc/exports

*** This bug has been marked as a duplicate of bug 75757 ***
Comment 6 Bruno Friedmann 2012-07-19 18:42:31 UTC
Adding insecure in /etc/exports need a root access on the nfs server.
How can a simple client claim this as requirement ? 

If this is a absolute requirement for kio_nfs, then the message should be clearly indicated in the error box.