[RESOLVED] Winsock wont connect (Resolved)

I am having a problem with winsock in my app, I can connect to the sever when I test it using my demo but when I use the actual application it wont connect. Below is the code I am using to connect to the server:

VB Code:

Private Sub Command2_Click()
messcon.Connect txtConnect, 7000
If messcon.State = sckConnected Then
Command2.Enabled = False
Else
MsgBox (LoadResString(68 + i))
End If
End Sub

I keep getting the please connect message showing up. It worked find before I added this code:

VB Code:

Private Sub Command3_Click()
If Not txtAttachment.Text = "" Then
NF = FreeFile
Open cmdAttach.FileName For Input As #NF
Input #NF, data
fname = cmdAttach.FileTitle
messcon.SendData "|DATA|" & data & fname
Close #NF
End If
End Sub
 
Private Sub Messlis_DataArrival(Index As Integer, ByVal bytesTotal As Long)
If InStr(1, str, "|DATA|") <> 0 Then
 NF = FreeFile
 MkDir (App.Path & "\Received Files\")
 Open App.Path & "\Received Files\" & fname For Output As #NF
 Print #NF, data
 Close #NF
 End If
End Sub

TIA

Nightwalker83

What protocol u r using? and what is the description of error.....?
please elaborate!

1. TCP Protocol

2. It's not an error message just a message thats part of my application.

Still not enough information to reach to any conclusion...
well.. if using TCP, have u made another winsock listening to your connect request? and also.. the winsock which is in listening mode cannot accept the connection request..

VB Code:

Private Sub Form_Load()
On Error Resume Next
intmax = 0
Messlis(intmax).LocalPort = 7000
Messlis(intmax).Listen
End Sub

This is the code I am using for the connection request:

VB Code:

Private Sub Messlis_ConnectionRequest(Index As Integer, ByVal requestID As Long)
'Allow the chat app to accept more than one connection
If Index = 0 Then
      intmax = intmax + 1
    Load Messlis(intmax)
Messlis(intmax).Accept requestID
End If
If Messlis(intmax).State = sckError Then
MsgBox (LoadResString(67 + i))
End If
End Sub

This code was working before so I don't think this is the problem since I didn't change it.

and the code in ConnectionRequest event...Where u are accepting the request...????

What do you mean?

The connection request is in the post above yours you missed it :D :D :D


Post the whole project if you can :) :) :)

What is the error message?

He has one winsock control listening (index = 0) and then he creates a new winsock control for every new user. -Note: You don't have to use something like intMax, just use messlis.UBound when creating new winsock controls-

However, as described on winsockvb.com, you are going to have to create a boolean array along with your winsock controls, and replace your code with this under connection_request.

Code:

---

for i = messlis.LBound to messlis.ubound
if Connection(i) = False then 'There is an empty winsock control..
messliss(i).accept requestID
connection(i) = true 'Set the boolean to true, it is taken
exit sub
end if
next i

If Index = 0 Then
      intmax = intmax + 1
    Load Messlis(intmax)
Messlis(intmax).Accept requestID
End If

---

Quote:

---

Originally posted by jeb2022

Code:

---

for i = messlis.LBound to messlis.ubound
if Connection(i) = False then 'There is an empty winsock control..
messliss(i).accept requestID
connection(i) = true 'Set the boolean to true, it is taken
exit sub
end if
next i

---

---

I tried this code but it up with a Sub or Function not defined error on this line:

VB Code:

if Connection(i) = False then

Private Connection(200) as boolean

This will just inform your app as to wether your winsock is in use.

you need to check through all currently loaded winsocks to see if they have a connection established, if not then the user on that winsock has left and it is free for use. The boolean indicates which are in use and which are not.

NOOOOOOOOOOOOO


in command2_click event you cant have

Code:

---

If messcon.State = sckConnected Then
Command2.Enabled = False
Else
MsgBox (LoadResString(68 + i))
End If

---

Wait for the connect event to fire on the winsock control. That will indicate when you are connected.

The winsock is still trying to connect when you display your message but hasnt actually completed connecting :) :) :) :)

The statements after connect were probably immediately fired before the connection negotiation finished. I had the same problem and I also return a value (boolean in my case), you can also try something like this.

VB Code:

'blah blah
Attempt_Connect:
    frmCommon.sckTCP(SocketIndex).Close
    frmCommon.sckTCP(SocketIndex).LocalPort = 0
On Error GoTo Error_Handler
    frmCommon.sckTCP(SocketIndex).Connect Trim(strIPAddress)    'Connect attempt
On Error GoTo 0
    
    Count_Pause = 0
    Do Until Count_Pause >= MAX_Retry
        If frmCommon.sckTCP(SocketIndex).State = sckConnected Then
            Count_Pause = MAX_Retry
        Else
            Call Pause(15)
            Count_Pause = Count_Pause + 1
        End If
    Loop
    
    If frmCommon.sckTCP(SocketIndex).State <> sckConnected Then
        GoTo Error_Handler  'Retry connecting while Count_Connect < 3
    End If
    
    ConnectSocket_sckTCP = True
    GoTo Exit_Proc
 
Error_Handler:
 
    Count_Connect = Count_Connect + 1
    If Count_Connect >= MAX_Retry Then
        'blah blah
         GoTo Exit_Proc
    Else
        GoTo Attempt_Connect    'Retry connect.
    End If
 
Exit_Proc:
 
End Function

BTW, I used Exit_Proc because is still had some statements which I did not include here. Essentially, you do a loop, up to three times, to check the state of the socket.

Pause() is a user defined pause using GetTickCount with DoEvents in it. I noticed that when I set pause to 10 milliseconds the loop occurs twice before the socket state becomes connected. When I changed it to 15 milliseconds, I passed through the loop only once.

This will not work for slow connections (post Above)

you are both making it more complicated than neccassary :) :)

When using winsock ensure you have Service Pack 5 Installed for VB

Actually, the Connect event fires first. But I went to the trouble of the loop so that my Connect_sckTCP() procedure will return a correct value. Here's an excerpt from the procedure trace I did:


16:31:57 - 0000000014 START ConnectSocket_sckTCP(1, 202.81.179.144).[/B]
16:31:57 - 0000000015 START CheckIfExist_sckTCP(1, ).
16:31:57 - 0000000016 RETURNED CheckIfExist_sckTCP(1, ) = 1
16:31:57 - 0000000017 CONNECT frmCommon.sckTCP(1) TO 202.81.179.144 'This is right before I use connect method.
16:31:57 - 0000000018 START Pause(15).
16:31:57 - 0000000019 START frmCommon.sckTCP_Connect(1). 'This is the Winsock event.
.
.
frmCommon.sckTCP_ConnectionRequest(0, 1040). 'Because I did a loop connect.
.
.
16:31:57 - 0000000041 RETURNED ConnectSocket_sckTCP = True

Quote:

---

Originally posted by BodwadUK
NOOOOOOOOOOOOO


in command2_click event you cant have

Code:

---

If messcon.State = sckConnected Then
Command2.Enabled = False
Else
MsgBox (LoadResString(68 + i))
End If

---

Wait for the connect event to fire on the winsock control. That will indicate when you are connected.

The winsock is still trying to connect when you display your message but hasnt actually completed connecting :) :) :) :)

---

I replaced the code you mentioned with:

VB Code:

Private Sub Command2_Click()
messcon.Connect txtConnect, 7000
If messcon.State = sckConnected Then
Command2.Enabled = False
Else
Exit Sub
End If
End Sub

My prog seem to work fine now.

Quote:

---

Originally posted by BodwadUK
This will not work for slow connections (post Above)

you are both making it more complicated than neccassary :) :)

When using winsock ensure you have Service Pack 5 Installed for VB

---

True, but I'll be using it only on a LAN. Besides, my app needs a fast connection so if didn't connect because of the lag then its not worth connecting anyway. The slow connect will defeat the purpose.

Quote:

---

Originally posted by Nightwalker83
I replaced the code you mentioned with:

VB Code:

Private Sub Command2_Click()
messcon.Connect txtConnect, 7000
If messcon.State = sckConnected Then
Command2.Enabled = False
Else
Exit Sub
End If
End Sub

My prog seem to work fine now.

---

You can just as well replace it with:

VB Code:

Private Sub Command2_Click()
    messcon.Connect txtConnect, 7000
End Sub

because there is no way the socket connects that fast that you can check for it in the next line of code. Not even in a LAN.
If you want to disable Command1 after the connection succeeded use something like:

VB Code:

Private Sub messcon_Connect()
    Command1.Enabled = False
End Sub

Quote:

---

Originally posted by Frans C
You can just as well replace it with:

VB Code:

Private Sub Command2_Click()
    messcon.Connect txtConnect, 7000
End Sub

because there is no way the socket connects that fast that you can check for it in the next line of code. Not even in a LAN.
If you want to disable Command1 after the connection succeeded use something like:

VB Code:

Private Sub messcon_Connect()
    Command1.Enabled = False
End Sub

---

That code isn't working.

it is actually connecting isnt it :) :) :) :)

Nope :(

You have got a socket listening as a server havent you???? :confused: :confused:

Yes as I said it was working before prefectly alright before I made the changes. I didn't not change anything in the Messcon or Messlis connection events so I don't know what the problem could be.

Doevents maybe? :confused:

You'd be surprised how many times that can solve a problem.

Quote:

---

Originally posted by Pc_Madness
Doevents maybe? :confused:

You'd be surprised how many times that can solve a problem.

---

You'de be surprised how many times it can CAUSE a problem as well, especially if you use it in winsock events (DataArrival for instance).

I tried your app and the connection works fine. Only change I made was remove the code that disabled the connect button if the entered IP address is equal to the localIP. That way I could do a local connect and it worked fine except for the popping message.

The message pops up because you immediately did a compare on the socket state though it hasn't changed yet. But when I checked the state of the socket it was already connected and I could send messages.

Quote:

---

Originally posted by leinad31
I tried your app and the connection works fine. Only change I made was remove the code that disabled the connect button if the entered IP address is equal to the localIP. That way I could do a local connect and it worked fine except for the popping message.

---

I removed the following code and it seems to be working.

VB Code:

If txtConnect.Text = messcon.LocalIP Then
Command2.Enabled = False
Command4.Enabled = False
Else
Command2.Enabled = True
Command4.Enabled = True
End If

Quote:

---

The message pops up because you immediately did a compare on the socket state though it hasn't changed yet. But when I checked the state of the socket it was already connected and I could send messages.

---

Yeah I used this code to check for the connection state:

VB Code:

Private Sub Timer2_Timer()
Select Case messcon.State
Case "7"
Me.Caption = Me.Caption & " - Connected"
Case "8"
Me.Caption = Me.Caption & " - Connection was closed"
End Select
End Sub

I had all the connection states but Messcon proberly wouldn't have encounted them.