Re: problème configuration nfs-kernel-server
Kohler Gerard <[email protected]> Thu, 25 Jun 2026 09:30:50 +0200
| Newsgroups | gmane.linux.debian.user.french |
|---|---|
| Message-ID | <[email protected]> |
> > Qu'entends-tu par blocage ? Quels sont les symptômes ? > > Sébastien désolé pour la lenteur de la réponse voici quelques éléments : serveur : 192.168.1.AA client : 192.168.1.BB ======== serveur : # ufw status numbered Status: active To Action From -- ------ ---- [ 1] 22/tcp ALLOW IN Anywhere [ 2] 5900/tcp ALLOW IN Anywhere [ 3] 2049 ALLOW IN 192.168.1.BB [ 4] 22/tcp (v6) ALLOW IN Anywhere (v6) [ 5] 5900/tcp (v6) ALLOW IN Anywhere (v6) SSH marche bien dans les 2 sens ping marche bien $ ping 192.168.1.AA PING 192.168.1.AA (192.168.1.22) 56(84) bytes of data. 64 bytes from 192.168.1.AA: icmp_seq=1 ttl=64 time=77.3 ms 64 bytes from 192.168.1.AA: icmp_seq=2 ttl=64 time=99.8 ms 64 bytes from 192.168.1.AA: icmp_seq=3 ttl=64 time=20.1 ms ^C --- 192.168.1.AA ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 20.086/65.729/99.792/33.554 ms mais mount ne marche pas : # mount -v -t nfs 192.168.1.AA:/home/XXX /home/XXX/YYY/ mount.nfs: timeout set for Thu Jun 25 09:28:40 2026 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.AA,clientaddr=192.168.1.BB' mount.nfs: mount(2): No route to host mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.AA,clientaddr=192.168.1.BB' mount.nfs: mount(2): No route to host