Xmanager 게시판

서버 리부팅후 XDMCP 접속 여전히 불가.

최종입력: 2013-04-05 17:26 - 넷사랑 | 답글: 4건

 
2013-04-04 15:35 - 강경우

서버 리부팅후 XDMCP 접속 여전히 불가.

 

말씀하신대로 다시 Rebooting 한 후 받은 로그입니다.

확인 부탁드립니다.

Xmanager 2.0.8.1 Korean
Copyright (c) 1997-2006 NetSarang Computer, Inc.
All rights reserved.

UTC Date: Thu Apr 04 06:33:20 2013
Local Date: Thu Apr 04 15:33:20 2013

X Server Directory: "C:\Program Files\NetSarang\Xmanager2\"
Session File: C:\Documents and Settings\Administrator\Application Data\NetSarang\Xmanager\2\Xbrowser\10.254.239.221.xsession
Connection Method: 1
Xdmcp UDP Port: 177
Xdmcp Host: '10.254.239.221'
Product Code: 0
License Type: 2

Server Generation 1
CreateConfig returns a return value: 3
Server profile: %system%\Default Profile.xcf
Hardware information:
Processor architecture: 0
Number of processors: 2
Page size: 4096
Processor type: 586
Minimum application address: 10000
Maximum application address: 7ffeffff
Active processor mask: 3
Allocation granularity: 65536
Processor level: 6
Processor revision: 0x170a
WinSock Version 1.1
Highest Version 2.2
Description: WinSock 2.0
System Status: Running
Max Sockets: 32767
Max UDP Datagram: 65467
Loaded RGB database 'C:\Program Files\NetSarang\Xmanager2\rgb\rgb.txt' successfully.
Local Hostname: 'd3bbae4c9b6a4fa'
Local Host IP Address: 23.30.31.11
Listening port: 6001
Xdmcp Init State: 0
Xdmcp Query Address: 10.254.239.221
Primary Screen Resolution: 1280 x 800
Size of Palette: 0
Number of Reserved Colors: 0
Resolution of Color: 24
Depth of Screen: 32
Maximum Cursor Width: 32
Maximum Cursor Height: 32
Frame Width: 4
Frame Height: 4
Border Width: 1
Border Height: 1
Maximum Client Area Width: 1280
Maximum Client Area Height:744
Icon Width: 32
Icon Height: 32
Caption Height: 26
DBCS Enabled: 1
GDI batch limit: 20

Mouse buttons: 5
Waveform Output Devices: 1
Mouse wheel present: 1

Monitors: 2
Selected Monitor: Virtual Screen
Same display format: 1
Virtual screen x 0, y 0, w 3200 h 1080
Root Window x 0, y 0, w 3200, h 1054
Exact StoreColor: 0
Reverse RGB Order: 0

Screen 0: 3200 x 1054
Keyboard file version: 3.0
Keyboard file: Korean 106 keyboard
Keyboard type: 3
nKeys, minKC, maxKC, mapWidth, nCompose: 106, 8, 114, 4, 0
Number of keycodes: 107
Number of KeySyms: 428
Bytes of KeySyms: 1712
OpenFont(client 0): 'fixed'
OpenFont(client 0): 'cursor'

=== OS Version Information ===
Platform id : 2
Major Version : 5
Minor Version : 1
Build Number : 2600
Description : "Service Pack 3"
Country Code : 82
Country String: 대한민국
ANSI Code Page: 949
Language ID : 18
==============================

Waiting for client connections ...

Xdmcp fatal error: Manager unwilling Host unwilling

프로그램 버전 : Xmanager 2.x
연결 방법 : XDMCP connection
2013-04-04 17:06 - 강경우

Re: 서버 리부팅후 XDMCP 접속 여전히 불가.

 
1번은 접속 시도되어 성공했는 데...

다시 창을 띄우니 실패합니다.


왜 그런것인지요?

-------------------------------------------- (접속 1)

Waiting for client connections ...

Xdmcp Request Address: 10.254.239.221
Xdmcp Connection Address 0: 23.30.31.11
Xdmcp: sent a REQUEST message
Xdmcp: received an ACCEPT message
Xdmcp: sent a MANAGE message.
Xdmcp: received a FAILED message.
Xdmcp fatal error: Session failed Session 167520021 failed for display csa:1: cannot open display

--------------------------------------- (접속 2)


Waiting for client connections ...

win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
Xdmcp: Timed out, state 3. Retransmissions: 0
win32SendTo: fd -1 is not found
XdmcpFlush: 7 bytes send failed
errno = 183
Xdmcp Query Address: 10.254.239.221
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
win32RecvFrom: fd -1 is not found
XdmcpFill: too few bytes(-1) received
2013-04-04 18:13 - 넷사랑

Re: 서버 리부팅후 XDMCP 접속 여전히 불가.

 
안녕하십니까?
넷사랑컴퓨터 기술지원입니다.

첫번째 질문의 "Xdmcp fatal error: Manager unwilling Host unwilling"은 Xaccess 파일에서 로그인 허용을 하지 않았기 때문에 발생하는 메시지입니다. 이 파일은 주로 kdm에서 기본적으로 허용하지 않기 때문입니다.

두번째 질문에서는,
접속에 성공하신 것으로 보아 필요한 설정은 모두 완료되었고, 추가적인 변경이 없음에도 접속이 이루어지지 않은 것, 그리고 로그의 메시지를 볼 때 네트워크 불안정을 생각해 볼 수 있습니다.

사용하시는 네트워크가 와이파이 네트워크이거나 간혹 IP 주소를 중복으로 지정하여 IP 충돌이 일어날 경우 이런 증상이 나타날 수 있습니다.

감사합니다.
2013-04-05 08:30 - 강경우

Re: 서버 리부팅후 XDMCP 접속 여전히 불가.

 
답변 잘 받았습니다...

첫번째 질문의 "Xdmcp fatal error: Manager unwilling Host unwilling"은 Xaccess 파일에서 로그인 허용을 하지 않았기 때문에 발생하는 메시지입니다. 이 파일은 주로 kdm에서 기본적으로 허용하지 않기 때문입니다.

어떤 조치 방법이 있을까요?
현재 계속 그런 상태입니다...
KDM에서 허용하기 위해 필요한 조치가 무엇인지요

확인 부탁드립니다. 협조 감사합니다.

참고로

* #any host can get a login window
-> 이작업은 미리 완료된 상태입니다. 이 부분외에 추가 진행해야 할 내용이 있는지요?
2013-04-05 17:26 - 넷사랑

Re: 서버 리부팅후 XDMCP 접속 여전히 불가.

 
지금까지 내용으로 보아 필요한 서버 설정은 모두 이루어져서 더이상의 서버 설정은 필요 없습니다.
연결이 되었다 안되었다 하는 이유는 네트워크 불안정 요소를 확인해 보셔야 할 것 같습니다
IP 주소를 수동으로 할당했다면 IP 주소 충돌이나 라우팅 설정 등을 확인해 보셔야 합니다.

해당 리눅스 서버에서 PC로 ping 명령을 보낸 후 패킷이 고르게 보내지는지도 확인해 보십시오.

감사합니다.