Strange nfs problem - Connection refused

Strange nfs problem - Connection refused

Post by D.K. » Mon, 04 Aug 2008 22:01:33



Hi all,
i hope someone can help me.
i cant mount an NFS share from remote.
i have to mount the nfs share vom the local server and from one remote
server.
mount to 127.0.0.1 will work, but not from the same device while using the
eth0 ip-address.
its an preinstalled appliance image so i dont take the most settings.


mount: mount to NFS server '192.168.22.94' failed: System Error: Connection
refused.



 
 
 

Strange nfs problem - Connection refused

Post by Unru » Tue, 05 Aug 2008 01:19:15



>Hi all,
>i hope someone can help me.
>i cant mount an NFS share from remote.
>i have to mount the nfs share vom the local server and from one remote
>server.
>mount to 127.0.0.1 will work, but not from the same device while using the
>eth0 ip-address.
>its an preinstalled appliance image so i dont take the most settings.

>mount: mount to NFS server '192.168.22.94' failed: System Error: Connection
>refused.

Well, make sure that portman and mountd have permissions in
/etc/hosts.allow, and that the file system is actually exported
(/etc/exports and exportfs) to 192.168.22.94

 
 
 

Strange nfs problem - Connection refused

Post by D.K. » Tue, 05 Aug 2008 02:26:57


i think i have done this all...

Expoprts:

/nfsdir *(rw,sync,no_root_squash) 192.168.22.0/24(rw,sync,no_root_squash)

Hosts.allow:

#
ALL: ALL
portmap: 192.168.22.0/255.255.255.0
lockd: 192.168.22.0/255.255.255.0
rquotad: 192.168.22.0/255.255.255.0
mountd: 192.168.22.0/255.255.255.0
statd: 192.168.22.0/255.255.255.0
ANY: ANY

Iptables are stopped


/nfsdir
192.168.22.0/24(rw,wdelay,no_root_squash,no_subtree_check,anonuid=65534,anongid=65534)
/nfsdir
<world>(rw,wdelay,no_root_squash,no_subtree_check,anonuid=65534,anongid=65534)

Ideas??
DK




>>Hi all,
>>i hope someone can help me.
>>i cant mount an NFS share from remote.
>>i have to mount the nfs share vom the local server and from one remote
>>server.
>>mount to 127.0.0.1 will work, but not from the same device while using the
>>eth0 ip-address.
>>its an preinstalled appliance image so i dont take the most settings.


>>mount: mount to NFS server '192.168.22.94' failed: System Error:
>>Connection
>>refused.

> Well, make sure that portman and mountd have permissions in
> /etc/hosts.allow, and that the file system is actually exported
> (/etc/exports and exportfs) to 192.168.22.94




 
 
 

Strange nfs problem - Connection refused

Post by Unru » Tue, 05 Aug 2008 03:10:37



>i think i have done this all...
>Expoprts:

>/nfsdir *(rw,sync,no_root_squash) 192.168.22.0/24(rw,sync,no_root_squash)
>Hosts.allow:

>#
>ALL: ALL
>portmap: 192.168.22.0/255.255.255.0
>lockd: 192.168.22.0/255.255.255.0
>rquotad: 192.168.22.0/255.255.255.0
>mountd: 192.168.22.0/255.255.255.0
>statd: 192.168.22.0/255.255.255.0
>ANY: ANY
>Iptables are stopped

>/nfsdir
>192.168.22.0/24(rw,wdelay,no_root_squash,no_subtree_check,anonuid=65534,anongid=65534)
>/nfsdir
><world>(rw,wdelay,no_root_squash,no_subtree_check,anonuid=65534,anongid=65534)
>Ideas??

Nope, except try lookin in the various /var/log files for some clue.

Ie try mounting and doing tail on various of the files to see if there is
anything there.

- Show quoted text -

>DK



>>>Hi all,
>>>i hope someone can help me.
>>>i cant mount an NFS share from remote.
>>>i have to mount the nfs share vom the local server and from one remote
>>>server.
>>>mount to 127.0.0.1 will work, but not from the same device while using the
>>>eth0 ip-address.
>>>its an preinstalled appliance image so i dont take the most settings.


>>>mount: mount to NFS server '192.168.22.94' failed: System Error:
>>>Connection
>>>refused.

>> Well, make sure that portman and mountd have permissions in
>> /etc/hosts.allow, and that the file system is actually exported
>> (/etc/exports and exportfs) to 192.168.22.94




 
 
 

Strange nfs problem - Connection refused

Post by D.K. [CCA » Tue, 05 Aug 2008 03:53:06


is this ok?
message from /var/log/messages
Aug  3 20:45:58 sysxen01 portmap[4519]: Only binding to LOOPBACK address!
DK




>>i think i have done this all...

>>Expoprts:

>>/nfsdir *(rw,sync,no_root_squash) 192.168.22.0/24(rw,sync,no_root_squash)

>>Hosts.allow:

>>#
>>ALL: ALL
>>portmap: 192.168.22.0/255.255.255.0
>>lockd: 192.168.22.0/255.255.255.0
>>rquotad: 192.168.22.0/255.255.255.0
>>mountd: 192.168.22.0/255.255.255.0
>>statd: 192.168.22.0/255.255.255.0
>>ANY: ANY

>>Iptables are stopped


>>/nfsdir
>>192.168.22.0/24(rw,wdelay,no_root_squash,no_subtree_check,anonuid=65534,anongid=65534)
>>/nfsdir
>><world>(rw,wdelay,no_root_squash,no_subtree_check,anonuid=65534,anongid=65534)

>>Ideas??

> Nope, except try lookin in the various /var/log files for some clue.

> Ie try mounting and doing tail on various of the files to see if there is
> anything there.

>>DK




>>>>Hi all,
>>>>i hope someone can help me.
>>>>i cant mount an NFS share from remote.
>>>>i have to mount the nfs share vom the local server and from one remote
>>>>server.
>>>>mount to 127.0.0.1 will work, but not from the same device while using
>>>>the
>>>>eth0 ip-address.
>>>>its an preinstalled appliance image so i dont take the most settings.


>>>>mount: mount to NFS server '192.168.22.94' failed: System Error:
>>>>Connection
>>>>refused.

>>> Well, make sure that portman and mountd have permissions in
>>> /etc/hosts.allow, and that the file system is actually exported
>>> (/etc/exports and exportfs) to 192.168.22.94




 
 
 

Strange nfs problem - Connection refused

Post by Bill Marcu » Tue, 05 Aug 2008 05:19:12



Quote:> is this ok?
> message from /var/log/messages
> Aug  3 20:45:58 sysxen01 portmap[4519]: Only binding to LOOPBACK address!
> DK

Is that on the server or the client?  If it's the server, it could be
the reason your client can't connect.  Look in /etc/default/portmap.
 
 
 

Strange nfs problem - Connection refused

Post by D.K. [CCA » Tue, 05 Aug 2008 17:12:40


great ...
thanks - this suggestion helps me
at the /etc/sysconfig/network are the pmap= -l parameter are set.
after deleting this parameter all works fine.
D.K.




>> is this ok?
>> message from /var/log/messages
>> Aug  3 20:45:58 sysxen01 portmap[4519]: Only binding to LOOPBACK address!
>> DK

> Is that on the server or the client?  If it's the server, it could be
> the reason your client can't connect.  Look in /etc/default/portmap.

 
 
 

1. Problem NFS client: (NFS)lockdsvc: Connection refused

Hi all,

I am stuck with a weird problem and I am hoping for some expert
advice. I have checked old postings, howtos and SuSE support database
to no avail.

We run a SuSE 6.3 machine serving 2 Linux NFS clients and 3 Win (2 98,
1 NT) Samba clients. Setup is done according to NFS howto and yast
(the SuSE setup tool).

The problem is that one of the Linux clients (SuSE 6.4) has
occasionally problems connecting to the NFS server. During boot-up,
it displays the following error message:

Importing Network File System (NFS)lockdsvc: Connection refused

The server /var/log/messages records:

mountd[123] /home/3W_data has been mounted by 192.168.100.105
(the Linux client)

However, client does not have access to the directory. At the same
time, other client accesses same directory without problems.

So far, the problem has gone away after one or several reboots but it
makes life a little bit difficult. Any ideas?

Thanks
Michael

2. SHELL Dependency between scripts??

3. Strange 111 (connection refused) error if sending/receiving with UDP

4. 2.5 PATCH: nvram.c Lindent

5. nfs, Redhat 6.2, "mount: RPC: Unable to receive; errno = Connection refuse"

6. Question about Transparent printing to PC running C332 terminal emulation

7. NFS and telnet "Connection refused" between RH 7 and 8 systems

8. samba support IPX protocol?

9. Cannot start nfs locking services: lockdsvc connection refused

10. nfs error: mount: RPC: Unable to receive; errno = Connection refused

11. NFS connection refused error

12. NFS mount: "Connection refused"

13. NFS connection refused