Jim Phillips wrote:
>
> We are attempting to connect an RF hand held bar code scanner to the HP3000
> (well, a vendor is trying to do this for us).  We can see the hand held
> connect to the RF access point, but as soon as the hand held attempts to
> connect to the HP, the hand held displays a message about the TCP connection
> being reset (presumably by the host).

What sort of "TCP connection" is it making?  Is there a listener process
running on the 3000 that is holding some particular port open?  Is the
connection TCP (stateful) or UDP (stateless), and is it persistent
across scans?

> If the vendor comes back to me and says that everything on the hand held is
> okay, and that it must be that the host (HP3000) is rejecting the
> connection, what can I do to either prove or dis-prove this?

You can use SOCKINFO with the 'c' (call socket) option, I believe, to
display sockets that are in a listening state.  If your server is
listening on the proper port, it should appear here.

And of course, if you have a firewall or access restrictive device
(router with access lists, inetd service with inetd.sec configured,
etc) insure the listening port is permitted as well as the reply path.

If the connection is TCP, you can try telnetting to the port in question
to see if you can establish a connection.  UDP would require a more
imaginative test (exercise for the reader :-) ).

And a left-field guess, the RF device may presume checksumming, so be
sure the 3000 has checksums enabled (has been covered in the archive).

Otherwise it's off to a packet sniffer or tracing on the 3000.

Jeff Kell <[log in to unmask]>