Domain Controller HTTP Redirect | Quisitive
Domain Controller HTTP Redirect
April 8, 2015
Read our blog.

First, I’m not a networking guy so if this steps on some best practice please comment below on a better solution.

For a recent customer, a new domain (we’ll say was setup for both internal and external access.  The customer found that employees within the company network were not able to access the webpage without specifying  Instead they were directed to a domain controller and thus a dead end.  Obviously we didn’t want to install IIS on each DC just to redirect the traffic.  Thankfully we found what looks to be a simple solution… port proxy at the server network interface level.  So far the testing looks perfect.

To enable the proxy (or forward)

netsh interface portproxy add v4tov4 listenport=80 connectport=80 protocol=tcp


netsh interface portproxy add v4tov4 listenport=80 connectaddress=<website IP> connectport=80 protocol=tcp

To see the forwarder(s)

netsh interface portproxy show all

To delete the forwarders

netsh interface portproxy delete v4tov4 listenport=80