VB Controls, Winsock Error 10016 "Connection forcefully rejected"

Winsock Error 10016 "Connection forcefully rejected"

Author	Message
AC #1 / 4	Winsock Error 10016 "Connection forcefully rejected" Hello, I run into this error internittantly. Does anyone know the cause? TIA
Mon, 19 Mar 2001 03:00:00 GMT

Souheil Charad #2 / 4	Winsock Error 10016 "Connection forcefully rejected" Hey, I ran into the smae problem few days ago, and I did nt find an explanation to it but what I can tell you is, it has to do with the current state of the connection, the protocol used (udp or TCP) and the name of the remote machine. I changed my app to work with UDP and the communication worked only on a lan, however the port was always Unrecognized. ( saw it on a protocol analyzer ). I would apreciate a feedback if you find it out. I could not find a doc that explains all the Err codes of the winsock control. apparently, certain operations can not be done when certain statuses are true..... I'm looking for something like that, i'll post it if I find it. Thanks Quote: >Hello, >I run into this error internittantly. Does anyone know the cause? >TIA
Mon, 19 Mar 2001 03:00:00 GMT

Souheil Charad #3 / 4	Winsock Error 10016 "Connection forcefully rejected" Hey, I ran into the smae problem few days ago, and I did nt find an explanation to it but what I can tell you is, it has to do with the current state of the connection, the protocol used (udp or TCP) and the name of the remote machine. I changed my app to work with UDP and the communication worked only on a lan, however the port was always Unrecognized. ( saw it on a protocol analyzer ). I would apreciate a feedback if you find it out. I could not find a doc that explains all the Err codes of the winsock control. apparently, certain operations can not be done when certain statuses are true..... I'm looking for something like that, i'll post it if I find it. Thanks Quote: >Hello, >I run into this error internittantly. Does anyone know the cause? >TIA
Mon, 19 Mar 2001 03:00:00 GMT

Bob Butle #4 / 4	Winsock Error 10016 "Connection forcefully rejected" Quote: >Hey, I ran into the smae problem few days ago, and I did nt find an >explanation to it but what I can tell you is, it has to do with the current >state of the connection, the protocol used (udp or TCP) and the name of the >remote machine. <cut> >>I run into this error internittantly. Does anyone know the cause? You will get that error if you set the RemoteIP to a valid IP address but set the RemotePort to a value for which no application is currently waiting in "Listen" mode. It means that TCP/IP contacted the server, but no application was accepting calls at the given port number.
Mon, 19 Mar 2001 03:00:00 GMT

Page 1 of 1

[ 4 post ]