Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 9 subscribers
  • Views 30174 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WAF with Exchange 2016

PeterWeir

Has anyone managed to get exchange 2016 working with WAF.

i have followed the instructions for 2013 but it's just not connecting.

Anyone got it to work?



This thread was automatically locked due to age.
  • 0

    Hi,


    so Reverse Authentication for WAF with Exchnage 2016 is optional and useful only for additional security level eg with OTP?  Or is it still something else useful? Because if it still reverse passthrough authentication does not work and users must enter the password twice it is wrong...

    Thanks

    Radovan

  • 0 in reply to RadovanJenčík

    Hi all,

     

    If we are not so concerned with pre-auth and instead are focused mainly on restricting what networks can get to what URLs, do we need to do anything other than set up the real and virtual servers and restrict networks under Site Path Routing?

    I've tested this and it seems to be working as expected with no firewall profiles configured.

     

    Thanks!

Unfiltered HTML