Ubuntu

RPC: Authentication error

Asked by ealthuis

A whole new problem has cropped up, apart from the NFS problem on this computer:

ea@discovery:~$ rpcinfo 192.168.0.12
rpcinfo: can't contact rpcbind: : RPC: Authentication error; why = Client credential too weak
ea@discovery:~$

A similar problem occurred on a nfs client when mounting a partition:

mount.nfs: portmap query failed RPC: Authentication error

Password has not been changed for a while, so what else is needed?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said : 		#1

What are the contents of /etc/hosts.allow and /etc/hosts.deny

Revision history for this message
ealthuis (ealthuis) said : 		#2

ea@discovery:~$ cat /etc/hosts.allow
# /etc/hosts.allow: list of hosts that are allowed to access the system.
# See the manual pages hosts_access(5) and hosts_options(5).
#
# Example: ALL: LOCAL @some_netgroup
# ALL: .foobar.edu EXCEPT terminalserver.foobar.edu
#
# If you're going to protect the portmapper use the name "rpcbind" for the
# daemon name. See rpcbind(8) and rpc.mountd(8) for further information.
# next line added for NFS usage
rcpbind mountd nfsd statd lockd rquotad : 192.168.0.11 192.168.0.12 192.168.0.13 192.168.0.10

ea@discovery:~$ cat /etc/hosts.deny
# /etc/hosts.deny: list of hosts that are _not_ allowed to access the system.
# See the manual pages hosts_access(5) and hosts_options(5).
#
# Example: ALL: some.host.name, .some.domain
# ALL EXCEPT in.fingerd: other.host.name, .other.domain
#
# If you're going to protect the portmapper use the name "rpcbind" for the
# daemon name. See rpcbind(8) and rpc.mountd(8) for further information.
#
# The PARANOID wildcard matches any host whose name does not match its
# address.
#
# You may wish to enable this to ensure any programs that don't
# validate looked up hostnames still leave understandable logs. In past
# versions of Debian this has been the default.
ALL:ALL

ea@discovery:~$

Revision history for this message
Manfred Hampl (m-hampl) said : 		#3

see https://help.ubuntu.com/community/SettingUpNFSHowTo#Portmap_Lockdown
Ensure that the list of authorized IP addresses includes the localhost address (127.0.0.1)

Revision history for this message
ealthuis (ealthuis) said : 		#4

I added 127.0.0.1 to the list , no improvement.

Now another point I have a suspicion that the motherboard has a problem, a while ago while starting, a message flashed by about a problem, it has never repeated itself. Also the screen has a yellowish background. I have had motherboard problems before, so I am working that angle.

I sent a question to the manufactures to determine what if anything is wrong

So I will suspend the work on these questions 677806 and 677874 until I have an answer from Gigabyte.
If I have to get the motherboard repaired or replaced I will let you know, then I can restart the NFS and see what happens.

I have not lost any of my files and I can do updates as needed just not as conveniently.
Thank you once again for your help.

Emanuel

Revision history for this message
Launchpad Janitor (janitor) said : 		#5

This question was expired because it remained in the 'Open' state without activity for the last 15 days.