Hello,
from time to time i'm using NFS to access files located on my desktop (nfs server/debian wheezy) on my pandora (nfs client). This is suddenly broken (still worked yesterday). The pandora sees the desktop inside the network:
------------------------------------------------------------------------------------------------------
arm-dev:/tmp$ nmap sle3
Starting nmap 3.81 ( http://www.insecure.org/nmap/) at 2015-05-23 10:59 CEST
Interesting ports on sle3 (192.168.179.32):
(The 1657 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
22/tcp open ssh
111/tcp open rpcbind
139/tcp open netbios-ssn
445/tcp open microsoft-ds
2049/tcp open nfs
8080/tcp open http-proxy
Nmap finished: 1 IP address (1 host up) scanned in 0.264 seconds
------------------------------------------------------------------------------------------------------
but from the logging of mount command it looks to me like the pandora never trys to access the server:
------------------------------------------------------------------------------------------------------
arm-dev:/tmp$ sudo mount.nfs sle3:/usr/src /sle3/src -vvv
mount.nfs: timeout set for Sat May 23 11:02:31 2015
mount.nfs: text-based options: 'addr=192.168.179.32'
mount.nfs: text-based options: 'addr=192.168.179.32'
[snip]
mount.nfs: text-based options: 'addr=192.168.179.32'
mount.nfs: text-based options: 'addr=192.168.179.32'
mount.nfs: Connection timed out
arm-dev:/tmp$
------------------------------------------------------------------------------------------------------
Does anyone have an idea, where to start investigating this problem.
Regards Stefan
from time to time i'm using NFS to access files located on my desktop (nfs server/debian wheezy) on my pandora (nfs client). This is suddenly broken (still worked yesterday). The pandora sees the desktop inside the network:
------------------------------------------------------------------------------------------------------
arm-dev:/tmp$ nmap sle3
Starting nmap 3.81 ( http://www.insecure.org/nmap/) at 2015-05-23 10:59 CEST
Interesting ports on sle3 (192.168.179.32):
(The 1657 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
22/tcp open ssh
111/tcp open rpcbind
139/tcp open netbios-ssn
445/tcp open microsoft-ds
2049/tcp open nfs
8080/tcp open http-proxy
Nmap finished: 1 IP address (1 host up) scanned in 0.264 seconds
------------------------------------------------------------------------------------------------------
but from the logging of mount command it looks to me like the pandora never trys to access the server:
------------------------------------------------------------------------------------------------------
arm-dev:/tmp$ sudo mount.nfs sle3:/usr/src /sle3/src -vvv
mount.nfs: timeout set for Sat May 23 11:02:31 2015
mount.nfs: text-based options: 'addr=192.168.179.32'
mount.nfs: text-based options: 'addr=192.168.179.32'
[snip]
mount.nfs: text-based options: 'addr=192.168.179.32'
mount.nfs: text-based options: 'addr=192.168.179.32'
mount.nfs: Connection timed out
arm-dev:/tmp$
------------------------------------------------------------------------------------------------------
Does anyone have an idea, where to start investigating this problem.
Regards Stefan