Hello,
we recently went through a little DNS re-organizational change. We get 
forward resolutions through a different host than we get inverse 
resolutions. Ever since this some of backs have intermittently failed.


Primary problem (repeatable) is hp-ux networker server 7.1.1 . Windows 
client. both the server and the client, using DNS, can lookup each other 
with both FQDN and short names as well as inverse using IP address.

And yet the client cannot find the server using winworkr (Networker User). 
I keep getting daemon.log entries on the server that say "Host name 
verification failed - unknown host: then the IP address. Yet I can do an 
nslookup of that IP address and see a name. And it is the same name as the 
client and its aliases.

Since nslookups, ping, etc all show no errors, yet Networker can't seem to 
resolve the problem, I don't know what to do. Actually I do - if I put the 
client in the hosts file of the server, it works. (the same names as shows 
in DNS). This is not an acceptable situation. I don't want to populate a 
hosts file since DNS works just fine.

Using various debug and  verbose options, I see the problem appears to be 
in the auth_lgto routines.

Help?
Thanks
/ Sid /

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