-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi, this is a forwarded message from Peter Brodsky,
partially abridged and adapted so it makes sense to publish on the list. (He has stated that he's okay with it being made public, in message http://lists.x2go.org/pipermail/x2go-user/2015-January/002798.html).
Expect my reply in a few minutes.
-Stefan
-------- Weitergeleitete Nachricht -------- Betreff: X2Go on submarine control system Datum: Fri, 09 Jan 2015 15:27:02 -0800 Von: Peter Brodsky <brodsky@apl.washington.edu> An: Stefan Baur <X2Go-ML-1@baur-itcs.de> [...]
Looking ahead: The operational setup is the control system running on the Mint machine with a Windows box displaying sonar and video data. I want to put the display for the former on the latter; thus X2Go. I've got a GB switch between the 2 machines.
Now: My user account on the Linux side has no password (before you have a heart attack about security, remember this is a completely isolated network). I boot up and the desktop for that account simply appears. And brings up the control display panel with it. The sub pilot doesn't want to mess around with logging in, etc.
Given that - is there a particular order to which I should fire up the X2Go client vs. booting up the linux server?
AND - if I also have a monitor (& keyboard & mouse) on the linux server
OK; any suggestions helpful.
Regards,
PS: Years ago I used a commercial product called Exceed, from a Canadian company called Hummingbird. Is X2GO something like that? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUs/9GAAoJEG7d9BjNvlEZrjsH/iM140eYpWBuE2+H8DtwIe4s fabFx+tNPEUFwnsMg0xCCkMMKML9mPhM+AxnMxm5pzt5bxJx5EP56BNAsa1ItUTd UcqnjqUOY4t7b4+2J/VU1j8A2GcvryQZ5+zLFVr40xdGnvYonpiuyfY2AtJDVu0g JvZ9d4XwQXHBp5Cx3k+kMb6QCKkrOU0R8vc4kPBcOMWVIoorSj1wRKeIgrIpsA/B xC/m9UL+im/aRv+/xI75tgR6emevS+5b2F1IJ6Fv9sftoXQ+Mkfbmh3cqUvhmJU/ n8jf81SpHzEt1Pf1JAyNQ5YPHIDwH9TvEqyi1++1oU0qGTm1KGCihDXIjlBwGtI= =qoO8 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 12.01.2015 um 18:07 schrieb Peter Brodsky <brodsky@apl.washington.edu>:
X2Go will not work with no authentication at all. However, you can use a SSH Public/Private Key pair to authenticate, and assign no password to the private key. That way, you can automate the login and make things work with a simple double-click on the icon.
Given that - is there a particular order to which I should fire up the X2Go client vs. booting up the linux server?
The server should be up and running first. You can test that with a batch script in which you do nc -z ip.of.ser.ver 22 (assuming you're using Port 22 for ssh/X2Go, as usual) nc is available for Windows just as well as for Linux. the -z tells it to connect to the given IP and port, and quit immediately. The error code of nc can then be used to determine whether the connection was successful. Whil unsuccessful, make the script wait a few seconds (Microsoft's recommended way to make a machine wait 1 second is to send a single ping to 127.0.0.1, I kid you not), then try again. Once successful, continue in the script and launch x2goclient. You will be happy to hear that with x2goclient, it is possible to specify a command/session to be run automatically at startup. You should check out the various command line arguments by running x2goclient.exe in a cmd.exe window and specifying "--help" as the parameter. I'm pretty sure there are a few parameters that you will want to try out.
If you don't want to go down the batch route, I could write a little AutoIt script for you that provides a GUI wrapper for a small fee (maybe 65-75 USD - and the source would be public under GPL).
You have to differentiate here. Windows' RDP client mstsc.exe is a tool that can be used for two things.
You can use it to connect to another client computer runnung a client version of Windows, in which case it will lock the local display of the remote machine, as you only paid for a single-seat license.
You can use it to connect to a Windows Terminal Server, which can run multiple GUI Sessions of various users simultaneously, that do not interfere with the local display of that server, as the Windows Terminal Server licensing model is designed for multi-seat use, even concurrent, independent sessions by the same user.
X2Go is technically more comparable to 2), only that you don't have to buy licenses, as we're strictly GPL.
(IIRC, it is *possible* to mirror/take over the local display session with X2Go, too, but this is not the default, and judging from how you phrased your question, I take it this also is not what you want.)
PS: Years ago I used a commercial product called Exceed, from a Canadian company called Hummingbird. Is X2GO something like that?
My last encounter with Hummingbird also dates back a few years (ca. 2009). At my former employer, we mostly used text-based mainframe access
X2Go adds compression and efficiency (roundtrip elimination) to the networking layer of X. Though with merely two computers on a Gigabit link, you won't really notice that. I'm surprised you're even using a switch, you could probably just hook them up directly, Gigabit cards do Auto-MDI/MDI-X, so you don't need a special crossover cable - getting the switch "out of the loop" would reduce complexity (eliminating a component that could possibly fail in the worst possible moment), which I think is something you will prefer in a man-rated submarine.
Also, we basically offer the entire ssh login/X-forwarding/tunneling of sound, file and printer sharing stuff in one nice GUI client. With the Hummingbird Exceed and all comparable solutions I know, you had to do all those steps manually, like, open a command prompt window to ssh into the server, start your local X server, run the remote application in the ssh session, realize you forgot to specify -X when making the connection, log out and in again, ... plus it was sluggish as hell given the network bandwidth we had back then (16 MBit on Token Ring and 100MBit on Ethernet when at the main site, 128kBit - 2MBit from a branch office).
Of course, there's way more to X2Go - check out http://wiki.x2go.org/doku.php/doc:newtox2go for an introdution - but these should be the key points relevant for your use case.
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUtACIAAoJEG7d9BjNvlEZcRAH/igXrjrB0maKopOoqHYR2l+u pM6gGlAdbvZZ8sRgZebdGCaeGLTD081CoYP1urmj7MssPTBphWFyb2OLirKHCzA0 uw8YjxSL46ezWDPnyfSfn/hyslrSvsOfuvjN0cqh1mZLO2FAqUPMZRlIXl67s3xT 6BbeB3G04pjAkFCJdugwX8UM/BbY6qfp0wa5eaakx1PFPvHzrCeIH7vVjOK/8bho pFu/+RDoZSE0CAnIh2Dng885D7xi9lY7VzkXWesRptcaYfCokGWI8zYLOl8LlEG8 ZOrKBPEwFX1tXspHGSxbTg4Q2ejwXpmgahQHmpc8ADU3NPhtLPvQOTla03d7db8= =SBkz -----END PGP SIGNATURE-----
OK, indeed it will not work without authentication.
Would like to try the public/private key route. I've done this for ssh
agents between linux machines, using ssh-keygen to obtain the keys.
Not clear how to do so w/X2GO client running under Windows. Can you
provide some instructions?
Thanks,
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 12.01.2015 um 21:00 schrieb Peter Brodsky:
If you have access to a Linux machine, just run ssh-keygen there with the usual parameters, copy the private key file over to the Windows machine, and specify it in the session settings (there's a field where you can specify the path to an RSA/DSA key). On the Linux box, add the public key to the authorized_keys file of the user account you're trying to log in as, and you should be all set.
If you want to create your key pair on Windows, you will need to use either ssh-keygen from a cygwin install, or PuttyGen.exe from the PuTTY tool suite - for the latter, you will need to use the "export" function of PuttyGen's GUI to save the private key, as PuTTY's own *.ppk key storage files are incompatible with standard ssh.
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUtDDkAAoJEG7d9BjNvlEZqokH/j7m83jsuyAT+QNoywdMEy79 Ai1HH8dtC1G4pOtw1cwUerEAcGUKRZUqOn/8Fy4BMkwBZwXfvl4AU3U+GezkBEsE JraCO54ETz3LukZjNmCLO7GmU7Ql57/Dyd42CzE6wNojzD3/LwTgSZ39cC0LqGtc gghKNgSsR2A9YasKn/S2r4gfrj5nUJC3avo1fd4HLNEUunaSRykmXUXmL9gi+6oQ qjRCL/Rf2Y9EqGj5++cW1KhUG/NQPQ9pHcfvpfq/1W3Ty8lO60z7YIQ9uiHaf5qr 3wRY7ItGG1gwLHd4czKHBJ7O7cnN1IJg7UI2GMNVNcqgawgdeOgYWV43SCytFMI= =aLQz -----END PGP SIGNATURE-----
No joy yet.
I generated keys on the linux side:
Then tried connecting - can't do it (tries quite a while, then times out). I did try both with and without the box "Try auto login" checked; doesn't work either way. Left the last 2 boxes unchecked.
??
On 01/12/2015 12:39 PM, Stefan Baur wrote:
-- Peter Brodsky Principal Engineer Applied Physics Laboratory, University of Washington 1013 NE 40th St Seattle, WA 98105 brodsky@apl.washington.edu 206.543.4216
Windows maintainer here.
1st, FYI, You do need "Try auto login" disabled when using an SSH key file on the Windows client.
2nd, What version of X2Go Client for Windows are you using? If you are using the latest version (4.0.3.1-20141214), you can use a debug build. If you can copy the entire command-line output from the debug build, great. (A command-line window opens when you launch the debug build.) Otherwise, at least tell us the last few/several lines before it fails to connect. Note that you need to either launch the debug build from the start menu / desktop shortcut, or from the command-line with the "--debug" argument passed.
Latest debug build: http://code.x2go.org/releases/binary-win32/x2goclient/releases/4.0.3.1-20141...
3rd, in addition to #2, please try using PuTTY (Windows SSH client) to connect to the machine. You'll need PuTTYgen too.
Full installer: http://the.earth.li/~sgtatham/putty/latest/x86/putty-0.63-installer.exe
Individual binaries you can just download & run (currently 0.63): http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe http://the.earth.li/~sgtatham/putty/latest/x86/puttygen.exe
Launch PuTTYgen and import the SSH key by going to: Conversions -> Import Key -> select your private key file. Then "Save Private Key".
Then when you launch PuTTY: specify the hostname/IP Specify the port (if you never changed the port, 22 is the default). Then: Connection -> SSH -> Auth -> specify the "Private key file for authentication" Go back to "Session". For convenience, give the session a name and click "Save". Now click "Open" (to connect.) If you get an error message, please tell us what the error message is. If not, enter your username on the server. (If you get an error message after you enter your username on the server, please tell us what the error message is.)
-Mike#2
On Mon, Jan 12, 2015 at 4:10 PM, Peter Brodsky <brodsky@apl.washington.edu> wrote:
Michael, I'll do this piecewise.
My X2Go client rev is 4.0.3.0 I have not yet downloaded the debug rev you cite below - will do that next.
Installed Putty (full installer). Following your directions, I hit Open and then answer No to caching the key (just try once). The result is a DOS-like window with these 2 lines:
Unable to use key file "C:\Cyclops\data\id_dsa" (OpenSSH SSH-2 private key) login as:
Just for the hell of it, I did enter the username at that prompt. But then it asks for a password, which of course I don't have - there is none, which is the whole point of this exercise.
On Tue, 13 Jan 2015, Michael DePaulo wrote:
OK - progress.
Turns out the private key must be in Putty's format. Used PuttyGen to convert it.
Now Putty is happy. Prompts me for a username, which I enter, then I'm logged in - no passwd required.
X2Go not quite there, however. It gets further(once I specify the Putty-formatted key), but then pops up a window: "Enter passphrase to decrypt a key"
But there is no passphrase. So I'm stuck there. Hitting "OK" without entering one goes nowhere.
On Tue, 13 Jan 2015, Michael DePaulo wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 13.01.2015 um 17:35 schrieb pmb@u.washington.edu:
*chiming in here*
@Mike#2, sorry, I hope I'm not sabotaging your debugging attempts. ;-)
@Pete, X2Go does not understand the PuTTY-formatted key. It wants the original ssh-keygen generated one.
Something to try would be if there's something odd with your keyfile - in a way that PuTTY understands it when importing it, but X2GoClient fails to understand it. To debug that, I would suggest a) running PuttyGen.exe again, b) loading the Putty-formatted key via the "Load" button in the lower part of the screen, c) then selecting "Conversions/Export OpenSSH key" from the top menu. d) Be sure to save that newly-exported key under a different name, maybe x2gologinkey_dsa e) Set the session in X2GoClient to use that newly generated keyfile. f) Try to connect.
Please report back the results.
You could also try the following, since you said the PuTTY-formatted key works with PuTTY itself:
If this works for you, you could script pageant.exe to load the keyfile, then start x2goclient afterwards. I'm actually doing it this way for my customers, though for a different reason (they use WinSCP to transfer files alongside X2GoClient, and this way they only have to load the key and authenticate once).
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUtU0EAAoJEG7d9BjNvlEZoxQIAJw2JhfKD8JnsS/ywStaYZGE GXf4hAjsVy/u19W8jUxQYbQhISdCgb+T7a4eUD3KW6J9XpdO7bGk1zE2dpL24vVV Ni0rBPq95dh0k5ltZKZmqVFc/M1row/hAIA/giQkbR6V46WnWzqZSYUsRVbr+qRp nWOI81L+g3duSAqQMQbTviI28rV98Ilk0bALcQlFisOer0lW7YOeEaupYgoIFLyJ tgBiZEgMauNz6dM0I4aEPlg82WBP6u7dRPC04pc4IGrVa27leFB9WEHOvp54Okly s/TsiB3WH80wsMKPrlkVELN6MFSzSnPGe//aHNMPNPGnIoV/JmlUmLFn/v0jfH4= =SsnH -----END PGP SIGNATURE-----
Gentlemen, I don't know what I did differently (besides reverting to the non-Putty key, which I swear did not work before) and...
Now it works.
At the moment I have no need for advanced features like remote file access, sound, or printing - just the ability to run a simple Java-based GUI running on the server. And that's looking great.
So - thanks so much. The support has been excellent.
Now I need to document this internally before I forget it all.
Best,
On Di 13 Jan 2015 20:18:34 CET, Peter Brodsky wrote:
Now I need to document this internally before I forget it all.
... and then provide us with your X2Go success story so that we can
put it onto our wiki [1].
Mike
[1] http://wiki.x2go.org/doku.php/doc:deployment-stories:start
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
There are a couple of "features" I wonder might be addressable.
For example, I mistakenly try to open a session to a (linux) server
which is not powered up, the (Windows) client simply sits and tries.
There's no way to cancel. Clicking on the small round on/off button in
the session window (the rectangular one that lands in the left/blue
area) does not take. I simply have to wait until it times out. Could
this not be dealt with more actively? Obviously this is a "don't do
that" kind of thing, but it does happen.
Also, if the server is shut down from the client window (which is the case for us because we're effectively headless), then the client "sort of" hangs again. Trying to kill the active session window by clicking the red X in the upper right does nothing. Eventually I get a notice that the server is incommunicado and asks if I want to terminate th current session. Would be nice if there were a cleaner way to handle this.
Sorry for the nitpicks - this is still a very useful tool.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 14.01.2015 um 19:01 schrieb Peter Brodsky:
You could file a wishlist bug for that, and see if one of our volunteer devs picks up on it, or someone steps up and offers to fix it for a price.
To do so, send an eMail to submit@bugs.x2go.org, subject: something descriptive, like "add cancel button for 'connecting' phase", first two lines of the eMail must be ... package: x2goclient severity: wishlist
leave one blank line after that, just like I did here, then add a description, e.g. you could just copy and paste the paragraph of your eMail that I quoted above.
Well, ordinary users should not be able to shut down the server remotely. So for our regular use cases, this isn't an issue.
To shut down the server remotely, assuming you have sufficient permissions, I would suggest the following script on the server (you can place a shortcut to it on the desktop if you like), probably best stored in /usr/local/sbin/ or /usr/local/bin/:
#!/bin/bash (sleep 10 && poweroff) & disown x2goterminate-session
If the account you're using for X2Go remoting doesn't have sufficient permissions to run the poweroff command, I suggest installing sudo (if not already present) and setting it up in a way that your account may run "poweroff" without having to authenticate first. In that case, you need to use sleep 10 && sudo poweroff inside the brackets in the above script. (Note that I haven't tested this, but this is how it should work)
The sleep 10 && poweroff tells your server to wait 10 seconds before it starts powering down. The brackets and the ampersand cause the job to run in the background. The disown tells your server to keep executing the backgrounded task even if the session disconnects. The x2goterminate-session is basically the suicide command for your running X2Go session.
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUtrX5AAoJEG7d9BjNvlEZzFYIAI/tQr3s+E5p282MPpGw+PgG gFNEDtdd77hANc+ESjmFMS0jIv3aSp8zUUh2jC0IvcCp6uh0N+B8zrU2rhdVi8qP 4tS+GaA84IX9bFxhH27No9igIkrgSmD9y1UwENE/IywhlkQd+pcJumSOXoKw+RxK NnXHZaVE8oow8Uw3G2jh0tfnjwE8wSR4pCte3k0ZTfFoT2WXxOmM6wwB7EyDGTqY zO2oblaHdUN+XVppoEOcMFhtE1R1geDyPzU99Gl1cujrazE1mOQnziv88M84eVw4 +hirTPqHwbBIdBTtHN8Wu9crsibbkWel0Zv54eEkypDWia4nyXKJhiT4yfAOvFY= =E/MW -----END PGP SIGNATURE-----
Let me know if this is a "feature", or a bug for which I should submit a report.
Running my X2Go client on a Windows 8 machine, I maximized the session window (by hitting the little square next to the red X). Now I cannot get to anything else on the client. There's no icon available to reduce or minimize the window. I tried "Esc" - no joy. Even shutting down the server doesn't help - now I have a dead session filling the screen. The only way to get out is Ctrl-Alt-Delete and kill the application.
Am I missing something obvious?
Thanks,
In the pyhoca-gui you can select in Input/Output one of these: Fullscreen, Maximized, Customs size.
If you use the x2go client, these settings are similar. (you might want to try the pyhoca-gui if the x2goclient doesn't work well, I had to do the same on my windows8.1)
Kristof
On Fri, Jan 16, 2015 at 11:01 PM, Peter Brodsky <brodsky@apl.washington.edu> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 19.01.2015 um 13:55 schrieb Mihai Moldovan:
Uh, I think there are two issues at hand here.
@Pete: Could you please tell us the values you selected on the first and third tabs of your session configuration? Also, please specify the X2GoClient version you're using (Help/About X2GoClient).
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEbBAEBAgAGBQJUvQCHAAoJEG7d9BjNvlEZkScH+KNiLbDgbckGGoMpFG82xEJh VqAOHbaZSdsatDm3HZf1ikl06lGNNYET3Cs4HHkaqzlwp03NSwFQQ2zcl9Enkkar /atQ4rELSwYPgxN3xr73GLcJmYgHADakUyNimC4DJBE5k0188EtjEddUlliWBG4v aNoYLmnkb2pCGbiT39uH0s5mLSKyKdRlxAsbBYtt5/lLyl+N8wFYQgIMHoGdcC5X omtCXOlTcqCH3sZFWeZR/w8vizrgvBbYpMCLOZiQhVbGR67pYlL4TCTD9IZVltP2 CFG1qI0XPshLtb72XU9mODAa/Ox26uyAQBs2QeYw5FOJutHqSvZsJVUXSSK1Qw== =7+2U -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 19.01.2015 um 14:03 schrieb Stefan Baur:
On 16.01.2015 11:01 PM, Peter Brodsky wrote:
[...]
Guys,
this seems to be an issue. See Bug 670 that has just received an update.
CCing the Bug, so X2Go-Dev gets to see this, too.
@X2Go-Dev/Bug#670: See http://lists.x2go.org/pipermail/x2go-user/2015-January/002827.html
@X2Go-User: See http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=670
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUvQ0jAAoJEG7d9BjNvlEZmqUH+gKv2w8XSGZ3gU8VKqsPZkoj AfaUC8URnbl2gWisuNBTmuievUv5NjpKPAmHrvs43nKIG1Ka5YX0vjlXZoa4y4fC 1gfQW5mDOJ9bpeI/cKIqu/rGUcHb7TlKCAPVTUnt8+4Qv0CLPA1RWhj8icbx4uvX LAl/kKhyVYauDrpAuLceYsVTASjQrFC8y7mfLYOhOLJVKRqOgIeoJgzLqhWcQkUd 4T5+zLRtA+RLs2vWkbaHzGRyBYW5NtfRwCYLHtFKohTXlavdgb7HgZEAs3lxhokY p4tOTY08P/aHLqQhk7LggxQYpFvf+KnUXbhd8CkZipOIllQY8T7IMWsBsuLgP5E= =DvHO -----END PGP SIGNATURE-----
This is getting worse. Now, for reasons I don't understand, my client session freezes. Eventually it pops up a window saying the server is not responding and asks me if I want to terminate the session. I say yes. Nothing happens.
Then I go back to the main X2Go client window and hit the "terminate"
button (the round one in the lower right of the gray rectangular window
inside the blue area). It asks if I want to terminate. I say yes.
Nothing happens.
Eventually another window pops up and tells me the server session has
been killed, and indeed that window goes away. Now the client is stuck
in a mode with a rotating wheel and a message "x2goclient.exe has
stopped working" and a button: "Close program". I hit that button and
it finally all goes away.
So then I try again from scratch. Immediately get a popup: "Socket error: Unknown error". I hit OK. Hit "Cancel". Try again. Now it's hung (no message, no session). Only way to kill it is via the big red X in the upper right of the client window.
On 01/14/2015 10:31 AM, Stefan Baur wrote:
-- Peter Brodsky Principal Engineer Applied Physics Laboratory, University of Washington 1013 NE 40th St Seattle, WA 98105 brodsky@apl.washington.edu 206.543.4216
WAIT - operator error - I had another machine w/the same static IP on the switch.
Obviously a big problem. Please discount the below and I promise self-flagellation for not thinking before posting...
On 01/22/2015 10:29 AM, Peter Brodsky wrote:
-- Peter Brodsky Principal Engineer Applied Physics Laboratory, University of Washington 1013 NE 40th St Seattle, WA 98105 brodsky@apl.washington.edu 206.543.4216
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 22.01.2015 um 19:31 schrieb Peter Brodsky:
Sorry for trolling, but given that you want to run X2Go on a submarine and suggested self-flaggelation, this just seems so appropriate and too good to pass up ... ;-)
https://www.youtube.com/watch?v=IhJQp-q1Y1s
SCNR, Stefan
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUwURCAAoJEG7d9BjNvlEZMbEIAJ7SFl8nocYaEXUnPtWsqg1U lNafjtSHCI2g1YGXe4us/ufBSdbEqup0jyG6E+h/0qsXornXGOa6muWtkGpxV9o8 R5U0GVjwp7LOho+z1Udk71btoQEHz+AZoSvL8M5haSYqpBylSIhVvntv74sqfMVF WTtR+a6xhAcF/fIMsA0GCLHbbRkBjfseU5iDw6mje6R0nmObHYr0j8jAmNYKJzLE GeBp7tTWoz3T6Cd6WlGPa036y2vimOEmxGant8ncbFWgh+DjZNR2byzajl5d3qAt sNzaJBgqwEVqGL1fvxIcz9KBtcQR1Ch84D3v5lWZA7eCMgVFTLackNnJ1ueMU8g= =lt9E -----END PGP SIGNATURE-----