Run a website and UltraVNC threw port 80

iampedro · Post by **iampedro** » 2005-01-25 19:44

To be able to run a website and VNC threw port 80 so have a page that automically is the default and it gives you two options one to vnc and the other would be the website and it would be the same port on the outside but on the computer it would be re-directed towards that IIS folder for the website..

ipsec · Post by **ipsec** » 2005-01-25 20:21

Create your own html page that redirects VNC connections. and just set up one other port?

A main page from IIS that will give you a link to continue on within port 80, and another link that will auto open and connect a viewer to a different port on your network.

Unfortunately since both apps are listening, I believe the last app to actually listen on the port (If its the same machine) is the one that works... that could be reversed though.

iampedro · Post by **iampedro** » 2005-01-28 13:39

I still think it is do able... If you know what the exact link to hit or you have someone make a asp or vb page or some type of page where it will come up and then it will give you options to internally connect to which ever port you really want to connect to. I just think it is possible and I will look into it once UltraVNC is finnish I may even build a program to compile it and spam it or something but I know that it is possible to trick IIS and the computer..

ipsec · Post by **ipsec** » 2005-01-31 05:23

iampedro wrote:I still think it is do able... If you know what the exact link to hit or you have someone make a asp or vb page or some type of page where it will come up and then it will give you options to internally connect to which ever port you really want to connect to. I just think it is possible and I will look into it once UltraVNC is finnish I may even build a program to compile it and spam it or something but I know that it is possible to trick IIS and the computer..

that wouldnt be tricking the server, you will still need to use two different ports.

If you have a main page that gives you two options then from one hyperlink you could go to the actual web page,
the other one could connect internally from the webserver to the local host via port 80 externally but the web server would have to do the local port translation from port 80 to a different port for VNC....

If you can create some sort of VB or active X webpage that can decifer what it is that the request is coming from - either it be a VNC web connection request or a regular http request... I would be interested in knowing how you can do that since the request would both be coming in from a web browser and not a client connection... Unless you are using the client connection software in which if you do a packet capture you may be able to script what requests are for the vnc viewer only and auto enable the connection on the server side..

either way thats a lot of work for something when you could just use SSL port option like port 443 which should also be enabled for your outgoing web requests.