I have a LTSP server that works perfectly for my other LTSP clients, but for one client NFS does not work.
The client says: [...] "Mounted devfs on /dev" "Freeing unused kernel memory: 52k freed" "nfs: server 192.168.0.254 not responding, still trying" I can ping the client no problem: [13:29:43]hans@samir:~>ping 192.168.0.4 PING 192.168.0.4 (192.168.0.4): 56 data bytes 64 bytes from 192.168.0.4: icmp_seq=0 ttl=255 time=21.4 ms 64 bytes from 192.168.0.4: icmp_seq=1 ttl=255 time=1.9 ms syslog on the server says: rpc.mountd: authenticated mount request from ws004:800 for /opt/ltsp/i386 (/opt/ltsp/i386) tcpdump on the server says: 13:35:58.280752 arp who-has ws004 tell samir 13:35:58.694867 arp who-has samir tell ws004 13:35:58.694959 arp reply samir is-at <mac-address of the server> 13:35:58.695660 ws004.800 > samir.sunrpc: udp 56 (DF) 13:35:58.698360 samir.sunrpc > ws004.800: udp 28 (DF) 13:35:58.701021 ws004.800 > samir.sunrpc: udp 56 (DF) 13:35:58.702350 samir.sunrpc > ws004.800: udp 28 (DF) 13:35:58.704568 ws004.800 > samir.1028: udp 60 (DF) 13:35:58.720063 samir.1028 > ws004.800: udp 60 (DF) 13:35:58.723112 ws004.62971347 > samir.nfs: 104 getattr [|nfs] (DF) 13:35:58.723508 samir.nfs > ws004.62971347: reply ok 96 getattr DIR 40755 ids 0/0 sz 1024 (DF) 13:35:58.725354 ws004.79748563 > samir.nfs: 104 fsstat [|nfs] (DF) 13:35:58.725806 samir.nfs > ws004.79748563: reply ok 48 fsstat [|nfs] (DF) 13:35:58.727904 ws004.96525779 > samir.nfs: 112 lookup [|nfs] (DF) 13:35:58.750439 samir.nfs > ws004.96525779: reply ok 128 lookup [|nfs] (DF) 13:35:58.755085 ws004.113302995 > samir.nfs: 112 lookup [|nfs] (DF) 13:35:58.755409 samir.nfs > ws004.113302995: reply ok 128 lookup [|nfs] (DF) 13:35:58.757425 ws004.130080211 > samir.nfs: 112 lookup [|nfs] (DF) 13:35:58.757963 samir.nfs > ws004.130080211: reply ok 128 lookup [|nfs] (DF) 13:35:58.760669 ws004.146857427 > samir.nfs: 116 read [|nfs] (DF) 13:35:58.761531 samir.nfs > ws004.146857427: reply ok 1472 read (frag 50026:1480@0+) 13:35:58.762123 samir > ws004: (frag 50026:1480@1480+) 13:35:58.763318 samir > ws004: (frag 50026:1244@2960) 13:35:59.460548 ws004.146857427 > samir.nfs: 116 read [|nfs] (DF) And then the following lines are repeated: 13:36:09.266495 ws004.146857427 > samir.nfs: 116 read [|nfs] (DF) 13:36:09.267279 samir.nfs > ws004.146857427: reply ok 1472 read (frag 50030:1480@0+) 13:36:09.267860 samir > ws004: (frag 50030:1480@1480+) 13:36:09.269062 samir > ws004: (frag 50030:1244@2960) Occasionally mixed with lines like: 13:36:03.690757 arp who-has ws004 tell samir 13:36:03.691501 arp reply ws004 is-at <mac-address of the client> The computers are connected through a hub. The firewall at the server is told to accept every packet from the clients mac-adress. The client is mentioned in /etc/hosts The client boots netboot, since the nic Etherworks III, is not supported by etherboot. Clues, anyone? -- Hans Ekbrand
msg04806/pgp00000.pgp
Description: PGP signature
