Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 1 subscriber
  • Views 7145 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

UTM 9.105-9: WAF Site-Path-Routing

Chri.s
HI Guys,

i am trying to set up an Path Routing on a Network with some Windows Servers. One of them is an Exchange 2010, one a Server 2012 Ts with Webaccess.

The Base Roots are /owa/ and /rdweb but even trying to reach the root Site i get a forbidden Error. 

I set up the Real Webservers and a virtual one with exceptions for URL Hardening (and for testing purposes all other). But it doesn't run.

May you can give me a short hint what else i need.

Kind regards,

Chris

(Based on this how to: UTM Web Application Firewall - configuring Site Path Routing)


This thread was automatically locked due to age.
Parents
  • 0
    Hostname in HTTP request (x.x.x.123) does not match the server name (utm.dom.loc)

    Try adding x.x.x.123 to the list of domains for the Virtual Server. Or, access the Virtual Server using the actual URL instead of a numeric IP.  Does that help?

    Cheers - Bob

    Sorry for any short responses.  Posted from my iPhone.
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    Hostname in HTTP request (x.x.x.123) does not match the server name (utm.dom.loc)

    Try adding x.x.x.123 to the list of domains for the Virtual Server. Or, access the Virtual Server using the actual URL instead of a numeric IP.  Does that help?

    Cheers - Bob

    Sorry for any short responses.  Posted from my iPhone.
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • 0 in reply to BAlfson
    Try adding x.x.x.123 to the list of domains for the Virtual Server. Or, access the Virtual Server using the actual URL instead of a numeric IP.  Does that help?

    Cheers - Bob

    Sorry for any short responses.  Posted from my iPhone.


    Hello,

    Thanks for the advice. The actual ext Url is ext.dom.de now it is running via utm.dom.loc. Perfect thanks. But now i need a hint how to add the three adresses (ext.dom.de) to work?
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?