I am part of a user group which has access to all outgoing protocols. I have tried using vnc to attach to a server sitting publicly on the internet. I am unable to attach to it. I tried creating a rule, giving access to me, outbound, on port 5900 and i STILL cannot connect to a remote server using vnc. I am a web proxy as well as a firewall client on my machine.
What gives? or am I just really stupid?
Thanks in advance.
(FYI, I can use remote desktops to connect to servers, but for this particular server i HAVE to use VNC).
I'm no expert on isa, but at a guess this appears essentially the same problem as ftp.
We have a scenario slightly different at work where isa is used as a proxy server and all clients except isa are restricted external access. Hence ftp must route via isa in order to exit the network to the internet.
The way this is done is by allowing ftp access out in the rule set. You will see in the protocol toolbox that ftp protocol is linked to an ftp application filter. I am guessing that this is where isa recognises and allows ftp access out from.
We then install the firewall client because secure nat is not an option for us when using isa purely as a web proxy. This redirects the external request from a ftp client to the isa server.
Now VNC I am assuming would be the same scenario. The difference here i can see is that VNC application filter is not predefined in isa at all. So while making access rules, the protocol is not enabled.
Given that I cant seem to find a VNC or Custom UDP port based application filter for download, and I am not good enough with C++ to create my own application filter.