Hello list, In the past we have instructed users to perform 'xhost +' from their centos desktop, then set the DISPLAY variable on a remote computer to forward their display back to the desktop. This does not seem to work on centos 6 - but it did work in centos 5. It works from a vnc session on the desktop machine, but does not work from the local desktop.
We would typically use a display variable like this: export DISPLAY=163.198.177.218:0.0 - The target system acts like the request is being refused: Error: Can't open display: 163.198.177.218:0.0
Have there been any changes in centos 6 which make xhost + behave differently for the desktop session? We've been struggling with this issue now for some time - can't find the right solution. Any help would be appreciated!
Thanks in advance, William
On 05/06/2013 14:15, Edsall, William (WJ) wrote:
Hello list, In the past we have instructed users to perform 'xhost +' from their centos desktop,
http://www.phy.bnl.gov/cybersecurity/old/xhost_plus.html
Edsall, William (WJ) wrote:
Hello list, In the past we have instructed users to perform 'xhost +' from their centos desktop, then set the DISPLAY variable on a remote computer to forward their display back to the desktop. This does not seem to work on centos 6 - but it did work in centos 5. It works from a vnc session on the desktop machine, but does not work from the local desktop.
We would typically use a display variable like this: export DISPLAY=163.198.177.218:0.0 - The target system acts like the request is being refused: Error: Can't open display: 163.198.177.218:0.0
Have there been any changes in centos 6 which make xhost + behave differently for the desktop session? We've been struggling with this issue now for some time - can't find the right solution. Any help would be appreciated!
Try adding:
DisallowTCP=false
in the [security] section of /etc/gdm/custom.conf
Then restart X/gdm (/sbin/init 3; /sbin/init 5)
James Pearson
On 6/5/2013 6:15 AM, Edsall, William (WJ) wrote:
In the past we have instructed users to perform 'xhost +' from their centos desktop, then set the DISPLAY variable on a remote computer to forward their display back to the desktop. This does not seem to work on centos 6 - but it did work in centos 5. It works from a vnc session on the desktop machine, but does not work from the local desktop.
We would typically use a display variable like this: export DISPLAY=163.198.177.218:0.0 - The target system acts like the request is being refused: Error: Can't open display: 163.198.177.218:0.0
Have there been any changes in centos 6 which make xhost + behave differently for the desktop session? We've been struggling with this issue now for some time - can't find the right solution. Any help would be appreciated!
thats an awful practice.
instead, connect to the target machine with an SSH client that has 'x-forwarding' enabled (this is a checkbox in PuTTY or SecureCRT, and is the -X flag on ssh command line). have your X 'server' running locally (already running if you're on a unix workstation, I recommend Xming for MS Windows desktops), and now any X application you launch via that ssh session will open on your local desktop automagically.
or using something like nomachine nx (http://www.nomachine.com)
-- Eero
2013/6/5 John R Pierce pierce@hogranch.com
On 6/5/2013 6:15 AM, Edsall, William (WJ) wrote:
In the past we have instructed users to perform 'xhost +' from their
centos desktop, then set the DISPLAY variable on a remote computer to forward their display back to the desktop. This does not seem to work on centos 6 - but it did work in centos 5. It works from a vnc session on the desktop machine, but does not work from the local desktop.
We would typically use a display variable like this: export
DISPLAY=163.198.177.218:0.0 - The target system acts like the request is being refused:
Error: Can't open display: 163.198.177.218:0.0
Have there been any changes in centos 6 which make xhost + behave
differently for the desktop session?
We've been struggling with this issue now for some time - can't find
the right solution. Any help would be appreciated!
thats an awful practice.
instead, connect to the target machine with an SSH client that has 'x-forwarding' enabled (this is a checkbox in PuTTY or SecureCRT, and is the -X flag on ssh command line). have your X 'server' running locally (already running if you're on a unix workstation, I recommend Xming for MS Windows desktops), and now any X application you launch via that ssh session will open on your local desktop automagically.
-- john r pierce 37N 122W somewhere on the middle of the left coast
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos