Hi folks,
i was hoping to not have to abuse the list but i'm having problems to get things working:
X2Go Client V. 3.01-2
Trying to start an xterm on the x2go-server i got the following:
NXPROXY - Version 3.0.0
Copyright (C) 2001, 2007 NoMachine. See http://www.nomachine.com/ for more information.
Info: Proxy running in client mode with pid '3820'. Session: Starting session at 'Wed Sep 8 20:26:14 2010'. Info: Connecting to remote host 'localhost:30007'. Info: Connection to remote proxy 'localhost:30007' established. Error: The remote NX proxy closed the connection. Error: Failure negotiating the session in stage '7'. Error: Wrong version or invalid session authentication cookie.
/var/log/auth.log is here:
http://nopaste.info/ebef4d50f6_nl.html
Did i miss something? I expected a straightforward installation according to the documentation.
Help is greatly appreciated
Stefan
-- Stefan Bauer ----------------------------------------- PGP: E80A 50D5 2D46 341C A887 F05D 5C81 5858 DCEF 8C34 -------- plzk.de - Linux - because it works ----------
On Wed, 2010-09-08 at 20:43 +0200, Stefan Bauer wrote:
Hi folks,
i was hoping to not have to abuse the list but i'm having problems to get things working:
X2Go Client V. 3.01-2
Trying to start an xterm on the x2go-server i got the following:
NXPROXY - Version 3.0.0
Copyright (C) 2001, 2007 NoMachine. See http://www.nomachine.com/ for more information.
Info: Proxy running in client mode with pid '3820'. Session: Starting session at 'Wed Sep 8 20:26:14 2010'. Info: Connecting to remote host 'localhost:30007'. Info: Connection to remote proxy 'localhost:30007' established. Error: The remote NX proxy closed the connection. Error: Failure negotiating the session in stage '7'. Error: Wrong version or invalid session authentication cookie.
/var/log/auth.log is here:
http://nopaste.info/ebef4d50f6_nl.html
Did i miss something? I expected a straightforward installation according to the documentation.
Help is greatly appreciated
Stefan
Are you trying to connect to an X2GoServer running on the same computer as the X2GoClient? That does not work - John
Am 08.09.2010 21:28, John A. Sullivan III schrieb:
Are you trying to connect to an X2GoServer running on the same computer as the X2GoClient? That does not work - John
It's a virtual machine in my lab. Precicely it's the same physical machine, but i'm accessing the virtual machine over TCP namely by a different ip-address than my machine.
-- Stefan Bauer ----------------------------------------- PGP: E80A 50D5 2D46 341C A887 F05D 5C81 5858 DCEF 8C34 -------- plzk.de - Linux - because it works ----------
On Wed, 2010-09-08 at 21:31 +0200, Stefan Bauer wrote:
Am 08.09.2010 21:28, John A. Sullivan III schrieb:
Are you trying to connect to an X2GoServer running on the same computer as the X2GoClient? That does not work - John
It's a virtual machine in my lab. Precicely it's the same physical machine, but i'm accessing the virtual machine over TCP namely by a different ip-address than my machine.
Hmmm . . . I'm not an expert on this part of X2Go but these lines from your log through me off:
Info: Connecting to remote host 'localhost:30007'. Info: Connection to remote proxy 'localhost:30007' established.
I wonder why it is connecting to localhost? - John
Am 08.09.2010 21:48, John A. Sullivan III schrieb:
Hmmm . . . I'm not an expert on this part of X2Go but these lines from your log through me off:
Info: Connecting to remote host 'localhost:30007'. Info: Connection to remote proxy 'localhost:30007' established.
Isn't the connection locally?
CLIENT | TCP/IP (192.168.0.16<->192.168.0.57) | SSH (X2go-Server) | local Socket (localhost<->localhost:30007) | NXPROXY
That's the picture i have in mind.
Stefan
-- Stefan Bauer ----------------------------------------- PGP: E80A 50D5 2D46 341C A887 F05D 5C81 5858 DCEF 8C34 -------- plzk.de - Linux - because it works ----------
If you are connecting from the guest to the server running on the host, you should be using the host's local ip address and not localhost.
You should also be using bridged networking for you virtual environment. I don't see an easy way to do this using a nat setup
On Wed, 2010-09-08 at 21:31 +0200, Stefan Bauer wrote:
Am 08.09.2010 21:28, John A. Sullivan III schrieb:
Are you trying to connect to an X2GoServer running on the same computer as the X2GoClient? That does not work - John
It's a virtual machine in my lab. Precicely it's the same physical machine, but i'm accessing the virtual machine over TCP namely by a different ip-address than my machine.
Hmmm . . . I'm not an expert on this part of X2Go but these lines from your log through me off:
Info: Connecting to remote host 'localhost:30007'. Info: Connection to remote proxy 'localhost:30007' established.
I wonder why it is connecting to localhost? - John
X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Am 08.09.2010 21:54, M0E Lnx schrieb:
If you are connecting from the guest to the server running on the host, you should be using the host's local ip address and not localhost.
I havent specified anywhere localhost! I'm accessing the x2go-server only by it's public ip-address - namely 192.168.0.57.
Cheers
Stefan Bauer ----------------------------------------- PGP: E80A 50D5 2D46 341C A887 F05D 5C81 5858 DCEF 8C34 -------- plzk.de - Linux - because it works ----------
Someone quoted your log earlier
[quote] Hmmm . . . I'm not an expert on this part of X2Go but these lines from your log through me off:
Info: Connecting to remote host 'localhost:30007'. Info: Connection to remote proxy 'localhost:30007' established.
I wonder why it is connecting to localhost? - John [/quote]
At any rate, what needs to happen is that both OS's need to be able to communicate with each other via ssh. say for instance, your server is running on the host OS (192.168.0.57). And your client is a guest OS in the same physical machine but with bridged networking and get it's IP of 192.168.0.58.
In this setup, when connecting from the client app, you would connect to 192.168.0.57, not localhost.
That's what I meant in my comment.
On Wed, 2010-09-08 at 21:57 +0200, Stefan Bauer wrote:
Am 08.09.2010 21:54, M0E Lnx schrieb:
If you are connecting from the guest to the server running on the host, you should be using the host's local ip address and not localhost.
I havent specified anywhere localhost! I'm accessing the x2go-server only by it's public ip-address - namely 192.168.0.57.
Cheers Hmm . . . could it be it is reverse resolving it from the hosts file? If not, what happens if you add the following line to /etc/ssh/sshd_config and restart the ssh daemon:
X11UseLocalhost no
On Wed, Sep 8, 2010 at 3:09 PM, John A. Sullivan III <jsullivan@opensourcedevel.com> wrote:
On Wed, 2010-09-08 at 21:57 +0200, Stefan Bauer wrote:
Am 08.09.2010 21:54, M0E Lnx schrieb:
If you are connecting from the guest to the server running on the host, you should be using the host's local ip address and not localhost.
I havent specified anywhere localhost! I'm accessing the x2go-server only by it's public ip-address - namely 192.168.0.57.
Cheers Hmm . . . could it be it is reverse resolving it from the hosts file? If not, what happens if you add the following line to /etc/ssh/sshd_config and restart the ssh daemon:
X11UseLocalhost no
X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
The X Forwarding setting in the sshd_config should now affect the connectivity with x2go AFAIK. what you need to do is verify that you can ssh the host from within the guest os. Take note of which port the server is listening on (for SSH) as this could definitely affect the connectivity.
Am 08.09.2010 22:13, M0E Lnx schrieb:
On Wed, Sep 8, 2010 at 3:09 PM, John A. Sullivan III <jsullivan@opensourcedevel.com> wrote:
On Wed, 2010-09-08 at 21:57 +0200, Stefan Bauer wrote:
Am 08.09.2010 21:54, M0E Lnx schrieb:
If you are connecting from the guest to the server running on the host, you should be using the host's local ip address and not localhost. I havent specified anywhere localhost! I'm accessing the x2go-server only by it's public ip-address - namely 192.168.0.57.
Cheers Hmm . . . could it be it is reverse resolving it from the hosts file? If not, what happens if you add the following line to /etc/ssh/sshd_config and restart the ssh daemon:
X11UseLocalhost no
X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
The X Forwarding setting in the sshd_config should now affect the connectivity with x2go AFAIK. what you need to do is verify that you can ssh the host from within the guest os. Take note of which port the server is listening on (for SSH) as this could definitely affect the connectivity.
As the server logs my ssh-attempts/logins - everything between client -> server is working. nxproxy is the one who is not able to connect locally to a port and continue it's work.
I just have no idea what's going on under the x2go hood.
Stefan
-- Stefan Bauer ----------------------------------------- PGP: E80A 50D5 2D46 341C A887 F05D 5C81 5858 DCEF 8C34 -------- plzk.de - Linux - because it works ----------
Am 08.09.2010 22:09, John A. Sullivan III schrieb:
Hmm . . . could it be it is reverse resolving it from the hosts file? If not, what happens if you add the following line to /etc/ssh/sshd_config and restart the ssh daemon:
X11UseLocalhost no
No! Again, i successfully connect with the x2go-client to the server. Here is all the work done for the client, more or less. Now there is some magic for x2goserver to either start a local application or a remote one and tunnel&compress the data back through the ssh-tunnel to the client where it gets displayed.
In my case, for unknown reasons, x2goserver is missing a socket to connect to.
Stefan
Stefan Bauer ----------------------------------------- PGP: E80A 50D5 2D46 341C A887 F05D 5C81 5858 DCEF 8C34 -------- plzk.de - Linux - because it works ----------
On Wed, 2010-09-08 at 22:18 +0200, Stefan Bauer wrote:
Am 08.09.2010 22:09, John A. Sullivan III schrieb:
Hmm . . . could it be it is reverse resolving it from the hosts file? If not, what happens if you add the following line to /etc/ssh/sshd_config and restart the ssh daemon:
X11UseLocalhost no
No! Again, i successfully connect with the x2go-client to the server. Here is all the work done for the client, more or less. Now there is some magic for x2goserver to either start a local application or a remote one and tunnel&compress the data back through the ssh-tunnel to the client where it gets displayed.
In my case, for unknown reasons, x2goserver is missing a socket to connect to.
Stefan May I ask what virtualization product you are using? - John
Am 08.09.2010 22:53, John A. Sullivan III schrieb:
On Wed, 2010-09-08 at 22:18 +0200, Stefan Bauer wrote:
Hmm . . . could it be it is reverse resolving it from the hosts file? If not, what happens if you add the following line to /etc/ssh/sshd_config and restart the ssh daemon:
X11UseLocalhost no No! Again, i successfully connect with the x2go-client to the server. Here is all the work done for the client, more or less. Now
Am 08.09.2010 22:09, John A. Sullivan III schrieb: there is some magic for x2goserver to either start a local application or a remote one and tunnel&compress the data back through the ssh-tunnel to the client where it gets displayed.
In my case, for unknown reasons, x2goserver is missing a socket to connect to.
Stefan May I ask what virtualization product you are using? - John
It's Virtualbox from SUN / Oracle. I'm going to rebuild this setup in my lab if i find some spare time on real hardware. It would just have been nice to see it working on a first glance.
thanks
stefan
-- Stefan Bauer ----------------------------------------- PGP: E80A 50D5 2D46 341C A887 F05D 5C81 5858 DCEF 8C34 -------- plzk.de - Linux - because it works ----------
-
John A. Sullivan III -
M0E Lnx -
Stefan Bauer