Regardless of how a system can end up with two STRTCPs, it turned out 
not to be the issue here. I think we've mentioned it to the customer, 
somewhere in our report.
What does worry me is what *else* could be affected by this odd 
combination of "HOSTSCHPTY(*REMOTE)" and a house DNS server responding 
to "LOCALHOST" and "LOOPBACK."
And it puzzles the Hell out of me how and why such a combination would 
arise in the first place. I can grant that there might be some 
legitimate reason to allow DNS to override the Host Table (even if I 
cannot imagine what that reason might be), but having a DNS respond to 
"LOCALHOST" or "LOOPBACK" sounds downright ludicrous, and as I 
discovered, the combination of the two is a recipe for disaster.
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.