Host checking only is useful if you have connections between HP-3000 systems
and use the HOST name or other information in SECURITY/3000 or STREAMX.   A
connection from a PC will always result in the RFA error unless your
$NO-HOST-CHECK encompasses all PCs.  Also, in my experience, the HOST name
does not include the domain & org so the '. hns.com' does nothing except
perhaps cancel out the effectiveness of the @ in front of it.   Try:

$NO-HOST-CHECK @

                -----Original Message-----
                From:   Mike Kapsak [mailto:[log in to unmask]]
                Sent:   Monday, June 28, 1999 10:08 AM
                To:     [log in to unmask]
                Subject:        ** NS/3000 INTERNAL ERROR IN RFA; Job:
#S6569; PIN: 1644; Info: 70

                Good Morning All,

                I am getting these console messages when many users logon to
our system.
                The Response Center informed me that this message appears
when the
                Vesoft product, Security/3000, attempts to query the PC that
is logging
                on.  Although the message says, "REMOTE ABORTED THE
CONNECTION", users
                are actually working fine. The RC recommended adding the
keyword
                $NO-HOST-CHECK to my securcon file. I did so but the
messages keep
                coming up on the console.

                My entry into the file reads $NO-HOST-CHECK @.hns.com. Is
this the
                correct syntax to limit the following messages.


                ** NS/3000 INTERNAL ERROR IN RFA; Job: #S6569; PIN: 1644;
Info: 70
                - Error: 11; Could not receive on socket
                - Socket error    : 64; REMOTE ABORTED THE CONNECTION.

                Thanks in advance,

                Mike Kapsak