For the benefit of those who might be reading this thread in the archives someday...
This test worked just fine: > $ .../amindexd -t > 220 clerk AMANDA index server (2.4.2p2) ready. > SECURITY USER root > 200 Access OK > DATE 2002-01-17 > 200 Working date set to 2002-01-17. > QUIT > 200 Good bye. > ...leading me to conclude that the amrecover binary itself was hosed somehow (I suspect the xinetd 'connection refused from xxx.xxx.xxx.xxx' error was caused by the fact that it wasn't even connecting to the correct port). I upgraded to 2.4.2p2 and sure enough, everything works just great now.
