[SOLVED] X Server not accepting remote connections after update

Trifon · 2015-02-21 05:11:32

Hi everyone! After recent upgrade Xorg on my laptop not allows other machines to use him as a window server, just an example:

on laptop:

vitaly@trifon:~/VM$ ps aux | grep Xorg
root 499 2.7 1.3 393628 105276 tty7 Ssl+ фев17 139:48 /usr/lib/xorg-server/Xorg -br -novtswitch -quiet :0 vt7 -auth /var/run/xauth/A:0-rfwYma
vitaly 23338 0.0 0.0 10728 2272 pts/3 S+ 08:01 0:00 grep --color=auto Xorg
As you can see, '-nolisten tcp' flag is absent.

vitaly@trifon:~/VM$ xhost
access control enabled, only authorized clients can connect
INET:192.168.2.2
INET:192.168.13.13

192.168.2.2 is my Virtual machine, which works perfectly before upgrade

if I try to start some graphics program, I see that:
[sandbox@sandbox ~]$ DISPLAY=192.168.2.1:0.0 xterm
xterm: Xt error: Can't open display: 192.168.2.1:0.0

Please tell me how can I let my server work?

Last edited by Trifon (2015-02-21 14:38:14)

Knute · 2015-02-21 05:40:27

Looks to me like 192.168.2.1 is not authorized.

Trifon · 2015-02-21 08:31:52

192.168.2.1 is a server, where must i authorise him?
and I repeat, before one of last system updates this method worked perfectly, other machines (debian wheezy, ubuntu 12.01 LTS) wokrs by this method.

result of server's nmap scan

[sandbox@sandbox ~]$ nmap 192.168.2.1

Starting Nmap 6.47 ( http://nmap.org ) at 2015-02-21 08:12 MSK
Nmap scan report for 192.168.2.1
Host is up (0.0056s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
6881/tcp open bittorrent-tracker
16001/tcp open fmsascon

6000 port is absent

server's iptables-save output

vitaly@trifon:/usr/lib/xorg-server$ sudo iptables-save
[sudo] пароль для vitaly:
# Generated by iptables-save v1.4.21 on Sat Feb 21 11:30:51 2015
*nat
:PREROUTING ACCEPT [5608:753227]
:INPUT ACCEPT [5494:739637]
:OUTPUT ACCEPT [177052:19461071]
:POSTROUTING ACCEPT [1913:133463]
-A POSTROUTING -o tap0 -j MASQUERADE
-A POSTROUTING -o wlp3s0 -j MASQUERADE
COMMIT
# Completed on Sat Feb 21 11:30:51 2015

smirky · 2015-02-21 08:41:18

If you want to be certain about the port, use

$ nmap -p6000 localhost

As far as I know, nmap scans the top 1000 used (known) ports which can be quite misleading sometimes.

Trifon · 2015-02-21 09:55:20

No good results
first i scanned 6000 port, it was closed. i scanned random ports, all was "closed" too

Nmap done: 1 IP address (1 host up) scanned in 0.22 seconds
[sandbox@sandbox ~]$ nmap -p6000 192.168.2.1

Starting Nmap 6.47 ( http://nmap.org ) at 2015-02-21 12:53 MSK
Nmap scan report for 192.168.2.1
Host is up (0.00025s latency).
PORT STATE SERVICE
6000/tcp closed X11

Nmap done: 1 IP address (1 host up) scanned in 0.08 seconds
[sandbox@sandbox ~]$ nmap -p1234 192.168.2.1

Starting Nmap 6.47 ( http://nmap.org ) at 2015-02-21 12:53 MSK
Nmap scan report for 192.168.2.1
Host is up (0.00024s latency).
PORT STATE SERVICE
1234/tcp closed hotline

Nmap done: 1 IP address (1 host up) scanned in 0.07 seconds
[sandbox@sandbox ~]$ nmap -p5731 192.168.2.1

Starting Nmap 6.47 ( http://nmap.org ) at 2015-02-21 12:54 MSK
Nmap scan report for 192.168.2.1
Host is up (0.00029s latency).
PORT STATE SERVICE
5731/tcp closed unknown

Nmap done: 1 IP address (1 host up) scanned in 0.08 seconds

But scan result on working machine tells me that 6000 port is open (Debian Wheezy, dist-upgrade done yesterday, xorg-server was updated and restarted)

vitaly@trifon:/usr/lib/xorg-server$ nmap 192.168.X.X

Starting Nmap 6.47 ( http://nmap.org ) at 2015-02-21 11:29 MSK
Nmap scan report for 192.168.X.X
Host is up (0.14s latency).
Not shown: 996 closed ports
PORT STATE SERVICE
22/tcp open ssh
111/tcp open rpcbind
6000/tcp open X11
6881/tcp open bittorrent-tracker

Last edited by Trifon (2015-02-21 09:58:23)

Gusar · 2015-02-21 10:14:38

"-nolisten tcp" is now the default, so you need to explicitly add "-listen tcp" if you want remote connections. /etc/X11/xinit/xserverrc would be the place to add it, I think.

Last edited by Gusar (2015-02-21 10:15:28)

Trifon · 2015-02-21 10:31:22

THANK YOU!
-listen tcp solved my problem, all works perfectly

smeisner777 · 2016-04-02 21:47:01

I wish I had found this post yesterday. I spent hours looking for the solution to this issue on a Linux Mint 17.3 "Rosa" installation. For Mint 17.3 distros add the following to /etc/mdm/mdm.conf and reboot (may logout and back in will work but I didn't try).

[security]
DisallowTCP=false

[server-Standard]
command=/usr/bin/X -listen tcp -audit 0

I first replaced the "-nolisten tcp" with "-listen tcp" in /etc/X11/xinit/xserverrc to no avail. Thanks for your posts!

jasonwryan · 2016-04-02 21:52:10

Why would you register to necrobump a thread when you aren't even using Arch?

Closing

Arch Linux

#1 2015-02-21 05:11:32

[SOLVED] X Server not accepting remote connections after update

#2 2015-02-21 05:40:27

Re: [SOLVED] X Server not accepting remote connections after update

#3 2015-02-21 08:31:52

Re: [SOLVED] X Server not accepting remote connections after update

#4 2015-02-21 08:41:18

Re: [SOLVED] X Server not accepting remote connections after update

#5 2015-02-21 09:55:20

Re: [SOLVED] X Server not accepting remote connections after update

#6 2015-02-21 10:14:38

Re: [SOLVED] X Server not accepting remote connections after update

#7 2015-02-21 10:31:22

Re: [SOLVED] X Server not accepting remote connections after update

#8 2016-04-02 21:47:01

Re: [SOLVED] X Server not accepting remote connections after update

#9 2016-04-02 21:52:10

Re: [SOLVED] X Server not accepting remote connections after update

Board footer