Hey Kevin,

        Unfortunately I do not have control over the remote program.  It's a
third party vendor for credit card authorization.  All your assumptions are
correct.  In your statement "Or use a UDP listener to receive control
signals like "reset".", I'm assuming that their listener is set up to
receive a "reset", since they are asking us to do so.  I just don't know how
to programmatically send a reset control signal.  That's what I really need.


Thanx
  Dane
----------------

Kevin Wrote :


-----Original Message-----
From: Keven Miller [mailto:[log in to unmask]]
Sent: Wednesday, July 23, 2003 12:59 PM
To: [log in to unmask]; [log in to unmask]
Subject: RE: [HP3000-L] TCP/IP RESET


What I picture with this description is that the remote system
program listens for one connection only, and apon making a connection,
goes into its processing with that socket -- No listener is active now.

When you drop the connection from local system, the remote will hang onto
its socket until aborted, or tcp-timeouts on the connection. At which point
the remote program would either need to be restarted or it loops around
and listens once more for a new connection.

So you cannot re-connect until the remote program re-issues a listener.

If you have control to change the remote program, you could change it
to always have a listener active and handle a new connection as desired,
as well as clean up of the old. Or use a UDP listener to recieve
control signals like "reset".

If you do not have control of the remote program, I don't know (yet)
what you could do.

___________________________________________________________________
Keven Miller   mailto:[log in to unmask]   http://www.exegesys.com

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