Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Subscribers 27 subscribers
  • Views 5880 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 (OWA) doesen't work after changes (Exchange: to forms based authentication)

AndréAegerter

Hi all

WAF doesen't work after changes (Exchange: to forms based authentication). My configuration before: WAF with the following authentication policies > Form with passthrough - worked.
Now, i get the following messages (WAF LOG): HTTP Staus Code 503. I tested on my iPad and iPhone over Mobile Network (Swisscom) and here, i get the Message: Service Unavailable.

 

What i have changed?

@ XG FW: I changed the Firewall rules as in the Picture (Authentication, all to none). Now, the authentication makes the Exchange 2016 and not more the XG FW
@ EX 2016: i changed the Authentication to forms based and chaged also the login Form (now, it is possible to login with the UPN Name).

Information: Internal, the OWA and ECP works without Problem. Only from external, WAF dosen't work anymore.

Someone has an idea?

 

 

cheers
Andrew

 

 



This thread was automatically locked due to age.
Parents
  • +1

    hi all

    i found the Problem. It was a dns issue. Point Diagnostics/ Tools/ Ping: I tried the Webserver to ping (internal FQDN), no answer. I switched the internal FQDN for all Webserver entries to the Hostname, what with the entry under Host and Services/ IP Host matched (Exchange Host).

    Test: I tried the Webserver to ping (Hostname) and it works fine. A new Test of externally (OWA), it was also successfully. Now, everything works fine ;)

Reply
  • +1

    hi all

    i found the Problem. It was a dns issue. Point Diagnostics/ Tools/ Ping: I tried the Webserver to ping (internal FQDN), no answer. I switched the internal FQDN for all Webserver entries to the Hostname, what with the entry under Host and Services/ IP Host matched (Exchange Host).

    Test: I tried the Webserver to ping (Hostname) and it works fine. A new Test of externally (OWA), it was also successfully. Now, everything works fine ;)

Children
No Data