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: Mon, 24 Jun 2013 11:18:02 +0000
Resent-Message-ID: <handler.195.B195.13720719492168@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.13720719492168
          (code B ref 195); Mon, 24 Jun 2013 11:18:02 +0000
Received: (at 195) by bugs.x2go.org; 24 Jun 2013 11:05:49 +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
Received: from fra07-inx04.webhod.de (fra07-inx04.webhod.de [212.224.89.152])
	by ymir (Postfix) with ESMTPS id 085665DB21;
	Mon, 24 Jun 2013 13:05:48 +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 [10.25.191.134] (nusnet-22-191.dynip.nus.edu.sg [137.132.22.191])
	by fra07-inx04.webhod.de (Postfix) with ESMTPSA id 177C9D20677;
	Mon, 24 Jun 2013 13:05:54 +0200 (CEST)
Message-ID: <51C827D6.3040809@matthiaskauer.com>
Date: Mon, 24 Jun 2013 19:04:54 +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

Alright,
I reverified this today.

So I go to Port Management in Vbox and select 17022 -> 22. I connect to 
ssh via port 17022 and putty successfully connects for verification that 
this works. I then start up x2go-client and enter (under session 
management -> session preferences) host: 127.0.0.2, port: 17022, session 
type:XFCE.
I then connect, enter my pw and wait.
I get an error window saying "Timeout connecting to 127.0.0.2" with 
title "Can not connect to 127.0.0.2:22" (wrong port here!)

I then change the port forward in Vbox and in x2go-client to 22 and now 
I can connect.

So again: VBox is representing the server here and I am manipulating the 
session profile, I am not sure where those global preferences that you 
are talking about are.

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.