So This leads me to think that TWSocket is not
closing/freeing/de-allocating
the LocalPort, such that when I try to reopen the connection a few seconds
after I close it, windows raises the 10048 error due to the LocalPort
still
being allocated
Is this the case
No, it isn't. But Windows
Hi...
Quote:
>When you don't assign the LocalPort, Windows automatically assign an
>available local port. This is usually what is done for connecting to a
>remote host. If you have any reason not to do so, just explain why.
If I use this code:
TheTCPClientSocket->Addr = TCP_ClientAdd
I have got to the bottom of the Error 10048
This means the port you are trying to use is already used and thus is no
more available.
It seems that the order in witch you assign values to the TWSocket
properties when you want to open a client is important
- so now I can open and close the c
Hi...
I have got to the bottom of the Error 10048
It seems that the order in witch you assign values to the TWSocket
properties when you want to open a client is important
- so now I can open and close the client heaps of times with out the
error 10048 being raised :-)
The code I was using l
RayA @ Ihug wrote:
> When I call the TWSocket->Connect() for the first time every thing
> works perfectly, the connection is made and data can be Rx'ed and
> Tx'ed without problems
>
> then I call TWSocket->Close()
>
> and a few seconds later I call TWSocket->Connect()
>- In the OnSessionCon
Try setting the ReuseAddr property to true. This might help.
Justin.
-Original Message-
From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On
Behalf Of RayA @ Ihug
Sent: Thursday, 31 March 2011 9:35 AM
To: twsocket@elists.org
Subject: [twsocket] TWsocket connection
Hi all...
I am running on Windows XP, Embarcadero XE
I am using the TWSocket Version:7.47 in Client mode to connect to another
PC on my LAN which is also using TWSocket in Listen mode.
When I call the TWSocket->Connect() for the first time every thing works
perfectly, the connection is mad
