From user-return-3136-archive-asf-public=cust-asf.ponee.io@guacamole.apache.org Wed Jan 24 13:57:57 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 47B96180630 for ; Wed, 24 Jan 2018 13:57:57 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 385B2160C3C; Wed, 24 Jan 2018 12:57:57 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7F5D0160C2E for ; Wed, 24 Jan 2018 13:57:56 +0100 (CET) Received: (qmail 49296 invoked by uid 500); 24 Jan 2018 12:57:50 -0000 Mailing-List: contact user-help@guacamole.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@guacamole.apache.org Delivered-To: mailing list user@guacamole.apache.org Received: (qmail 49286 invoked by uid 99); 24 Jan 2018 12:57:50 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jan 2018 12:57:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 1FB121A0BE6 for ; Wed, 24 Jan 2018 12:57:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.998 X-Spam-Level: X-Spam-Status: No, score=-0.998 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id X9nNRDP-P52o for ; Wed, 24 Jan 2018 12:57:49 +0000 (UTC) Received: from amcrelay3.faa.gov (amcrelay3.faa.gov [162.58.35.110]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 314D95F1B3 for ; Wed, 24 Jan 2018 12:57:48 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2GrAgAFgmha/1EEZxdeGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYMVLWZ0JwecYjGBUYkRjUmCfQolhRYChH5XFQEBAQEBAQEBAgN?= =?us-ascii?q?oKIJrS1kBAQEBAQEjAgxeAQEBBDo0FwQCAQgNBAQBARkGCQchERQDAQUIAQEEE?= =?us-ascii?q?wiIBIIRAxUFC6ZBAo4jIQKHHQ0KgnsBAQEBAQEBAwEBAQEBASKEToIVgz+DLoJ?= =?us-ascii?q?rRASBKDFiAoUuBYpXh2CBdY8dPZBaAYR9jEuHYo4fiQsCAg0CGoE8NSSBUCsKQ?= =?us-ascii?q?UxAgWoJhE54AQGLfIEPAYEWAQEB?= X-IronPort-AV: E=Sophos;i="5.46,407,1511848800"; d="scan'208";a="83286668" Received: from unknown (HELO 006-smtp-out.faa.gov) ([23.103.4.81]) by amcrelay3.faa.gov with ESMTP; 24 Jan 2018 06:57:40 -0600 Received: from SN1F00601MB032.006f.mgd2.msft.net (23.103.4.84) by SN1F00601MB029.006f.mgd2.msft.net (23.103.4.81) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.20.407.12; Wed, 24 Jan 2018 12:57:40 +0000 Received: from SN1F00601MB032.006f.mgd2.msft.net ([23.103.4.84]) by SN1F00601MB032.006f.mgd2.msft.net ([23.103.4.84]) with mapi id 15.20.0407.015; Wed, 24 Jan 2018 12:57:39 +0000 From: To: Subject: RE: Connection failures Thread-Topic: Connection failures Thread-Index: AdOTiUnCsNuKfHRLS767UhXaKbdwYQAAL9CAAAAxZcAAXxepAAACwU5w Date: Wed, 24 Jan 2018 12:57:39 +0000 Message-ID: References: <479bb1879bdd45798eefbc1cfe103868@SN1F00601MB032.006f.mgd2.msft.net> <1516793618688-0.post@n4.nabble.com> In-Reply-To: <1516793618688-0.post@n4.nabble.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [23.103.4.196] x-ms-publictraffictype: Email x-ms-traffictypediagnostic: SN1F00601MB029: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I just played around with my setup for an RDP connection we have, and what = you suggested didn't work. The RDP server is a Windows 2008 R2 server. I = truly believe that the issue is due to us making our machines FIPS complian= t, which is why SSH connections now fail with "SSH handshake failed". Howe= ver, we didn't make any changes at all to our Windows servers, so I would'v= e expected the RDP connections to work as they always had, which is not the= case. Also, someone else had mentioned that the problem was antivirus and to turn= that off. First of all, that's not the issue, as I get the connection fai= lures for both SSH and RDP when I use a browser on a Linux box. Secondly, = I can't turn off our antivirus as its controlled by our IT department and w= e don't have admin rights to be able to do that. I am assuming that Guacamole is using an SSH library that is NOT FIPS-140 c= ompliant? If so, are there updates that need to be installed to allow this= ? Even via a guacamole recompile? Thanks for the help! Harry -----Original Message----- From: ldap123user [mailto:kontokala7@gmail.com]=20 Sent: Wednesday, January 24, 2018 6:34 AM To: user@guacamole.apache.org Subject: RE: Connection failures I had same error over RDP. Problem is to set ignore certificates and use NL= A authentication (windows 2012 R2) This settings helped me connect with success: rdp 192.168.0.2 3389 test password nla true true -- Sent from: http://apache-guacamole-general-user-mailing-list.2363388.n4.nab= ble.com/