Winsock

Hello!

I have a problem using Winsock with my application.

I'm using the UDP protocol.

I have two programs, the client and the server.

The server sends data every 2 seconds.

If I start the server first and then the client, it works.

But, if I start the client first, it does not get the data.

Likewise, if I exit the server and then reload it, the client does not get the data.

Why is this?

Thanks!

Do the server and client attempt to connect immediatly after they are run or does the user start the connection?

They never "connect" the server just sends a small string every two seconds.

i dont see what is wrong then, it should work. Anyone?

they dont connect? :confused:

Without some sort of connection or connection attempt, how do you know anything is working at all?

Quote:

---

Originally posted by etoo


If I start the server first and then the client, it works.

But, if I start the client first, it does not get the data.

Likewise, if I exit the server and then reload it, the client does not get the data.

Why is this?

Thanks!

---

perhaps the reason for it not working after reload is the winsock wasn't closed? Make the code close the winsock on connection if it is not used anymore something like this:

VB Code:

Private Sub Winsock1_ConnectionRequest(Index As Integer, ByVal requestID As Long)
 
If Winsock1(Index).State <> sckClosed Then
        Winsock1(Index).Close
End If
'plus all other connection code
End Sub

In general, you should use the TCP protocol when you need a client-server relationship.

If you absolutely *have* to use UDP, make sure that your RemotePort and Bind settings are set up correctly when both the server program and client program load.