From owner-freebsd-questions@freebsd.org Thu May 10 01:01:33 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93B44FD0A71 for ; Thu, 10 May 2018 01:01:33 +0000 (UTC) (envelope-from bferrell@baywinds.org) Received: from baywinds.org (50-196-187-248-static.hfc.comcastbusiness.net [50.196.187.248]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "baywinds.org", Issuer "rr-v" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 230F58143B for ; Thu, 10 May 2018 01:01:32 +0000 (UTC) (envelope-from bferrell@baywinds.org) Received: from [192.0.2.130] (rr-iii [192.0.2.130]) by baywinds.org (8.14.4/8.14.4) with ESMTP id w4A11To3008992 for ; Wed, 9 May 2018 18:01:30 -0700 Subject: Re: ssh -X remote does not work due to problem with xauth To: freebsd-questions@freebsd.org References: <20180509104700.GA3259@c720-r314251> <20180509180935.GA1064@c720-r314251> <44d0y4iplm.fsf@lowell-desk.lan> <20180509203049.GA2230@c720-r314251> From: Bruce Ferrell Message-ID: <56ee503a-222c-c94b-d5f5-2d933730e64c@baywinds.org> Date: Wed, 9 May 2018 18:01:29 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180509203049.GA2230@c720-r314251> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2018 01:01:33 -0000 On 05/09/2018 01:30 PM, Matthias Apitz wrote: > El día miércoles, mayo 09, 2018 a las 03:41:25p. m. -0400, Lowell Gilbert escribió: > >>> X11Forwarding is definitely enabled on the remote server. Other users in >>> my company network who are coming from Ubuntu workstations to the same >>> server do not face this problem. >> Have you tried increasing the verbosity on the ssh session? >> And if possible, on the sshd at the other end? > Have you read my original post? I used -vv as options for the > SSH client site and in addition watch the client with truss(1). > > matthias Just out of curiosity, are you able to increase logging on the server? The error would tend to imply the client is making the request and being rejected at the server. By design, the client can't necessarily tell why... But the server knows.