You are not logged in.
Yes I have googled and went through all Xming trouble? pages. Thanks for asking.
I have a arch box called janus and a xp workstation japetus
on janus /etc/ssh/sshd_config have
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost yes
on japetus installed: Putty 0.60, under Connection|SSH|X11|Enable X11 forwarding is switched on the X display location is: localhost:0, with MIT-Magic-Cookie-1 protocol
on japetus installed: Xming 6.9.0.31
there is no firewall running on japetus
on japetus started Xlaunch and left Display number: 0
on japetus fired up putty and connected to janus. Contrary to recommend the DISPLAY var is not set, so:
on janus:
export DISPLAY=localhost:0
echo $DISPLAY returns localhost:0 so that is in order
on janus: xlock &
result
Error: Can't open display: localhost:0
I've been over these settings over and over and am not able to get it working. It must be a small simple oversight
archlinux on a Gigabyte C1037UN-EU, 16GiB
a Promise PDC40718 based ZFS set
root on a Samsung SSD PB22-J
running LogitechMediaServer(-git), Samba, MiniDLNA, TOR
Offline
Have you managed to solve this? I'm facing EXACT same situation and having the EXACT same problem.
Last edited by oinkl (2011-02-22 15:36:50)
Offline
It's a bit strange that the DISPLAY var is not set when yoyu log in, but try changing it to localhost:10
A temporary file is just a pipe with an attitude and a will to live.
Offline
I've just tried that, and it didn't work.
BTW, is it necessary to install Xorg on the Arch machine?
The only X11 packages I have installed are xterm, with all it's included dependencies.
Offline
If you have enabled X11 forwarding in putty; kill sshd on archlinux (/etc/rc.d/sshd stop) and launch it with sshd -d. You should see debug messages that can help ypou to solve the problem. Quite possibly you have to enable a configuration option (sshd will tell you if lanched with -d). If it still do not work, repost with the output you have seen
Last edited by olive (2011-02-23 01:17:48)
Offline
Logs as attached.
debug1: sshd version OpenSSH_5.8p1
debug1: read PEM private key done: type RSA
debug1: private host key: #0 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: private host key: #1 type 2 DSA
debug1: read PEM private key done: type ECDSA
debug1: private host key: #2 type 3 ECDSA
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-d'
Set /proc/self/oom_score_adj from 0 to -1000
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
debug1: Bind to port 22 on ::.
Server listening on :: port 22.
debug1: Server will not fork when running in debugging mode.
debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8
debug1: inetd sockets after dupping: 3, 3
Connection from 192.168.2.1 port 4556
debug1: Client protocol version 2.0; client software version PuTTY_Release_0.60
debug1: no match: PuTTY_Release_0.60
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.8
debug1: permanently_set_uid: 99/99
debug1: list_hostkey_types: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: client->server aes256-ctr hmac-sha1 none
debug1: kex: server->client aes256-ctr hmac-sha1 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST_OLD received
debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT
debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: KEX done
debug1: userauth-request for user root service ssh-connection method none
debug1: attempt 0 failures 0
debug1: PAM: initializing for "root"
debug1: PAM: setting PAM_RHOST to "192.168.2.1"
debug1: PAM: setting PAM_TTY to "ssh"
debug1: userauth-request for user root service ssh-connection method password
debug1: attempt 1 failures 0
debug1: PAM: password authentication accepted for root
debug1: do_pam_account: called
Accepted password for root from 192.168.2.1 port 4556 ssh2
debug1: monitor_child_preauth: root has been authenticated by privileged process
debug1: PAM: establishing credentials
debug1: Entering interactive session for SSH2.
debug1: server_init_dispatch_20
debug1: server_input_channel_open: ctype session rchan 256 win 16384 max 16384
debug1: input_session_request
debug1: channel 0: new [server-session]
debug1: session_new: session 0
debug1: session_open: channel 0
debug1: session_open: session 0: link with channel 0
debug1: server_input_channel_open: confirm session
debug1: server_input_channel_req: channel 0 request x11-req reply 1
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req x11-req
debug1: server_input_channel_req: channel 0 request pty-req reply 1
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req pty-req
debug1: Allocating pty.
debug1: session_pty_req: session 0 alloc /dev/pts/0
debug1: server_input_channel_req: channel 0 request shell reply 1
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req shell
debug1: Setting controlling tty using TIOCSCTTY.
debug1: Received SIGCHLD.
debug1: session_by_pid: pid 5077
debug1: session_exit_message: session 0 channel 0 pid 5077
debug1: session_exit_message: release channel 0
debug1: session_pty_cleanup: session 0 release /dev/pts/0
debug1: session_by_channel: session 0 channel 0
debug1: session_close_by_channel: channel 0 child 0
debug1: session_close: session 0 pid 0
debug1: channel 0: free: server-session, nchannels 1
Connection closed by 192.168.2.1
debug1: do_cleanup
debug1: PAM: cleanup
debug1: PAM: closing session
debug1: PAM: deleting credentials
Transferred: sent 3664, received 2008 bytes
Closing connection to 192.168.2.1 port 4556Offline
Okay, I've managed to get it working after installing the xorg package on Arch.
pacman -S xorgWhat I don't understand is, if I'm using Xming as my X Server on Windows, why do I still need to install the full Xorg stack in guest OS Arch?
Offline
as far as I know only xauth is needed
Offline
as far as I know only xauth is needed
Yup I needed only xauth, thanks for the tip!
Offline