All servers and clients all talk to each other and they al perform reverse lookup, so the thing I always do, even before attempting a backup of a new client (because the DNS team at my site always forget - so it seems), is to:
from client:
nslookup master-name
nslookup master-name
nslookup media-name
nslookup media-name
nslookup client-name
nslookup client-name
nslookup master-ip
nslookup master-ip
nslookup media-ip
nslookup media-ip
nslookup client-ip
nslookup client-ip
...and then I run all twelve commands again on the media, and then all twelve again on the master.
Then after this, I run the equivalent for:
bpclntcmd -hn master-name
bpclntcmd -hn master-name
bpclntcmd -hn media-name
bpclntcmd -hn media-name
bpclntcmd -hn client-name
bpclntcmd -hn client-name
and the same size ahain but with -ip <machine-ip> i.e. each IP addy twice (I'm getting bored with typing - but ended up typoing more anyway - sheez!)
and then all twelve commands again from media and then from client...
As you can probably guess I have a little short script to do it for me...
It's the only way I know to confirm:
1) No duplicate reverse DNS.
2) No duplicate DNS.
3) No confusion between DNS and hosts files
4) No funnies with WINS
If things don't work after this try from the master:
$ bpgetconfig -M media-name SERVER
$ bpgetconfig -M client-name SERVER
and check that for both that the first entry of "SERVER = <blah>" is the master server name.
The try:
$ bpgetconfig -M client-name SERVER
...and:
$ bpgetconfig -M client-name MEDIA_SERVER
and check that your media server is listed in one of or both lists.
HTH,
Dave.