This issue is most likely occuring because your work's firewall is doing protocol filtering not just prot filtering. It means that the type of traffic flowing through the router is checked e.g. is this http of ftp ot vnc traffic so changing the port numbers isn't enough.
This issue is discussed more on this mailing list, but the answer is if you work chooses to restrict that they have their reasons. One possible alternative is to try to set up SSH tunneling (for this you need to see if you can SSH out somewhere. If SSH works then you could tunnel VNC through it. BUt this would be a difficult process and you need to decide if it is worth it. Angelo On Tue, 5 Oct 2004 16:16:53 +0200, Magnus Ekerljung <[EMAIL PROTECTED]> wrote: > Hey guys. > I have a little problem. > I've read all the posts regarding proxys and firewalls, and tried what I've > found, but it still won't work. Here's the deal: > I've got a computer at home that's behind a router. I want to be able to > control this computer from work. > At work I have no rights to open ports, and the computer uses a proxy. > Port 80 is open because WWW works. > I've set the vnc server to port 80, and I forwarded port 80 on the router to > the vnc PC. > I asked a friend to connect to my vnc using vnc viewer: <ip>::80, and it > works. > However, from work it does not. I've tried the negative port number (-5820) > and it doesn't work either. > Does anyone have any idea on what can be done to solve this? > > Any help is greatly appreciated. Much thanks > / Magnus > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
