Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 30 replies
  • Subscribers 3 subscribers
  • Views 136652 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

Joining the domain failed.

poynter
Having an awful time trying to add the UTM to the domain. 

Running  9.106-17

Tried setting the DNS forwarders, ping finds domain and domain controller

AD Server added fine and working. 

Hostname is utm.pps.local 

SSO Page tried: 

Domain: utm.pps.local / UTM.PPS.LOCAL / UTM / PPS.LOCAL / pps.local

tried pre-adding the computer to the domain and tried pre-adding as pre-2000 computer. 

utm.pps.local in DNS fine. 

AD Server is Server 2012 R2


This thread was automatically locked due to age.
Parents
  • 0
    Wally, I've never had much luck with NTLM and SSO with the UTM.  I wonder if this isn't a different issue.

    What happens if you switch the browser's Proxy Settings to use an internally-resolvable FQDN for the UTM's Internal interface instead of the numeric IP of "Internal (Address)?"

    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
    Wally, I've never had much luck with NTLM and SSO with the UTM.  I wonder if this isn't a different issue.

    What happens if you switch the browser's Proxy Settings to use an internally-resolvable FQDN for the UTM's Internal interface instead of the numeric IP of "Internal (Address)?"

    Cheers - Bob


    Thanks for your suggestion Bob. Fortunately I had already implemented the resolvable FQDN for the proxy settings.
Reply
  • 0 in reply to BAlfson
    Wally, I've never had much luck with NTLM and SSO with the UTM.  I wonder if this isn't a different issue.

    What happens if you switch the browser's Proxy Settings to use an internally-resolvable FQDN for the UTM's Internal interface instead of the numeric IP of "Internal (Address)?"

    Cheers - Bob


    Thanks for your suggestion Bob. Fortunately I had already implemented the resolvable FQDN for the proxy settings.
Children
No Data
Unfiltered HTML