| Dart Home | PowerTCP Sockets for .NET | Custom Development | Reply | PowerTCP Sockets for .NET (Secure and Standard) Topics | Forums |
| Author | Forum: PowerTCP Sockets for .NET (Secure and Standard) Topic: 15 second delay in connected event firing |
| wLucking will_affinity@yahoo.com From: Gardena, CA USA Posts: 6 Member Since: 11/21/02 |
posted January 27, 2005 12:29 PM I am using PowerTCP SSL for .NET client and server. The client connects quickly to the server. The client's connected event then always takes 15 seconds to fire. I'm not sure where the 15 seconds is coming from. Any ideas? |
Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted January 27, 2005 12:38 PM There is negotiation that goes on during the connection process. For some reason your server is taking a long time to do it. Does it happen every time you connect? Or just the first time after the Tcp object is instantiated? |
| wLucking will_affinity@yahoo.com From: Gardena, CA USA Posts: 6 Member Since: 11/21/02 |
posted January 27, 2005 12:44 PM The delay occurs only when there hasn't been activity with the server for several seconds. The strange thing is it is always 15 seconds for the connected event to fire in those cases. When activity is coming from the client continuously, less than one second to establish a new connection after closing the old, then there is no delay for handling new connections from that client. |
| Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted January 27, 2005 1:35 PM It's probably some sort of delay on the server. If you want us to figure it out, please send us the info we need to connect to the server. Make sure you include your serial number in the email. Send it to support@dart.com |
| wLucking will_affinity@yahoo.com From: Gardena, CA USA Posts: 6 Member Since: 11/21/02 |
posted January 27, 2005 2:17 PM The client application and server are in too advanced stage of development to where it would not be practical to send them. I'll try to figure it out on my own or possibly create a workaround. I thought I'd ask anyway. |
| wLucking will_affinity@yahoo.com From: Gardena, CA USA Posts: 6 Member Since: 11/21/02 |
posted January 27, 2005 9:12 PM I’d like to share with you what the problem was. I was running CA certificate service off one of my Windows servers within the LAN, which also happened to be the primary domain controller. About a week or two ago I re-installed that server and forgot there was a CA service previously I also changed the domain name of the Windows domain (the purpose for the reinstallation). The cert on my computer, used for development, was issued off the legacy version of that server and it’s CA. To solve the problem I setup a new enterprise CA and issued a new cert to my development machine. No more delays. I’m not sure why there was a timeout of 15 seconds, maybe because it was trying to authenticate the root authority, which didn’t exist, causing the delay and resulting timeout? I’m not completely familiar with all that goes on, but it is good to have it fixed. Cheers. |
| Reply | PowerTCP Sockets for .NET (Secure and Standard) Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|