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

Problems in Patterns

Bruno Ramos

After the pattern updates, the UTM simply does not join the domain.
Any possibility about this case?

Multiple clients with the same problem

Hugs,



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to Bruno Ramos

    Hi, Bruno, and welcome to the UTM Community!

    Did this problem resolve itself?  Are you running High Availability?  What makes you think the domain was not joined?

    Cheers - Bob

     
    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

    Ola Balfson, I made sure the equipment did not enter, because it was issued a warning that the UTM was not in the domain. I also could not create groups in the UTM and refer to some group of AD.

    What makes me worried was that a UTM object was created in AD and the Base DN and Bind DN connection tests were successful.


    The problem was resolved after placing a rule without Firewall Allow from any Source> Any Service> Any Destination.
    Which does not make any sense. In the logs it looked like the UTM was blocking itself.

    Before making this rule in Firewall, I performed the following tests.

    1. I placed the User in Prefetch Directory Users, to synchronize the groups of the same.

    2. I created a Request Route pointing the domain to the AD server.

    3. UTM and AD time were the same.

    4. The user to join the Domain was Admin and Admin of the domain.

     

    Regards,

Unfiltered HTML