HP3000-L Archives

December 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jim Phillips <[log in to unmask]>
Reply To:
Jim Phillips <[log in to unmask]>
Date:
Tue, 19 Dec 2000 13:08:16 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
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).  However, I can ping the hand held
from the host (HP3000) while it has this display on it.  There is no ping
available on the hand held.  The vendor has taken the hand held back for
more testing (it's hard to believe they did any testing), and believes that
the software on the hand held is incorrect (we had a proof-of-concept demo
using a different hand held that worked fine).

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?  I was thinking
of a packet sniffer or something that could trace the packets from/to this
hand held.  Would that show us anything helpful?

Any ideas are welcome.

Jim Phillips                           Information Systems Manager
Email: [log in to unmask]     Therm-O-Link, Inc.
Phone: 330-527-2124                    P. O. Box 285
Fax:   330-527-2123                    10513 Freedom Street
Web:   http://www.tolwire.com          Garrettsville, OH  44231

ATOM RSS1 RSS2