Hi,

really great. The proxy feature seems to work without any special configuration on the x2go server. Though, what did not work is the tunneling of rdp (rdesktop) through SSH. When I choose "direct rdp connection" then the connection works. There should be a corresponding setting where we could also tunnel rdp through ssh when selecting ssh proxy like the standard connections I have tested now.

Cheers, Matt

Am 13.01.2014 19:30, schrieb Buddy Butterfly:

Hi,

this is great news. Exactly what I wanted to know. Are there special settings when using the SSH proxy from x2go client on the x2go server or does the client run the SSH forwarding on demand?

Cheers, Matt

Am 13.01.2014 02:20, schrieb Michael DePaulo:

...

I think the x2go proxy can do that. Mike Gabriel and others could give you a definite answer.

Stefan Baur's instructions for using SSH forwarding via the command line will work. Just note that in the SSH server settings, you will need to enable TCP forwarding if it is not enabled by default. The settings are usually in /etc/ssh/sshd_config .

I think that you can also use x2go client's built in feature to use a "proxy server". I think this feature is just SSH forwarding. Ultimately, which way of doing SSH forwarding is your preference. To use the x2go client's built in feature: ultimately want to connect to. The host should be the hostname or the IP

1. In x2go client, define a session for each x2go server host your

address of the x2go server host 2. Under the preferences for each session, enable "Use Proxy server for SSH connection". Then enter the vpn client box's hostname or IP address as the "host" of the proxy server. The "type" of proxy server should set to "SSH".

And of course, you can use x2go to connect to this headless box. I recommend you install the full desktop environment you intend to use, but disable X from starting automatically. How to do this varies from distro to distro. For example, on Red Hat and Fedora, you would make the default runlevel 3 instead of 5. On Ubuntu, you would disable the service / upstart job "lighdm" (or "gdm" if using GNOME Ubuntu, or "kdm" if using kubuntu, and so on.)

-Mike

On Sun, Jan 12, 2014 at 5:37 PM, Buddy Butterfly <buddy.butterfly@web.de <mailto:buddy.butterfly@web.de>> wrote:

Hi,

it is a VPN client with multiple VPN clients.
Kind of a VPN concentrator. But this is not
important. It is a headles system.
I am looking for the best solution
to use other systems via this box with x2go
but also use the box itself with x2go.

So I thought I could to from client computers:

1. Have one session with x2go to the box.
2. Create ssh forwardings on the box.
3. Connect with other x2go sessions via the box
   (ssh forward) to the systems behind the box.

What I do not know is, if x2go does have some
kind of proxy server. Meaning that I could connect
to the box and would have beeing presented a list
of hosts I could connect further via x2go.

Thanks a lot,
Matt


Am 12.01.2014 21:21, schrieb Michael DePaulo:

...

On Jan 12, 2014 12:57 PM, "Buddy Butterfly"
<buddy.butterfly@web.de
<mailto:buddy.butterfly@web.de>> wrote:
>
>
> Hi,
>
> sry for this dumb question but I am kind of confused.
> Would be happy if someone would bring me back on track ;-)
>
> Cheers,
> Matt
>
>
> Am 09.01.2014 16:22, schrieb Buddy Butterfly:
> >
> > Hi,
> >
> > I have a small box with linux on it as VPN box.
> > This box is headless. So it will be accessed from another
computer in
> > the lan. But this box will be used to access the company systems.
> > So the question is, what would be the best solution?

I don't follow you here.
Is this box a VPN server or a VPN client?

> >
> > 1. x2go to the box and x2go from there to the systems?
> >
> > 2. Install a proxy or the like (do not know if this exists) on
the box
> >    and connect from 1 x2go client routed via the box?
> >    Is probably an ssh forward enough?
> >
> > Thanks and cheers,
> > Matt
> >
>
>
> _______________________________________________
> X2Go-User mailing list
> X2Go-User@lists.berlios.de
<mailto:X2Go-User@lists.berlios.de>
> https://lists.berlios.de/mailman/listinfo/x2go-user

Am 14.01.2014 03:22, schrieb Michael DePaulo:

HI Matt,

I am glad to hear that much worked for you.

I am not sure what you mean by "direct rdp connection." On the windows x2goclient 4.0.1.2, in the "Session type" list I see "Connect to Windows terminal server." Also, I don't know how a "direct" rdp connection would work unless you launched one from an x2go session running on the vpn client.

He's talking about the checkbox that appears once you select "Connect to Windows terminal server". I've seen it myself, hough it might have been on an x2goclient pulled from heuler.

I'm guessing that checking this box turns x2goclient into yet another RDP client where you don't need an X2Go server to connect to.

-Stefan

Am 14.01.2014 03:31, schrieb Stefan Baur:

Am 14.01.2014 03:22, schrieb Michael DePaulo:

...

HI Matt,

I am glad to hear that much worked for you.

I am not sure what you mean by "direct rdp connection." On the windows x2goclient 4.0.1.2, in the "Session type" list I see "Connect to Windows terminal server." Also, I don't know how a "direct" rdp connection would work unless you launched one from an x2go session running on the vpn client.

He's talking about the checkbox that appears once you select "Connect to Windows terminal server". I've seen it myself, hough it might have been on an x2goclient pulled from heuler.

I'm guessing that checking this box turns x2goclient into yet another RDP client where you don't need an X2Go server to connect to.

-Stefan

Hi,

yes, it is exactly this. And it works perfect. It calls rdesktop. It just would be very nice if there would be the same funktionality when going via a SSH proxy such that the rdp session is routed through SSH.

Cheers, Matt