| 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: Server 2012 Errors |
| cbenard From: USA Posts: 21 Member Since: 04/20/07 |
posted January 23, 2014 10:46 AM Hello. We've been using Dart PowerTCP SSL Sockets 1.1.1.0 for a really long time. We recently migrated a main app to new servers which are running Windows Server 2012 and we're having problems. No code has changed. When we attempt a Tcp object Connect() with a Certificate assigned and the secure protocol set to Auto, we now get: System.InvalidOperationException: The token supplied to the function is invalid at f.Invoke(Delegate A_0, Object[] A_1) at Dart.PowerTCP.SslSockets.Tcp.Connect(String server, Int32 serverPort, String client, Int32 clientPortMin, Int32 clientPortMax) at Dart.PowerTCP.SslSockets.Tcp.Connect(String server, Int32 serverPort) In the System event log, this is logged: A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows SChannel error state is 252. Is this normal for Server 2012? I downloaded a trial of your new 4.4 version and it is totally different and will require a big re-write to conform to the new design. I have been unable to find an equivalent ConnectTimeout property in any of the TcpSocketOptions. If it was an easy port, we'd probably just pay to upgrade instead of looking to other options like WCF. |
| Nick B (Admin) From: Utica, NY USA Posts: 619 Member Since: 05/25/10 Extra Support Options Custom Application Development |
posted January 23, 2014 11:25 AM Hello, We don't perform testing of old versions of our components on new operating systems (Server 2012 was released in 2012, SSL Sockets 1.1.1.0 in 2008), so I can't say if this is normal or not for Server 2012. There were changes to Microsoft's security implementation in Windows 8/Server 2012 which may be causing these issues; have you tried specifying different values for the secure protocol instead of Auto? The connect timeout was not included in version 4.0 since it is not implemented in Microsoft's Socket class, but I have added your interest in this to the feature request TFS383. If you are interested in version 4.4, we can assist with porting your application, or rewrite it for you under custom development. If this is something you would be interested in, please contact sales@dart.com. ------ |
| cbenard From: USA Posts: 21 Member Since: 04/20/07 |
posted January 23, 2014 11:34 AM Just so I'm clear, how did you implement ConnectTimeout in 1.1.1.0 if it's not in Socket? Were you using IAsyncResult with a BeginConnect and AsyncWaitHandle.WaitOne()? Is this how you'd recommend us implementing it on top of your 4.4 library? |
| cbenard From: USA Posts: 21 Member Since: 04/20/07 |
posted January 23, 2014 1:10 PM Further update: I took your advice of: "Have you tried specifying different values for the secure protocol instead of Auto?" We were able to packet capture (WireShark) the negotiation between each of our partners and determine which ones were using TLS and which were using SSL v3. We set it explicitly on each partner (thankfully I'd already added that ability to the program), and the messages are now successful. I don't know what broke in Windows Server 2012 and DART PowerTCP SSL Sockets, but at least we can work around it without having to make any application changes. Could you still answer the part about the ConnectTimeout (my second post to this thread about how you implemented it)? |
| Jamie Powell (Admin) From: Rome, NY USA Posts: 448 Member Since: 03/13/07 Extra Support Options Custom Application Development |
posted January 24, 2014 4:22 PM Thank you for your reply. This functionality is not currently supported in the current version of PowerTCP Sockets for .NET, however it will be reviewed for inclusion in a future release. Please contact sales@dart.com for updates regarding the implementation of this feature. Thank you, Jamie |
| Reply | PowerTCP Sockets for .NET (Secure and Standard) Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|