Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 77316200D3A for ; Wed, 15 Nov 2017 23:01:01 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 755F7160BF4; Wed, 15 Nov 2017 22:01:01 +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 BACF4160BE4 for ; Wed, 15 Nov 2017 23:01:00 +0100 (CET) Received: (qmail 57218 invoked by uid 500); 15 Nov 2017 22:00:59 -0000 Mailing-List: contact user-help@guacamole.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@guacamole.incubator.apache.org Delivered-To: mailing list user@guacamole.incubator.apache.org Received: (qmail 57208 invoked by uid 99); 15 Nov 2017 22:00:59 -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, 15 Nov 2017 22:00:59 +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 2F5B31A0A8D for ; Wed, 15 Nov 2017 22:00:59 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.312 X-Spam-Level: * X-Spam-Status: No, score=1.312 tagged_above=-999 required=6.31 tests=[SPF_HELO_PASS=-0.001, 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 Kp_EKrQgC3ce for ; Wed, 15 Nov 2017 22:00:57 +0000 (UTC) Received: from n4.nabble.com (n4.nabble.com [162.253.133.72]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id C233C60D33 for ; Wed, 15 Nov 2017 22:00:56 +0000 (UTC) Received: from mben.nabble.com (localhost [127.0.0.1]) by n4.nabble.com (Postfix) with ESMTP id 1268F1645DC47 for ; Wed, 15 Nov 2017 15:00:56 -0700 (MST) Date: Wed, 15 Nov 2017 15:00:56 -0700 (MST) From: glarkin53 To: user@guacamole.incubator.apache.org Message-ID: <1510783256073-0.post@n4.nabble.com> In-Reply-To: References: <1510085970139-0.post@n4.nabble.com> Subject: Re: Unreachable RDP desktop after renaming computer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Wed, 15 Nov 2017 22:01:01 -0000 vnick wrote > On Tue, Nov 7, 2017 at 3:19 PM, glarkin53 < > greg.larkin@ > > wrote: > >> Hi, >> >> I'm working on a project to provide access to Windows desktops hosted on >> Amazon AWS. We spin up a number of Windows EC2 instances (Windows 2012 R2 >> servers) and then connect to them with Guacamole. >> >> Upon the first connection to a machine, it has the Amazon auto-generated >> hostname, such as "win-oekuqjop15l.us-west-2.compute.internal". Our >> process >> requires the hostname to be changed and the machine rebooted, so we may >> issue the following commands in a Powershell window: >> >> Rename-Computer glarkin >> Restart-Computer >> >> After the machine restarts, Guacamole is unable to connect to the >> machine. >> The dialog box reads "The remote desktop server is currently >> unreachable." >> The machine is still up and running, and I can connect to it with a >> desktop >> RDP client from my laptop, so I think there is a problem with Guacamole >> somewhere. >> > > Greg, > I suspect that you're running into a DNS caching issue on the system > hosting Guacamole. Depending on what distribution you're running, there > could be one of several daemons running that caches DNS information. > sssd, > nscd, and nslcd are the ones I can think of off the top of my head. Also, > depending on which DNS servers you're pointing at with your laptop vs. > Guacamole, it could be something on one of those systems, too. > > -Nick Hi Nick, Thanks very much for the reply. Would DNS caching be an issue if I'm using IP addresses only to create the connections in Guacamole? I should have clarified that I'm only using Amazon EC2 internal network IP addresses for the hostname in the Guacamole connections. Those IPs don't change, as far as I can tell, but I'll double-check that. I'm pretty sure they would if I powered the Windows machines completely off, but I'm only issuing a reboot. The other angle I'm pursuing is to start the Windows machines with a pre-selected hostname instead of the default. That way, our users would not have to rename the machines and reboot them. Thank you, Greg -- Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/