Winsock won't close {RESOLVED}

[vb_paladin]

I have a listbox containing user's computer names. When I click on a name, my single winsock control connects to that user's computer fine. But when I click on a different name, I have the code

Winsock1.Close: DoEvents

to close Winsock1 and enable it to connect to that user. But the event

Private Sub Winsock1_Close()

End Sub

never fires and therefore Winsock1 never closes. How can I make it close??

[Walter]

I don't think that DoEvents should really be there after your Winsock1.Close.

have a public variable holding the state of the winsock and check it before connection to another computer

Dim wconn As Boolean
 
Private Sub Winsock1_Close()
     wconn = False
End Sub

then in your listbox code

Winsock1.Close
     If wconn = False Then
          wconn = True
          'connect
     End If

[vb_paladin]

It still doesnt work. This is the code for my listbox.

When the user clicks a different name in the listbox, sckOut should disconnect from the current user it is connected to, and reconnect to the new username that is selected.

Private Sub lstUsers_Click()
If lstUsers.List(lstUsers.ListIndex) = strLocalName Then
    Exit Sub
ElseIf lstUsers.List(lstUsers.ListIndex) = strUserName Then
    Exit Sub
End If
 
lstUsers.Enabled = False
 
If sckOut.State = sckConnected Then
    sckOut.SendData "DISCONNECTING_USER": DoEvents
    sckOut.Close
End If
 
strUserName = lstUsers.List(lstUsers.ListIndex)
strUserPort = lstPorts.List(lstUsers.ListIndex)
sckOut.RemoteHost = strUserName
sckOut.RemotePort = strUserPort + 1
sckOut.Connect
End Sub

[Spajeoly]

The Private Sub:

Private Sub Winsock1_Close()
 
End Sub

Only fires when the connection is closed by the remote host. You can make winsock connect right after you close it in your code..

[vb_paladin]

so I don't have to send a message telling the remote host to close the winsock

sckOut.SendData "DISCONNECTING_USER

All I have to do is do sckOut.Close locally and then the remote host's Winsock1_Close() event will fire and disconnect, correct?

[Spajeoly]

Should do.

[ccoder]

Originally posted by vb_paladin
and therefore Winsock1 never closes. How can I make it close??

Spajeoly answered part of your question, but from the above quote, it appears that there may more to your problem.

Do you know for a fact that Winsock1 does not close? Or was this an assumption because you didn't see the Winsock1_Close sub fire?

If you are hardcoding a LocalPort number, the connection will remain in a TIME_WAIT mode for about 4 minutes after closing and you will not be able to connect during that time. Be sure to set LocalPort to zero and let the system select an unused port number every time you connect.