Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Subscribers 27 subscribers
  • Views 1291 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

Exchange 2010 on XG330

bretua

Before moving to XG, I used TMG Forefront to publish exchange and its services.

After moving to XG, with the help of a consultant somehow we managed to make it work but a lot of issues are still present.
One major issue is that when users click on the logout button in OWA, they get the logout page, but if you click back or type in the OWA address again, the user is still logged in.

Another issue is that there is no landing page. Once users type in the OWA address they get greeted by an ugly pop up window asking them to provide a username and password.

Is there anyone here who has experience with publishing exchange and its services with Sophos XG firewalls? We could be doing some sort of consultancy!!!

Any help would be appreciated.

Thank you,
Albert



This thread was automatically locked due to age.
Parents Reply
  • +1 in reply to bretua

    I thought for certain you may have had authentication required for the firewall rule enabled, that would explain the non standard login screen. There is obviously another setting that is causing this. I will attach the settings that I currently use at a customer site, mind you they only use exchange 2013 for managing an office365 deployment. These settings are a bit dated and the exceptions could be cleared and rebuilt ( using the WAF Troubleshooting guide support.sophos.com/.../KB-000036242 ) should you want to make sure your protected the best.

    Protection Policy

    1/2

    2/2

    Firewall WAF Rule

    Exception 1

    Exception 2

Children
  • +1 in reply to AADD

    Thank you for your reply. Unfortunately, I cannot seem to be having access to the WAF troubleshooting guide you have shared with me. As for the screenshots, I see a couple of differences between your and mine setup. I have scheduled downtime this weekend and will try out some changes to the policy. This is the production and it's really difficult to work it out. The problem is I am new to Sophos and this whole thing seems too complicated at times! Slight smile

  • +1 in reply to AADD

    Your solution just worked perfectly!

    Thank you very very much Slight smile

    Cheers!

  • +1 in reply to bretua

    I am glad I could lend a hand. I updated the link to the WAF Troubleshooting Guide, its really useful to know how to deal with issues if you are going to protect webapps with the WAF. People tend to forget Sophos provides support for the WAF itself, not the applications behind it.