XLaunch XDMCP settingsLaunch

XLaunch XDMCP settings
XDMCP settings
Settings for the XDMCP mode. This mode is the most problematic, is not secure, and usually requires altering of the remote machine's settings. The XDMCP protocol will send and receive data on port 177/UDP. But the actual connections will be made to the local port 6000+n /TCP, where n is the display number.

Connect to host
Enables XDMCP and sends 'Query' UDP packets to the specified host.
If you are having problems use Wireshark or equivalent to monitor UDP traffic on the remote host and look for the sequence 'Query' 177/UDP, 'Willing' x/UDP, 'Request' 177/UDP, 'Accept' x/UDP, 'Manage' 177/UDP and see where it stops. If it gets through the sequence then test with local and remote 'xeyes' in multiwindow mode, because the Display Manager acts just like an X client from then on in to provide its login window.

Use indirect connect
Enables XDMCP and sends 'IndirectQuery' packets to the specified host. This host presents a chooser box of several hosts or sends 'ForwardQuery' to another host depending on how it's X Display Manager is configured (via Xaccess file entries).

Search for hosts (broadcast)
Enables XDMCP and broadcasts 'BroadcastQuery' packets to the network. The first responding display manager will be chosen for the session.

XDMCP remote settings
A quick guide to setting insecure XDMCP mode on a remote machine running kdm, gdm, xdm or wdm...
On the remote *nix machine edit the following files, restart the X Display Manager and run at 'init 5'.

Edit the file Xaccess (each Display Manager has its own). Make sure you have a line like this that is uncommented.
 *         #any host can get a login window

Edit the X Display Manager config file (kdmrc, gdm.config, xdm-config or wdm-config) and change
[Xdmcp]
Enable=false (may be shown as 0 in some distributions)
  to
[Xdmcp]
Enable=true (or 1 in some distributions)

or for a xdm style configuration

DisplayManager.requestPort:    0
  to
!DisplayManager.requestPort:    0

출처 : XLaunch Wizard help for Xming - XLaunch XDMCP settings 항목

신고
Posted by 구차니
TAG XDMCP, Xming

댓글을 달아 주세요

Linux/Fedora Core2009.04.06 21:47
여기저기 찾아 보다가 결국에는 GG 때리고 말았는데..
2008년 2월 문서로, KDE에서 kdm을 사용할때는 되는데 GNOME에서 gdm으로는
XDMCP가 열리지 않는 버그가 있다고 한다.
아무튼.. KDE로 시도를 해보던가, 아니면 포기를 하던가 해야겠다..

아니면.. FC6에서는 제대로 되려나..

[링크 : http://forums.fedoraforum.org/showthread.php?t=188130]


아무튼
/etc/X11/gdm/gdm.conf의 에서
/etc/gdm/gdm.conf로 위치가 옮겨졌다.
신고
Posted by 구차니
TAG gdm, XDMCP

댓글을 달아 주세요

XDMCP uses TCP, UDP port 177 and TCP port 6000 to 6005

Setup X. Do not setup with a resolution higher than what the remote users are able to use for their display. The newer version is now capable of probing the video chipset and determine that for you. Some older (X) version may not! Test the X Server by typing either startx or telinit 5. Make sure X is running properly.

[출처 : http://tldp.org/HOWTO/XDMCP-HOWTO/procedure.html]


일단은 방화벽 부터 처치하고, 한번 다시 시도해 봐야겠다.
그나저나.. 이미 실행되어 있는 Xwindow를 끌어 올 방법은 없나..
신고
Posted by 구차니

댓글을 달아 주세요

Linux2009.03.25 23:35
/etc/X11/gdm/gdm.conf
가 FC6에서는
/etc/gdm/custom.conf로 변경되었다고 한다.
[발견 : http://www.netsarang.co.kr/bbs/detail.html?id=xmanager&num=9199&page=66&s_select=&s_text=]

아무튼 Xming이나 cygwin/x를 통해 XDMCP로 접속하려는 나의 음모는 무참히 실패로 돌아가고,
터널링이 문제인지 머가 문제인지 알 수 없는 상황이라, 내일은 내부망에서 접속을 시도해봐야겠다.

Step 3: Enable XDMCP
Code:
gksudo gedit /etc/gdm/gdm.conf
Scroll down to the section
Code:
[xdmcp]
Change
Code:
Enable=false
to
Code:
Enable=true
[링크 : http://ubuntuforums.org/showthread.php?p=2302970]

SSH 터널링은 왜 되었냐면!


신고
Posted by 구차니

댓글을 달아 주세요

  1. 어렵어요 ~

    2009.03.26 10:33 신고 [ ADDR : EDIT/ DEL : REPLY ]