X2Go Bug report logs - #195
windows client ignores ssh port

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#195: windows client ignores ssh port
Reply-To: Matthias Kauer <software@matthiaskauer.com>, 195@bugs.x2go.org
Resent-From: Matthias Kauer <software@matthiaskauer.com>
Resent-To: x2go-dev@lists.berlios.de
Resent-CC: X2Go Developers <x2go-dev@lists.berlios.de>
X-Loop: owner@bugs.x2go.org
Resent-Date: Fri, 21 Jun 2013 16:18:02 +0000
Resent-Message-ID: <handler.195.B195.137183062724891@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 195
X-X2Go-PR-Package: x2goclient
X-X2Go-PR-Keywords: moreinfo
Received: via spool by 195-submit@bugs.x2go.org id=B195.137183062724891
          (code B ref 195); Fri, 21 Jun 2013 16:18:02 +0000
Received: (at 195) by bugs.x2go.org; 21 Jun 2013 16:03:47 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham
	version=3.3.2
X-Greylist: delayed 581 seconds by postgrey-1.34 at ymir; Fri, 21 Jun 2013 18:03:47 CEST
Received: from fra07-inx04.webhod.de (fra07-inx04.webhod.de [212.224.89.152])
	by ymir (Postfix) with ESMTPS id 36D4B3BDED;
	Fri, 21 Jun 2013 18:03:47 +0200 (CEST)
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
Received: from [192.168.1.109] (unknown [119.56.94.10])
	by fra07-inx04.webhod.de (Postfix) with ESMTPSA id 4297FD20689;
	Fri, 21 Jun 2013 17:54:11 +0200 (CEST)
Message-ID: <51C47701.5080209@matthiaskauer.com>
Date: Fri, 21 Jun 2013 23:53:37 +0800
From: Matthias Kauer <software@matthiaskauer.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
CC: 195@bugs.x2go.org, control@bugs.x2go.org
References: <517E6CF1.6080806@matthiaskauer.com> <20130621104059.20664yi8eoqgqh7f@mail.das-netzwerkteam.de>
In-Reply-To: <20130621104059.20664yi8eoqgqh7f@mail.das-netzwerkteam.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Gabriel,
I can't verify all your questions right now since I don't have access to 
this setup for a bit, but I'll try my best:

The VM is the server, I was essentially connecting from the host system 
to the guest system. I rerouted port 17022 in the advanced NAT settings 
(or port forwarding settings) of virtual box and I never actually 
changed the ssh port. [This setup worked with putty, but maybe I should 
verify if this is at the root of the problem]

About where I manipulate the port, I really think that was in the 
session profile and I probably never touched the global settings.
I'll try to verify that ASAP though.

Best,
Matthias

On 21/6/2013 4:40 PM, Mike Gabriel wrote:
> tag #195 moreinfo
> found #195 4.0.0.3
> thanks
>
> Hi Matthias,
>
> On Mo 29 Apr 2013 14:52:01 CEST Matthias Kauer wrote:
>
>> Package: X2Go Client
>> Version: 4.0.0.3 (Qt - 4.8.1)
>>
>> I want to use x2go over port 17022. For testing I therefore set
>> Virtualbox to forward 17022 -> 22 and entered 17022 as ssh port in the
>> x2goclient's config. After a while, a connection timeout window
>> appears detailing that 127.0.0.2:22 could not be reached. Having VBox
>> forward 22 -> 22 and entering 22 in x2goclient resolved this.
>>
>> Best,
>> Matthias
>>
>> I am using Win7 64bit Host, Vbox 4.2.12, Xubuntu 12.10 guest
>> matthias@matthias-VirtualBox:~$ uname -a
>> Linux matthias-VirtualBox 3.5.0-27-generic #46-Ubuntu SMP Mon Mar 25
>> 19:58:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>
> thanks for your bug report.
>
> Please give us some feedback on the questions below:
>
>    o do you manipulate the SSH port in the global X2Go Client configuration
>      (Windows Registry folder ,,settings'')?
>    o or do you manipulate the SSH port in the session profile?
>    o (I presume a yes for first of the two questions above)
>
> Neither am I getting clean the setup you have.
>
>    o is the VBox VM your X2Go Server?
>    o or your X2Go Client?
>
> I hope to get your problem fixed with the next X2Go Client release, so a
> quick response is appreciated.
>
> Mike
>
>

Send a report that this bug log contains spam.