Hello Tracy,

You mentioned that one system was doing fine...  2nd system was seeing the 
problem... and from the logging message in the $stdlist of JINETD we see:

Received call for: telnet tcp
telnet/tcp: Connection from unknown (10.10.5.5) at Wed Feb 15 15:01:51

... so we can tell the reverse IP to Name lookup failed as the host name 
logged is "unknown".

Question I now have is what differences between the working and failing 
system do you have in the RESLVCNF.NET.SYS file?

~or~

Is there a different network path between the working system and the DNS 
Server and the failing system and the DNS Server?

~or~

Maybe the working system does not have "run inetd -L" configured ?


The warranty and liability expired as you read this message.
If the above breaks your system, it's yours and you keep both pieces.

Regards,
James Hofmeister
Email: <first>.<last>@hp.com
Hewlett Packard - Global Solutions Engineering (WTEC)
P.S. My Ideals are my own, not necessarily my employers. 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *