> From: owner-openssl-us...@openssl.org On Behalf Of chithuanand > Sent: Tuesday, 09 June, 2009 00:13
> The Winsock2 WSAGetLastError() returns 100054, means "Socket > forcefully shut down by remote host". > Precisely 10054 is connection-reset. In TCP "shut down" normally is used for the normal/graceful shutdown i.e. FIN exchange(s). "forcefully shut down" clearly means something different, and the only other prompt possibility is reset/abort using RST, but it's clearer to say reset. "by remote host" may be misleading. In the early ARPAnet-like Internet, resets were always from the remote host. Routers did other things, like ICMP Net,Host Unreachable, but not reset. Nowadays, there are lots of things like gateways, proxies, firewalls, "smart" (too smart for their own good) routers, etc., that sometimes cause/force a TCP reset. If you're connecting through some wireless network/carrier, to me that would definitely be one suspect. If it is in fact coming from the remote host, reset is often (not necessarily always) used if the server process fails. This can mean different things depending on what the server is, e.g. segfault, GPF, unhandled_exception, whatever. > Initially we had only one webservice class. This webservice > class is based on gSOAP generated proxy classes, which will > in turn use openSSL functions to access a secured > webservice.All the methods in this class worked perfectly > till we added one more class, which access another set of > webservices. The new class contains a set of totally disjoint > methods,and it should not affect the existing code. The same > code also works properly in some other networks. > Does the server/service report (usually log) anything relevant to your access/connection/request/whatever? In particular, if it logs something about "server error" you need to look there. If it too reports seeing a reset, coming from your direction, then you need to look for something in the network in between. If this is a network problem, it may be easier to look for it using clear data. Do you have the option of connecting to these servers/services without SSL (or with SSL but using an eNULL ciphersuite) and if so does it have the same problem? (Obviously you should do that only with nonconfidential data. If there is higher-level authentication e.g. password, use a temporarily assigned and immediately disabled test id, etc.) > > SSL_ERROR_SYSCALL means that an underlying call to the > system failed. > > Check errno in that case. > > > Or in desktop-Windows=Winsock2 WSAGetLastError() . > I don't know if windows mobile(?) is the same. > <snip rest> ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
