Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.suse    |    Suse is actually not that bad    |    138,051 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 136,134 of 138,051    |
|    Paulo da Silva to All    |
|    Re: vnc/firewall    |
|    09 Feb 17 07:49:07    |
      From: p_s_d_a_s_i_l_v_a_ns@netcabo.pt              Ă€s 22:15 de 08-02-2017, Carlos E. R. escreveu:       > On 2017-02-08 18:36, Paulo da Silva wrote:       >       >> Enabling VNC in "External zone" works.       >> OK, but what does "External zone" mean? I don't want vnc outside my       >> local network.       >> I thought "Internal zone" refers to local network, but I read (in help)       >> everything is enabled by default. So, it should work and it didn't.       >       > If you only have one interface, the default nowdays is to configure it       > as external. You configure it yourself as internal when you trust the       > LAN router and firewall to internet. It is your choice to define the       > network interface as external or internal. No, the system does not set       > up an interface as internal just because it is connected to the internal       > LAN. You do that, not the system. You tell the firewall what to do.       >       Thanks for the enlightenment, Carlos.       But that's not my problem.              My problem is that I enabled VNC in the External zone.       Internal Zone is grayed meaning all ports are free.       If the client is local, why cannot it access the server without VNC in       the External zone enabled?       Is VNC server available outside local network?              Thanks              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca