I came back from the weekend to find one Solaris client failing that has
never had a problem before now... For sake of example, lets say the
client name is A. It failed with an error to the effect:

* A:/ save: SYSTEM error: client `B' is not properly configured on the
NetWorker Server
* A:/ save: Cannot open save session with legatosvr
* A:/var save: SYSTEM error: client `B' is not properly configured on
the NetWorker Server
* A:/var save: Cannot open save session with legatosvr

The server named B is not a backup client and never has been... Both
forward and reverse lookups of A agree from the Networker Server... But
if I add 'B' as an Alias in the configuration of client A, I can now
backup client A with no problems... What causes this to happen ???

Note: Our DNS is managed by a Windows admin, since its Microsoft, I'm a
Unix admin responsible for backups, so I have no control over DNS...
Client A is in our DMZ (192.168.x.x), client B is in our local 10.x net.
Server is 7.2.2 on Win2003, client is Solaris running 7.2 client.

Regards,


Paul G.
--
/"\
\ /     ASCII RIBBON CAMPAIGN
 X        AGAINST HTML MAIL
/ \

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER