Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to use IIS7.5 as a way to route to vnc on different servers or virtual servers. I cant get http to work but not non-http protocols like VNC, telnet, etc. Is there a way to do that?

example: -->   -->


Windows Home Server 2008 (Windows 2008). I realize that IIS is a poor solution but I am trying not to add too much complexity.

I don't have a TCP proxy or a hardware firewall. I have a simple router that can do port forwarding but does not understand DNS. I create virtual servers so I'd like to be able to get at them via domain name or even better subdomain name.

What would be preferable would be

Trying to be simple but it seems like maybe that is not possible.

P.S. I got the idea because of the RDP capability within WHS 2011.

share|improve this question

migrated from Nov 22 '11 at 1:46

This question came from our site for professional and enthusiast programmers.

IIS is an HTTP server, so its purpose in life is to serve HTTP content. Using WAS, you can host non-HTTP WCF services. It MAY be possible to use this to host a non-HTTP proxy (though I even doubt this, as that is probably designed to support short request-response sessions, not a continuously open, bidirectional TCP connection), however, IIS is a terrible solution to this problem. Is your requirement to specifically use IIS, or are you open to other tools (such as a firewall or generic TCP proxy) to solve it? If so, what is your environment? What firewall? Windows verison? – gregmac Nov 22 '11 at 2:16
I'm open to any solution that can help with this and co-exist with IIS. – Mike Reeves Nov 23 '11 at 1:20

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.