Posted: 05 September 2005 at 5:09am | IP Logged

I am using the winsock component in server mode with VB6.  .listen works fine for the initial connection. The socket handle is a positive number and the connection is established.

When the client disconnects, the socket handle goes to -1.

When the client attempts to connect again, it may use a different port to connect with. The OnConnectionRequest event is triggered, but with requestID = -1.

The .accept method is therefore passed -1. The connection does not generate any errorrs, but the .remoteport property still contains the old port number and no further messages are accepted from the client by winsock.

How do I allow winsock to handle connections going away and being re-established?

Posted: 09 March 2006 at 6:18pm | IP Logged

hello

I've got the same problem.

I'm a student, and i was working on a personal script form my final exam, so i used the free version of the component.

I'ts impossible to connect some one who have been already connect, also if it deconect itself before trying reconnection, and also if the client connection program have been close and start again.

I haved also try to restart the server after any client deconnection (i'm working in sigle connection because the free version don't allowed multi connection), it dosent work.

I'm going to be crazy , please, i really need it, or i'll have to use another one.

I hope u can correct easly this bug or give us a solution to avoid it.

Thanks a lot

Posted: 10 March 2006 at 4:16am | IP Logged

Hi neophemus

I persisted for a while as I could not make a class object using the the standard windows axtiveX control with vb6 (enterprise edition only?) and the Ostrasoft product looked like it would provide a more elegent solution to the problem I was working on (PLC to PC based vision system intercommunications)

I never resolved the problem - even though I tried using APIs to try to reset the dll from under it. I gave up and used the windows axtiveX  - which has now been extensively tested and running 24 / 7 in an FDA related production environment in a major pharmaceutical plant for the last 6 months with no problems.

Hopefully ostrosoft will sort this problem

Posted: 15 March 2006 at 3:12am | IP Logged

Keep up the good work - hopefully you will have something next time round.

Peter