>check using netstat -tupln
[root@tiger mahmood]# netstat -tupln | grep vnc
tcp 0 0 0.0.0.0:5901 0.0.0.0:*
LISTEN 12185/Xvnc
tcp 0 0 0.0.0.0:6001 0.0.0.0:*
LISTEN 12185/Xvnc
tcp 0 0 :::6001 :::*
LISTEN 12185/Xvnc
>The easiest way to check if that is the problem is by trying to
>telnet to the appropriate port (ie :0 is 5900 :1 is 5901 ...) If it
>works from localhost but not from a remote it is iptables or another
>firewall.
[mahmood@tiger ~]$ telnet localhost:5900
telnet: localhost:5900: Name or service not known
localhost:5900: Unknown host
[mahmood@tiger ~]$ telnet localhost:5901
telnet: localhost:5901: Name or service not known
localhost:5901: Unknown host
[mahmood@tiger ~]$ telnet 127.0.0.1:5900
telnet: 127.0.0.1:5900: Name or service not known
127.0.0.1:5900: Unknown host
[mahmood@tiger ~]$ telnet 127.0.0.1:5901
telnet: 127.0.0.1:5901: Name or service not known
127.0.0.1:5901: Unknown host
[mahmood@tiger ~]$
>if you've cofirmed the service has started on the target box
[mahmood@tiger ~]$ service vncserver status
Xvnc (pid 12185) is running...
>the target box also needs an exception in IPTables for those ports.
From the output of iptables, are they open or close?
Regards,
Mahmood
________________________________
From: Jason Bronner <[email protected]>
To: Mahmood Naderan <[email protected]>
Cc: "[email protected]" <[email protected]>
Sent: Tuesday, March 5, 2013 6:43 PM
Subject: Re: troubleshooting vnc
if you've cofirmed the service has started on the target box start looking at
things between the boxes which would cause a timeout. i.e. Ports being
forwarded in the router to the target box. VNC needs a couple of these, should
be a full listing on portforward.com for what it uses along with a listing of a
good number of routers by make/model# with screenshots. the target box also
needs an exception in IPTables for those ports.
