Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I realize this is a rather old question, but I thought worth answering. IIS is not necessarily the best technology of choice here as it is intended to provide a service, not so much to relay a service. </p> <p>However, if you really wanted to use IIS you can install a product like <a href="http://www.helicontech.com/isapi_rewrite/" rel="nofollow">Helicon Tech's ISAPI Rewrite</a> which supports the proxying of websites through IIS with very little configuration. However, this will be using valuable resources on your server for a problem that may not merit it.</p> <p>Given my understanding that you own both networks (the parent network and the child "secure" network) and that they are both on different subnets but internal, you should be able to use a standard router from your favorite computer supply store to act as the bridge. The router can be told to allow access to a specific port/IP combo on the secure network but no others. This configuration will vary from router to router, but the concept is the same. On a more capable router like a Cisco ASA5505 you can very easily bridge accross multiple child subnets on different physical ports (with any combination of permissions/restrictions) while maintaining the same public interface for internet access. Having a dedicated router like this will provide much greater performance and reliability than proxying through a shared server and IMO better security control.</p> <p>Bottom line is that you have multiple options for solving your problem, but my personal preference would be to adjust the network architecture/router to accomodate your needs before I would use IIS as a proxy server.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload