In response to various suggestions:

NIC config:
We changed the NICs on the client from 'hardware default' to 100/full.  It
probably was causing some problems.  It still doesn't work, but now I'm
getting a new status message: "Timed out connecting to client (54)", instead
of "Can't connect to client (58)"

Telnet attempt:
After I stop the netbackup client service, start telnet, and configure
telnet to use 13782, I am able to telnet to the client on port 13782.

Bpcoverage:
Running bpcoverage -c <client name> gives:   "Exit status 54: timed out
connecting to client"
Before we changed the NIC duplex setting, it was giving: "Exit status 57:
client connection refused"

Bp.conf:
There is no bp.conf, as the client is Windows 2000.  However, in the
'Backup, Archive, and Restore' GUI the client and server name are definitely
correct.

Hosts file entries:
I've got hosts file entries on the master and the client.  They could ping
eachother before, but it couldn't hurt.  It didn't change anything.
They ping eachother just fine, and can open up eachother's C$ shares.  As
far as I can tell, every type of communication works except for Netbackup.

BPCD on the client IS recieving the request from the master server.  It just
spits out the following every time:
12:37:28.906 [5268.4576] <2> bpcd main: offset to GMT 21600
12:37:28.906 [5268.4576] <2> bpcd main: Got socket for input 668
12:37:28.921 [5268.4576] <2> logconnections: getsockname(668) failed: 10038
12:37:28.921 [5268.4576] <16> bpcd setup_sockopts: setsockopt 1 failed:
h_errno 10038
12:37:28.921 [5268.4576] <2> bpcd main: setup_sockopts complete
12:37:28.921 [5268.4576] <16> bpcd main: authentication failed: 17

I've reinstalled the client software several times.

I appreciate all the replies.  I really need to get this resolved, but it
looks like I have an unusual problem.  I'm probably going to end up going to
Veritas support with this, I guess.

Jesse Gardner