On the server side, you can
1. make sure the xrdp / sessman services are running
Code:
$ service xrdp status
* Checking status of Remote Desktop Protocol server xrdp [ OK ]
* Checking status of RDP Session Manager sesman [ OK ]
2. use netstat to check the services are bound to the expected ports
Code:
$ sudo netstat -nlpt | grep xrdp
tcp 0 0 127.0.0.1:3350 0.0.0.0:* LISTEN 3995/xrdp-sesman
tcp 0 0 0.0.0.0:3389 0.0.0.0:* LISTEN 3993/xrdp
3. check whether the server side firewall is enabled and if so whether it is allowing incoming connections for those ports
Code:
$ sudo ufw status
Status: active
To Action From
-- ------ ----
22/tcp ALLOW 192.168.1.0/24
3389/tcp ALLOW 192.168.1.0/24
3350/tcp ALLOW 192.168.1.0/24
On the client side you can use telnet or nmap to make sure the port is reachable
Code:
$ telnet 192.168.1.12 3389
Trying 192.168.1.12...
Connected to 192.168.1.12.
Escape character is '^]'.
^]
$ sudo nmap -p 3389 192.168.1.12
Starting Nmap 5.21 ( http://nmap.org ) at 2013-04-11 17:19 UTC
Nmap scan report for 192.168.1.12
Host is up (0.022s latency).
PORT STATE SERVICE
3389/tcp open ms-term-serv
MAC Address: XX:XX:XX:XX:XX:XX (Intel Corporate)
Nmap done: 1 IP address (1 host up) scanned in 0.11 seconds
Bookmarks