Hello Everyone

Just debugged a status 59, 58 that I'm rather surprised that I figured out.

You see, the client is a Windows NT box with two gigabit interfaces, different
IP addresses on the same subnet but the same hostname for both addresses.

The status 59 was due to the master server using one DNS server that could
resolve the name to address but the media server used another one that wasn't
pulling the zone.   I dutifully sent email complaining about this to the DNS
team then I decided to grab an image by temporarily stuffing the ipaddresses
into the media servers host table which is when I started getting status 58's.

Turns out that due to the way the A records was being spit out for the name
resolution on the master server and the way the host table match was occurring
on the media server, the two servers were using different ip addresses to
reference the client hence the status 58.    Allowing only one name to ipaddress
match on both servers allowed the backups to complete normally.

It's interesting that NT allows single name to multiple ipaddress name
resolution (it round robins on them, I tested that) while the standard is for
single or multiple name to single ip address matching, it's more interesting
that NT administrators go ahead and do it.   Since I don't see Microsoft ever
playing fair, Veritas will probably have to expand their ip address to name
matching algorithms a bit.   Meanwhile I guess I'll have to hardwire some hosts
table entries.

Regards,
John I Wang
Sr. Systems Engineer
Steverson Information Professionals

---
Enron Networks
Enron Building room 3427e
ph (713) 345-4888
cell (832) 493-1263
fax (713) 646-8462
pg pagejwang AT skytel DOT com or 1-877-390-4155






**********************************************************************
This e-mail is the property of Enron Corp. and/or its relevant affiliate and 
may contain confidential and privileged material for the sole use of the 
intended recipient (s). Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender or reply to Enron Corp. 
at enron.messaging.administration AT enron DOT com and delete all copies of the 
message. This e-mail (and any attachments hereto) are not intended to be an 
offer (or an acceptance) and do not create or evidence a binding and 
enforceable contract between Enron Corp. (or any of its affiliates) and the 
intended recipient or any other party, and may not be relied on by anyone as 
the basis of a contract by estoppel or otherwise. Thank you. 
**********************************************************************