->>In response to your message<<-
  --received from Dustin J. Mitchell--
>
> Sorry, there are a lot of moving parts here, and they all need to move
> in the same direction.
> 
> Both server and client should be compiled to include bsdtcp (and
> whatever else -- doesn't matter).
> 
> Both server and client should be configured to use bsdtcp - the server
> in the dumptype, and the client in /etc/amanda/amanda-client.conf.
> 
> The client should be listening for TCP connections using the bsdtcp plist.
> 
> It's messy, I know -- it's all there for historical reasons.
> 

Okay, I see how this should work . . . but I'm not getting the desired
result on my end.

If I do everything you specify above, the server won't connect with the
client.  I can only get the server to connect to the client if I also
compile the client with bsdudp and load the according plist file.  Then
I get the "client configured for auth=bsdudp while server requested
'bsdtcp'" even when the amanda-client.conf specifies "auth bsdtcp".

So, I'm to the point (unless you have any other suggestions to resolve
the problem with bsdtcp alone not connecting) of just going with
bsdudp.  I know you suggested bsdtcp and I would like to get this to work
but it just won't.  I assume you suggest bsdtcp over bsdudp for
security reasons.  Is bsdudp that bad?

If I'm forced to go with bsdudp and configure both server and client to
use bsdudp instead of bsdtcp, I still get this error message with an
amcheck

 [client configured for auth=bsdudp while server requested 'BSD']

If you notice in my previous emails, this line has always been at the
top before subsequent lines which then switch to "server requested
'bsdtcp'".  Any idea on this?

Thanks again for all the help!!!

Paul