Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 3 subscribers
  • Views 9705 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

"Target service not allowed" for Dell Server manager - localport 1311

Eric Burch

I am relatively new to Sophos UTM. We use Dell servers that use Dell Server Manager on port 1311 to give server vitals. Has worked for a while but has stopped on Windows 2012R2 (still working on Windows 2008R2 but I have to use localhost instead of the file server name?). I added the service as TCP/UDP source 1:65535 and destination 1311. If I add the service to Web Protection > filtering options > Misc >Allowed target services I get a "host not found" using the https://fileserver:1311 url. If I don't I get the service not allowed. Previously, I put my internal servers in the filtering options > Exceptions list to skip authentication and thought that was the fix. Not sure what is the right way is but need to be able to access the tool.

Best Regards

Eric



This thread was automatically locked due to age.
  • 0

    Can the UTM resolve the hostname of the server?

  • 0

    Hi, Eric, and welcome to the UTM Community!

    If you're using Standard mode, skipping the Proxy is configured in the browser, so you'll need to adjust your GPO or PAC file.

    In this case, I will guess that you would want to consider DNS best practice.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    That (DNS best practices) is the way it is set up - weird that I can ping (support>tools>pingcheck) the hostname successfully from the UTM but name resolution (support>tools>DNS lookup) fails

  • 0 in reply to warper

    I can ping the hostname from the UTM but name resolution fails. Doesn't make sense as ping requires hostname resolution.

  • 0 in reply to Eric Burch

    Take that back - hostname lookup fails with an unqualified hostname but passes with a fully qualified host name

  • 0 in reply to Eric Burch

    Just an update - when I use the policy update tool I get Blocked, reason: Target Service Not Allowed, Policy name: default content filter profile assignment, Exceptions: Internal Exceptions (which is an exception in the filtering options)

     

    I have enabled everything I can think of and still get the error on the server

    The content could not be delivered due to the following condition: Target service not allowed

  • 0 in reply to Eric Burch

    Eric, add the service on the 'Misc' tab of 'Filtering Options'.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    I did that and it still doesn't work but the error changes to a "host not found" - url request string is fileserver:1311/. If I change the request url in the browser to the FQDL I get a page can't be displayed" notice. The service connects over https port 1311 so I added a service TCP/UDP destination 1311 and source 1:65535.

    2017:02:03-10:25:40 utm httpproxy[6081]: id="0002" severity="info" sys="SecureWeb" sub="http" name="web request blocked" action="block" method="CONNECT" srcip="192.168.xxx.xxx" dstip="" user="" group="" ad_domain="" statuscode="502" cached="0" profile="REF_DefaultHTTPProfile (Default Web Filter Profile)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="0" request="0xdea80600" url="https://fileserver:1311/" referer="" error="Host not found" authtime="0" dnstime="3" cattime="0" avscantime="0" fullreqtime="210070" device="0" auth="2" ua="Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; rv:11.0) like Gecko" exceptions="auth,url,certcheck"
    20
  • 0 in reply to Eric Burch

    statuscode="502

    If adding antivirus to the Exception doesn't fix that, then you will need to skip the proxy for this access.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Unfiltered HTML