Return-Path: Delivered-To: apmail-incubator-etch-user-archive@minotaur.apache.org Received: (qmail 32866 invoked from network); 14 Oct 2010 12:12:56 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 14 Oct 2010 12:12:56 -0000 Received: (qmail 88221 invoked by uid 500); 14 Oct 2010 12:12:56 -0000 Delivered-To: apmail-incubator-etch-user-archive@incubator.apache.org Received: (qmail 88171 invoked by uid 500); 14 Oct 2010 12:12:55 -0000 Mailing-List: contact etch-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: etch-user@incubator.apache.org Delivered-To: mailing list etch-user@incubator.apache.org Received: (qmail 88163 invoked by uid 99); 14 Oct 2010 12:12:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Oct 2010 12:12:55 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS,T_FRT_STOCK2 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of nasinha@cisco.com designates 171.71.176.117 as permitted sender) Received: from [171.71.176.117] (HELO sj-iport-6.cisco.com) (171.71.176.117) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Oct 2010 12:12:46 +0000 Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlUFADKQtkxAaMHG/2dsb2JhbACBRJ9dcZ8GnFyFSASEUIh6 X-IronPort-AV: E=Sophos;i="4.57,330,1283731200"; d="scan'208,217";a="603904053" Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-6.cisco.com with ESMTP; 14 Oct 2010 12:12:25 +0000 Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9ECBVk3001096 for ; Thu, 14 Oct 2010 12:12:24 GMT Received: from xmb-bgl-414.cisco.com ([72.163.129.210]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 14 Oct 2010 17:41:49 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB6B98.FADC2CE4" Subject: Etch TLS connection issue with windows 7 and windows 2008 Date: Thu, 14 Oct 2010 17:41:48 +0530 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Etch TLS connection issue with windows 7 and windows 2008 Thread-Index: ActrmPnc8wbN5hzrTTiEPdv3V0VtPw== From: "Nabhonil Sinha -X (nasinha - Infosys at Cisco)" To: X-OriginalArrivalTime: 14 Oct 2010 12:11:49.0914 (UTC) FILETIME=[FAEBA7A0:01CB6B98] This is a multi-part message in MIME format. ------_=_NextPart_001_01CB6B98.FADC2CE4 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 I am trying a client - server application where my client is in windows 7 and my server is in windows 2008 server. I am using the etch version 1.0.1 and I faced a problem with the TLS connection. It was giving me the error =20 System.Net.Sockets.SocketException: An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call =20 After looking at one of the posts I have changed the SocketOptionLevel.Tcp to SocketOptionLevel.Socket . This solved the earlier issue, and now I am facing another error where it is closing the TLS connection abruptly. It is giving the following error. =20 System.IO.IOException: Authentication failed because the remote party has closed the transport stream. at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolTo ken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Net.Security.SslStream.AuthenticateAsClient(String targetHost, X509CertificateCollection clientCertificates, SslProtocols enabledSslProtocols, Boolean checkCertificateRevocation) at Etch.Util.TlsConnection.SetUpSocket() at Etch.Util.Connection`1.Run0(Boolean first) =20 Any ideas what could have gone wrong. After changing the SocketOptionLevel to socket the TCP connections are working fine but facing issues with TLS connection.=20 =20 Thanks in Advance =20 ---------------------------- Regards,=20 Nabhonil Sinha Infosys - Cisco OSDC =20 IP: 8-229-7031 Direct: 91-80-39802132 Mobile: 91-95388 91254 ---------------------------- =20 ------_=_NextPart_001_01CB6B98.FADC2CE4 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

I am trying a client – server application = where my client is in windows 7 and my server is in windows 2008 server. I am = using the etch version 1.0.1 and I faced a problem with the TLS connection. It was = giving me the error

 

System.Net.Sockets.SocketException: An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call

 

After looking at one of the posts I have changed = the SocketOptionLevel.Tcp to SocketOptionLevel.Socket . This solved the earlier issue, and now I am facing another = error where it is closing the TLS connection abruptly. It is giving the following = error.

 

System.IO.IOException: Authentication failed because the remote party has closed the transport = stream.

   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 = readBytes, AsyncProtocolRequest asyncRequest)

   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, = AsyncProtocolRequest asyncRequest)

   at = System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolTok= en message, AsyncProtocolRequest asyncRequest)

   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 = count, AsyncProtocolRequest asyncRequest)

   at System.Net.Security.SslState.ForceAuthentication(Boolean = receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)

   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult = lazyResult)

   at System.Net.Security.SslStream.AuthenticateAsClient(String targetHost, = X509CertificateCollection clientCertificates, SslProtocols enabledSslProtocols, Boolean checkCertificateRevocation)

   at Etch.Util.TlsConnection.SetUpSocket()

   at Etch.Util.Connection`1.Run0(Boolean first)

 

Any ideas what could have gone wrong. After = changing the SocketOptionLevel to socket the TCP connections are working fine but = facing issues with TLS connection.

 

Thanks in Advance

 

----------------------------
Regards,
Nabhonil Sinha
Infosys - Cisco OSDC

 

IP: 8-229-7031
Direct: 91-80-39802132
Mobile: 91-95388 91254

----------------------------

 

------_=_NextPart_001_01CB6B98.FADC2CE4--