Re: Can't access vncserver from TightVNC on WinXP - Nevermind

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry guys,

kept drilling down to discover that the iptables rules within the device were preventing that
which is pretty obvious from the message. Now all I gotta figure out is the rule to allow just
selected services. 

Cheers
TechRanj

--- techranj-subs@xxxxxxxxx wrote:

> Hi,
> 
> got a bit of an issue. Have vncserver (V4.0-5) running on Fedora Core 2. The box running Fedora
> is
> on a public IP with no firewall or NAT in front of it. Just an ADSL modem/Router with
> Firewall/NAT
> turned off. "vncserver" starts up without errors except a few messages about security policy
> file
> and font paths and stuff. When I use a local Remote Desktop Client from KDE to VNC into it, it
> works without problems. But when I use WinXP (TightVNC Viewer), I get "Failed to Connect to
> Server" error on the client side. The WinXP PC is on the same network behind the same Router,
> same
> LAN etc. and is also on a Public IP. 
> 
> On doing a Packet capture using ethereal, I see the WinXP PC sending a TCP message to the
> vncserver machine and the vncserver machine responds with an ICMP message of "Destination
> unreachable (Host administratively prohibited) i.e. Type 3, Code 10. I have no idea what's going
> on. 
> 
> Any ideas?
> TechRanj
> 
> -- 
> fedora-list mailing list
> fedora-list@xxxxxxxxxx
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
> 


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux