0

I have two IIS sites, which expose the same virtual directory.

One is bound as http::80:wfe.website.com, and is accessed through a reverse proxy server.
The second is bound as http::80:www.website.com, and is not exposed externally.
Our public DNS entries for this website refer www.website.com, and point towards our reverse proxy servers.

We have an entry in our host files, pointing www.website.com to 127.0.0.1.
I have no proxy settings in my LAN settings.
If I ping www.website.com I correctly go to 127.0.0.1.

Now for my issue: On 5/6 of the legs of my load-balanced IIS farm, when I go to www.website.com, I get the website.
On one of the legs of my farm, I get redirected to the wfe.website.com address, which requires internet access.
My colleagues do not have the same problem.

For troubleshooting purposes I really need to be able to access this site locally.

Reaces
  • 5,547
  • 4
  • 36
  • 46
  • "On one of the legs of my farm, I get redirected to the wfe.website.com address," Who redirected you? If it is the reverse proxy, post details about its setup. – Lex Li Mar 13 '19 at 15:55
  • @LexLi That's just it, I shouldn't be hitting the reverse proxy because the host file points towards 127.0.0.1. – Reaces Mar 13 '19 at 17:57

0 Answers0