On 02/27/14 08:45, Patrick Dupre wrote: > >> ----- Original Message ----- >> From: Ed Greshko >> Sent: 02/27/14 01:36 AM >> To: Community support for Fedora users >> Subject: Re: vncviewer >> >> On 02/27/14 08:33, Patrick Dupre wrote: >>> Are you sure? >>> >>> telnet connections are not accepted on the machine. >>> telnet machine x (x=0,1) gives No route to host >>> >>> vncviewer 193.49.194.196:0 >>> or >>> vncviewer 193.49.194.196:1 >>> give >>> >>> main: unable connect to socket: No route to host (113) >>> >> Is your client on the same LAN as 193.49.194.196 ? >> > Of course there is a firewall, it is not on the same LAN > Should I ask to have the port open? > which ones ? > which protocle? vnc? > Is it the same probleme with freenx? > [root@meimei ~]# nmap -v -n -P0 -p5900-5906 193.49.194.196 Starting Nmap 6.40 ( http://nmap.org ) at 2014-02-27 08:39 CST Initiating SYN Stealth Scan at 08:39 Scanning 193.49.194.196 [7 ports] Completed SYN Stealth Scan at 08:39, 3.02s elapsed (7 total ports) Nmap scan report for 193.49.194.196 Host is up. PORT STATE SERVICE 5900/tcp filtered vnc 5901/tcp filtered vnc-1 5902/tcp filtered vnc-2 5903/tcp filtered vnc-3 5904/tcp filtered unknown 5905/tcp filtered unknown 5906/tcp filtered unknown Which is what I would expect and which is what I think you're seeing from your remote client.... I think you should discuss the situation with the Network Administrator. Port 5901 would be sufficient, but they may not grant your request. Yes, this is the same issue for freenx. -- Getting tired of non-Fedora discussions and self-serving posts -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
