Can't mount NFS shares

Vahis · External Since: May 19, 2007 Posts: 79

I can't mount any NFS shares using the factory client to connect to 11.0
server.

#mount 192.168.0.99:/data1 /nfs1

Returns:
mount.nfs: access denied by server while mounting 192.168.0.99:/data1

Server log:
refused mount request from 192.168.0.99 for /data1 (/data1): illegal
port 26564

I can _browse_ the share with url in Konqueror, then the log says
accepted, any port that occurs.

But not mount it, not cli or fstab.
YaST can put the line correctly in fstab, but mount impossible.

I have asked this in the factory list, but I thought someone here might
know...

Vahis
--
"Sunrise 5:54am (EEST), sunset 8:49pm (EEST) at Espoo, Finland (14:54 hours daylight)"
http://waxborg.servepics.com
Linux 2.6.25.20-0.5-default #1 SMP 2009-08-14 01:48:11 +0200 x86_64
9:32am up 1 day 14:54, 9 users, load average: 0.47, 0.16, 0.10

Rob · External Since: Jan 08, 2009 Posts: 25

Vahis <waxborg DeleteThis @gmail.com.invalid> wrote:
> I can't mount any NFS shares using the factory client to connect to 11.0
> server.
>
> #mount 192.168.0.99:/data1 /nfs1

You need to have a name for your machines. NFS refuses to mount
systems on bare IP addresses when there is no name available for
the systems.

Either set up DNS or put the names and addresses of the client
and server systems in /etc/hosts on both systems.

Vahis · External Since: May 19, 2007 Posts: 79

On 2009-08-23, Rob <nomail.TakeThisOut@example.com> wrote:
> Vahis <waxborg.TakeThisOut@gmail.com.invalid> wrote:
>> I can't mount any NFS shares using the factory client to connect to 11.0
>> server.
>>
>> #mount 192.168.0.99:/data1 /nfs1
>
> You need to have a name for your machines. NFS refuses to mount
> systems on bare IP addresses when there is no name available for
> the systems.
>
> Either set up DNS or put the names and addresses of the client
> and server systems in /etc/hosts on both systems.

This new to me. they have worked before till 11.1.
11.2 is the first client that can't mount.

But I'll try that later today, thanks:)

Vahis
--
"Sunrise 5:54am (EEST), sunset 8:49pm (EEST) at Espoo, Finland (14:54 hours daylight)"
http://waxborg.servepics.com
Linux 2.6.25.20-0.5-default #1 SMP 2009-08-14 01:48:11 +0200 x86_64
12:48pm up 1 day 18:10, 10 users, load average: 0.05, 0.09, 0.06

bb · External Since: Jan 09, 2009 Posts: 16

On 2009-08-23 11:51, Vahis wrote:
> On 2009-08-23, Rob <nomail RemoveThis @example.com> wrote:
>> Vahis <waxborg RemoveThis @gmail.com.invalid> wrote:
>>> I can't mount any NFS shares using the factory client to connect to 11.0
>>> server.
>>>
>>> #mount 192.168.0.99:/data1 /nfs1
>> You need to have a name for your machines. NFS refuses to mount
>> systems on bare IP addresses when there is no name available for
>> the systems.
>>
>> Either set up DNS or put the names and addresses of the client
>> and server systems in /etc/hosts on both systems.
>
> This new to me. they have worked before till 11.1.
> 11.2 is the first client that can't mount.
>
> But I'll try that later today, thanks:)
>
> Vahis

That is new for me too.

bblin4:/ # showmount -e cups
Export list for cups:
/backup 192.168.0.0/24
bblin4:/ # rcautofs status
Checking for service automount unused
bblin4:/ # cat /etc/auto.master
#
# Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#
#/misc /etc/auto.misc
#/net -hosts
#
# Include central master map if it can be found using
# nsswitch sources.
#
# Note that if there are entries for /net or /misc (as
# above) in the included master map any keys that are the
# same will not be seen as the first read key seen takes
# precedence.
#
/net -hosts
+auto.master
bblin4:/ # rcautofs start
Starting automount done
bblin4:/ # getent hosts cups
192.168.0.17 cups
bblin4:/ # cd /net/192.168.0.17
bblin4:/net/192.168.0.17 # ls
backup

/bb

Vlad_Inhaler · External Since: Apr 24, 2007 Posts: 31

On Aug 23, 8:41 am, Vahis <waxb... RemoveThis @gmail.com.invalid> wrote:
> I can't mount any NFS shares using the factory client to connect to 11.0
> server.
>
> #mount 192.168.0.99:/data1 /nfs1
>
> Returns:
> mount.nfs: access denied by server while mounting 192.168.0.99:/data1
>
> Server log:
> refused mount request from 192.168.0.99 for /data1 (/data1): illegal
> port 26564
>
> I can _browse_ the share with url in Konqueror, then the log says
> accepted, any port that occurs.
>
> But not mount it, not cli or fstab.
> YaST can put the line correctly in fstab, but mount impossible.
>
> I have asked this in the factory list, but I thought someone here might
> know...
>
> Vahis
> --
> "Sunrise 5:54am (EEST), sunset 8:49pm (EEST) at Espoo, Finland (14:54 hours daylight)"http://waxborg.servepics.com
> Linux 2.6.25.20-0.5-default #1 SMP 2009-08-14 01:48:11 +0200 x86_64
> 9:32am up 1 day 14:54, 9 users, load average: 0.47, 0.16, 0.10

Things to look at:
- did you activate both the client and server sides with Yast? I seem
to remember that a couple of processes need to be running and if you
did the /etc/fstab entry by hand you might have missed them. Yast
does the necessary. You might even have missed installing a package.
- I have had problems with nfsv4 where nfsv3 works fine (something
stupid I will have done but I have never felt the need to chase it up)
- what does the entry look like in /etc/exports?
- do your uids (and gids) match across the two machines?
- can any other machine in your network browse that particular share?
- Is a firewall blocking something (unlikely)

I have never used automount, I tend to keep things very simple.