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.

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.

0 poynter over 11 years ago

Confirmed time on the server and UTM match, time zone on UTM is Europe / London, Time Zone on server is (UTC) Dublin, Edinburgh, Lisbon, London

Thanks!
Cancel
Vote Up 0 Vote Down

Cancel
0 PMD over 11 years ago

I have had problems adding the UTM to a domain as well. Interestingly enough, even though the system reports that it was not added to the domain - checking the DC, the UTM has in fact been added. You might want to check to see if it is there.

Worth noting - AD/LDAP authentication works fine even though the UTM shows that it is not joined to the domain.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 11 years ago

Hi, pointer, and welcome to the User BB!

Check to be sure that the UTM is correctly resolving the IP of your DC in WebAdmin 'Support >> Tools' 'DNS Lookup'.

You might want to review Configuring HTTP/HTTPS proxy access with AD SSO with a Sophos UTM

If the UTM doesn't think that it has joined the domain, delete it in AD before trying again.

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel
0 poynter over 11 years ago

Hi,

Thanks for the replies. Yes I can ping the domain and DC from the tools menu. But no it's not appearing in AD.

Still happening in the 9.2 beta - I'll raise it there too.
Cancel
Vote Up 0 Vote Down

Cancel
0 poynter over 11 years ago

is there anywhere in the logs that would show what the UTM is doing?
Cancel
Vote Up 0 Vote Down

Cancel
0 poynter over 11 years ago

Found this in the logs:

Failed to join domain: failed to lookup DC info for domain 'PPS.LOCAL'

But the DC is set as the only forwarder.
Cancel
Vote Up 0 Vote Down

Cancel
0 poynter over 11 years ago

Tried NET ADS JOIN -U Administrator from the console and returns:

Failed to join domain: failed to lookup DC info for domain 'PPS.LOCAL' over rpc: Undetermined error

Tried added DC to hosts file, resolv.conf = nameserver 127.0.0.1, smb.conf =

[global]

realm = pps.local
netbios name = snarf
security = ads
Cancel
Vote Up 0 Vote Down

Cancel
0 poynter over 11 years ago

edited resolv.conf, so the DC is the primary nameserver - same error.
Cancel
Vote Up 0 Vote Down

Cancel
0 poynter over 11 years ago

Please can someone from Sophos confirm what version of Samba is used and if it is compatible with a 2012 (R2) level domain???

SMBSTATUS does not work.
Cancel
Vote Up 0 Vote Down

Cancel
0 Michael Dunn over 11 years ago

In UTM 9.1 we are using samba-3.6.4-2.

We have confirmed that the UTM can join to a AD 2012r2 server.

Please note that the UTM does not necessarily use resolv.conf and hosts files. You should be using the WebAdmin console for editing that stuff.

What happens if you just:
dig pps.local

Also, is there anything interesting in named.log?
Cancel
Vote Up 0 Vote Down

Cancel