Hallo list,
I'm very glad to introduce two new features in X2Go Client.
Direct RDP connection to Windows Terminal Server. This feature was sponsored from Mirco Rohloff from "Rohloff AG" - http://www.rohloff.de With this feature you can open direct RDP connection using installed on the client system RDP client program without X2Go proxy. It could be useful in mixed environments with both Linux and Windows TS. This feature is only available for Linux client. To use it, choose Session type "Connect to Windows terminal server" in Session preferences. You should also check "Direct RDP Connection". After that you can configure additional setting in tab "Settings". In this tab you can choose display resolution, RDP client to use and also specify additional command line parameters. I suggest to use direct RDP connections only over LAN or VPN connections. Over Internet using X2Go proxy is faster and securer. You can install X2Go Client-3.99.3.0 which contain this feature from our repository "heuler"
X2Go client with old (0.9.6) Pulseaudio. This feature was sponsored from Stefan Baur from "BAUR-ITCS UG" - http://office.stefanbaur.de/ This is an alternative "interims" X2Go Client for Windows which includes an obsolete version of Pulseaudio. You can try this version if you have problems with sound in Flash. You can download a Windows binary from here: http://code.x2go.org/releases/binary-win32/x2goclient/with-old-pulseaudio-0....
Regards, Alex
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
On Thu, 2012-09-06 at 12:23 +0200, Oleksandr Shneyder wrote:
Hallo list,
I'm very glad to introduce two new features in X2Go Client.
- Direct RDP connection to Windows Terminal Server. This feature was sponsored from Mirco Rohloff from "Rohloff AG" - http://www.rohloff.de With this feature you can open direct RDP connection using installed on the client system RDP client program without X2Go proxy. It could be useful in mixed environments with both Linux and Windows TS. This feature is only available for Linux client. To use it, choose Session type "Connect to Windows terminal server" in Session preferences. You should also check "Direct RDP Connection". After that you can configure additional setting in tab "Settings". In this tab you can choose display resolution, RDP client to use and also specify additional command line parameters. I suggest to use direct RDP connections only over LAN or VPN connections. Over Internet using X2Go proxy is faster and securer. You can install X2Go Client-3.99.3.0 which contain this feature from our repository "heuler" <snip> I'm delighted to see the changes; thank you very much. I was also intrigued with Mike's additions of sound and local shares.
While WAN performance using X2Go proxy may have been faster with RDP5 as found in rdesktop for Linux and the XP Windows RDS client, we have found that RDP6/7 performance is much faster than X2Go proxy. This is available in xfreerdp for Linux and the freely downloadable TSPlus RDP6/7 client for Windows including Windows XP (www.tsplus.net). Thanks again - John
Please, there are two very basic features that are still missing. Whenever I have two or more machines to x2go, I have to start two client sessions. And then those two collide, causing one to crash. The only way to fix this is to edit /usr/bin/x2gostartagent on one of the target machines and change SSH_PORT to 30200. It seems that as it stands now, x2go is intended to be used with only one machine at a time!
[1]merc1984@f-m.fm
On Thu, Sep 6, 2012, at 03:23, Oleksandr Shneyder wrote:
Hallo list,
I'm very glad to introduce two new features in X2Go Client.
- Direct RDP connection to Windows Terminal Server.
This feature was sponsored from Mirco Rohloff from "Rohloff AG" -
With this feature you can open direct RDP connection using installed on
the client system RDP client program without X2Go proxy. It could be
useful in mixed environments with both Linux and Windows TS. This
feature is only available for Linux client. To use it, choose Session
type "Connect to Windows terminal server" in Session preferences. You
should also check "Direct RDP Connection". After that you can configure
additional setting in tab "Settings". In this tab you can choose display
resolution, RDP client to use and also specify additional command line
parameters. I suggest to use direct RDP connections only over LAN or VPN
connections. Over Internet using X2Go proxy is faster and securer.
You can install X2Go Client-3.99.3.0 which contain this feature from our
repository "heuler"
- X2Go client with old (0.9.6) Pulseaudio.
This feature was sponsored from Stefan Baur from "BAUR-ITCS UG" -
[3]http://office.stefanbaur.de/
This is an alternative "interims" X2Go Client for Windows which includes
an obsolete version of Pulseaudio. You can try this version if you have
problems with sound in Flash.
You can download a Windows binary from here:
[4]http://code.x2go.org/releases/binary-win32/x2goclient/with-old-pulse audio-0.9.6/x2goclient-3.99.3.0.interims-pre2-setup.exe
Regards,
Alex
--
Oleksandr Shneyder
Dipl. Informatik
X2go Core Developer Team
email: [5]oleksandr.shneyder@obviously-nice.de
web: www.obviously-nice.de
--> X2go - everywhere@home
X2Go-User mailing list
[6]X2Go-User@lists.berlios.de
[7]https://lists.berlios.de/mailman/listinfo/x2go-user
Email had 1 attachment:
- signature.asc 1k (application/pgp-signature)
References
- mailto:merc1984@f
- http://www.rohloff.de/
- http://office.stefanbaur.de/
- http://code.x2go.org/releases/binary-win32/x2goclient/with-old-pulseaudio-0....
- mailto:oleksandr.shneyder@obviously-nice.de
- mailto:X2Go-User@lists.berlios.de
- https://lists.berlios.de/mailman/listinfo/x2go-user
-- http://www.fastmail.fm - Same, same, but different...
Hi,
On Do 06 Sep 2012 20:09:48 CEST wrote:
Please, there are two very basic features that are still missing. Whenever I have two or more machines to x2go, I have to start two client sessions. And then those two collide, causing one to crash. The only way to fix this is to edit /usr/bin/x2gostartagent on one of the target machines and change SSH_PORT to 30200. It seems that as it stands now, x2go is intended to be used with only one machine at a time!
[1]merc1984@f-m.fm
If you are juggling with multiple simultaneous X2Go sessions, the
please try pyhoca-gui. One application instance can handle various
sessions to the same or to many servers.
However, I do not observer what you describe above with multiple
running instances of X2Go Client. Can you describe steps on how to
reproduce the issue?
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein 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...
On Thu, 2012-09-06 at 21:26 +0200, Mike Gabriel wrote:
Hi,
On Do 06 Sep 2012 20:09:48 CEST wrote:
Please, there are two very basic features that are still missing. Whenever I have two or more machines to x2go, I have to start two client sessions. And then those two collide, causing one to crash. The only way to fix this is to edit /usr/bin/x2gostartagent on one of the target machines and change SSH_PORT to 30200. It seems that as it stands now, x2go is intended to be used with only one machine at a time!
[1]merc1984@f-m.fm
If you are juggling with multiple simultaneous X2Go sessions, the
please try pyhoca-gui. One application instance can handle various
sessions to the same or to many servers.However, I do not observer what you describe above with multiple
running instances of X2Go Client. Can you describe steps on how to
reproduce the issue?
<snip> I do and strongly second the motion. We are promoting the concept of Content Networks to break the paradigm of a user has one PC to do any of several jobs and replace it where a project has a content network - everything needed to create, consume, communicate, and collaborate on content in a single security context. Users thus have a virtual PC for any tasks, e.g., inter-company collaboration, ad agencies, PR firms, contract engineers, etc.
Thus, one PC may launch several instances of X2Go Client each connecting to a different X2Go Server. Since they are all starting their connections at port 30000, they collide unless one edits x2gostartagent on each X2Go Server to ensure they are unique. That is impractical in a large environment or environments where one may not have control of the X2Go Server.
Earlier versions of x2goclient (e.g., 3.0.1-5) allowed this but I suspect it was by accident. We would really like to see this functionality restored, i.e., a physical PC can run multiple instances of x2goclient to different X2Go Servers without manually configuring each X2Go Server. Thanks - John
-- [1]merc1984@f-m.fm
On Thu, Sep 6, 2012, at 12:46, John A. Sullivan III wrote:
On Thu, 2012-09-06 at 21:26 +0200, Mike Gabriel wrote:
Hi,
On Do 06 Sep 2012 20:09:48 CEST wrote:
Please, there are two very basic features that are still missing.
Whenever I have two or more machines to x2go, I have to start two
client sessions. And then those two collide, causing one to crash. The
only way to fix this is to edit /usr/bin/x2gostartagent on one of the
target machines and change SSH_PORT to 30200. It seems that as it
stands now, x2go is intended to be used with only one machine at a
time!
--
[1][2]merc1984@f-m.fm
If you are juggling with multiple simultaneous X2Go sessions, the
please try pyhoca-gui. One application instance can handle various
sessions to the same or to many servers.
However, I do not observer what you describe above with multiple
running instances of X2Go Client. Can you describe steps on how to
reproduce the issue?
<snip>
I do and strongly second the motion. We are promoting the concept of
Content Networks to break the paradigm of a user has one PC to do any of
several jobs and replace it where a project has a content network -
everything needed to create, consume, communicate, and collaborate on
content in a single security context. Users thus have a virtual PC for
any tasks, e.g., inter-company collaboration, ad agencies, PR firms,
contract engineers, etc.
Thus, one PC may launch several instances of X2Go Client each connecting
to a different X2Go Server. Since they are all starting their
connections at port 30000, they collide unless one edits x2gostartagent
on each X2Go Server to ensure they are unique. That is impractical in a
large environment or environments where one may not have control of the
X2Go Server.
Earlier versions of x2goclient (e.g., 3.0.1-5) allowed this but I
suspect it was by accident. We would really like to see this
functionality restored, i.e., a physical PC can run multiple instances
of x2goclient to different X2Go Servers without manually configuring
each X2Go Server. Thanks - John
Or better, if we could open just one x2go client and have it open multiple machines. What I do now is open the x2go client and connect to one server. The window opens fine. Then I go back to the same x2go client and try to open another machine, but I click on its tile (right side) and nothing happens. So I must open a second x2go client, click on the second machine and it opens the new window, but then I get a popup that the first has been terminated. The reason is they are both trying to use port 30000.
References
- mailto:merc1984@f
- mailto:merc1984@f-m.fm
-- http://www.fastmail.fm - Choose from over 50 domains or use your own
-- [1]merc1984@f-m.fm
On Thu, Sep 6, 2012, at 12:46, John A. Sullivan III wrote:
On Thu, 2012-09-06 at 21:26 +0200, Mike Gabriel wrote:
Hi,
On Do 06 Sep 2012 20:09:48 CEST wrote:
Please, there are two very basic features that are still missing.
Whenever I have two or more machines to x2go, I have to start two
client sessions. And then those two collide, causing one to crash. The
only way to fix this is to edit /usr/bin/x2gostartagent on one of the
target machines and change SSH_PORT to 30200. It seems that as it
stands now, x2go is intended to be used with only one machine at a
time!
--
[1][2]merc1984@f-m.fm
If you are juggling with multiple simultaneous X2Go sessions, the
please try pyhoca-gui. One application instance can handle various
sessions to the same or to many servers.
However, I do not observer what you describe above with multiple
running instances of X2Go Client. Can you describe steps on how to
reproduce the issue?
<snip>
I do and strongly second the motion. We are promoting the concept of
Content Networks to break the paradigm of a user has one PC to do any of
several jobs and replace it where a project has a content network -
everything needed to create, consume, communicate, and collaborate on
content in a single security context. Users thus have a virtual PC for
any tasks, e.g., inter-company collaboration, ad agencies, PR firms,
contract engineers, etc.
Thus, one PC may launch several instances of X2Go Client each connecting
to a different X2Go Server. Since they are all starting their
connections at port 30000, they collide unless one edits x2gostartagent
on each X2Go Server to ensure they are unique. That is impractical in a
large environment or environments where one may not have control of the
X2Go Server.
Earlier versions of x2goclient (e.g., 3.0.1-5) allowed this but I
suspect it was by accident. We would really like to see this
functionality restored, i.e., a physical PC can run multiple instances
of x2goclient to different X2Go Servers without manually configuring
each X2Go Server. Thanks - John
Also pyhoca-gui does not recognize certificate login, so entering a password is necessary, and it does not name the remote machine in the taskbar.
References
- mailto:merc1984@f
- mailto:merc1984@f-m.fm
-- http://www.fastmail.fm - A no graphics, no pop-ups email service
-
John A. Sullivan III -
merc1984＠f-m.fm -
Mike Gabriel -
Oleksandr Shneyder