[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: urgent problem with gsk error in http api - resolved



Sender: "Ian Patterson" <ian@xxxxxxxxxxxxxxxxxxxx>

We have resolved the issue with the socket disconnect problem - the answer
may be of use to other Users.

The system (here in the UK) finally gets out to the Internet via a gateway
in the USA, controlled by a network group in the States.
Last week this group installed a spam filter (called Websense ??) which
checked https and http traffic. The spam filter caused the sockets problem.
Everything OK when the filter was turned off.

Just one more thing to look for when things go AWOL.

Thanks for helping.

Regards

Ian Patterson

ian@xxxxxxxxxxxxxxxxx <mailto:ian@xxxxxxxxxxxxxxxxx>

Grange IT Limited
tel 01947 880458
www.grangesystems.com



-----Original Message-----
From: owner-ftpapi@xxxxxxxxxxxxx [mailto:owner-ftpapi@xxxxxxxxxxxxx]On
Behalf Of Scott Klement
Sent: 19 January 2005 19:29
To: ftpapi@xxxxxxxxxxxxx
Subject: RE: urgent problem with gsk error in http api


Sender: Scott Klement <klemscot@xxxxxxxxxxxx>

On Wed, 19 Jan 2005, Ian Patterson wrote:
>
> Thanks Scott, I had guessed something like that.
> What I did not know was if this may be internal to the as/400 or external
> (i.e. anything physically outside of the box - Lan, routers, all that
> rubbish).

IT could be internal. Or it could be on the server. Or it could be any of
the devices in between.

That's the problem with this error -- all we know is that the socket was
disconnected, we don't know WHY it was disconnected, or what caused it.


> Since I sent the first e-mail, the customer has attempted many re-tries,
and
> one got through, then more failures.

The fact that one of them worked makes it more likely that it's a hardware
error.  Software errors are usually consistent (always fail or always
succeed) whereas hardware tends to be more sporadic.


> Just for the record, the socket re-set (i.e. disconnect) is not likely to
be
> the remote server having a wobbly ? - I would have expected another type
of
> message for that.

I've never heard the phrase "having a wobbly"?  But if you mean "having
problems" yes, it could the server having problems...  It could be pretty
much anything.  But, like I said, I think it's more likely to be hardware,
since you can get it to work if you keep trying.

The hardware problem could be on either end of the connection, but if
other clients are connecting to the same server without problems, it's
likely to be the client's end rather than the server's end...
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------


-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------