>> #define EBADRPC         72              /* RPC struct is bad */

>> use tcpdump or equivalent and find out exactly what is happening on
>> the network to investigate further...

> [...]
> 17:31:20.976174 guybrush.sunrpc > lechuck.1023: udp 76 (ttl 64, id 17781)
> 17:31:21.485919 arp who-has guybrush tell lechuck
> 17:31:21.485919 arp reply guybrush is-at 0:c0:df:62:50:d2
> 
> As far as I can see it looks fine to here.
> 
> 17:31:21.505909 lechuck.1022 > guybrush.849: udp 80 (ttl 4, id 0)
> 17:31:23.524899 lechuck.1022 > guybrush.849: udp 80 (ttl 4, id 0)
> 17:31:27.532894 lechuck.1022 > guybrush.849: udp 80 (ttl 4, id 0)
> 17:31:35.528894 lechuck.1022 > guybrush.849: udp 80 (ttl 4, id 0)
> 
> This is when the booting gives up and returns error 72.

This isn't very informative; if there is a problem, it will be with the
*contents* of the packets.  Get tcpdump to print out full contents and
it may be possible to guess more accurately from that.  (This is one
thing I really dislike about tcpdump as opposed to etherfind: by
default, tcpdump throws away the information I'm usually looking for -
the packet contents.  The other thing I really dislike about tcpdump is
that even when you do get it to print packet contents, it is
inconsistent about whether it prints the link-level header or not,
which makes it borderline impossible to mechanically unpack the packet
contents.)

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B