0

I have a public IIS hosted web site running on windows server 2016. This server is member of a windows nlb cluster. I can't access this web site through https directly from the cluster nodes. This is fine from anywhere else.

What troubles me is that, this is however working fine on a public IIS hosted web site not member of a windows nlb cluster.

The way I do it is to modify the host. file to resolve the dns name to the loopback address 127.0.0.1.

I have a couple of questions:

  1. What is the root cause of this problem?
  2. Could it be solved by installing a Microsoft loopback adapter?

Any help appreciated.


EDIT: This is working fine with http though. Below is the actual error message given by the navigator (Internet Explorer but whatever). TLS advanced options are already turned on but this is probably unrelated.

enter image description here

  • Reveal the actual error message or so on. Don't ever just say "I can't access". Effectively that means nothing at all. – Lex Li Sep 18 at 15:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.