尝试将 SciLinux 7.1 (EL7.1) 盒加入到在 Windows 2008R2 64 位上运行的 AD 域。
遵循 Red Hat Enterprise Linux 7 Windows 集成指南:
$ sudo realm discover -v mems.local
* Resolving: _ldap._tcp.mems.local
* Resolving: mems.local
! Discovery timed out after 15 seconds
mems.local
type: kerberos
realm-name: MEMS.LOCAL
domain-name: mems.local
configured: no
然而:
$ nslookup -type=srv _ldap._tcp.mems.local
Server: 172.17.21.20
Address: 172.17.21.20#53
_ldap._tcp.mems.local service = 0 100 389 mwinds2.mems.local.
_ldap._tcp.mems.local service = 0 100 389 mwinds1.mems.local.
现在我该怎么做?
# realm join mems.local
See: journalctl REALMD_OPERATION=r1063.5453
realm: Cannot join this realm
# journalctl REALMD_OPERATION=r1063.5453
-- Logs begin at Wed 2015-07-29 14:50:27 AKDT, end at Wed 2015-07-29 15:08:25 AKDT. --
Jul 29 15:08:10 playbox.mems.local realmd[5456]: * Resolving: _ldap._tcp.mems.local
Jul 29 15:08:20 playbox.mems.local realmd[5456]: * Resolving: mems.local
Jul 29 15:08:25 playbox.mems.local realmd[5456]: * No results: mems.local
# nslookup _ldap._tcp.mems.local
Server: 172.17.21.20
Address: 172.17.21.20#53
*** Can't find _ldap._tcp.mems.local: No answer
# nslookup -type=srv _ldap._tcp.mems.local
Server: 172.17.21.20
Address: 172.17.21.20#53
_ldap._tcp.mems.local service = 0 100 389 mwinds2.mems.local.
_ldap._tcp.mems.local service = 0 100 389 mwinds1.mems.local.
$ tcping mwinds1 389
mwinds1 port 389 open.
答案1
如果有人偶然发现这个问题,这里是修复我的 Ubuntu 14.04 盒子的方法,其中我的域名一直超时。
编辑/etc/nsswitch.conf:
使主机行看起来像这样 -
hosts: files dns mdns4_minimal [NOTFOUND=return] mdns4
然后再次尝试你的发现。
答案2
您使用 NetworkManager 吗?IIRC realm discover 的作用是查询 DHCP 域的 NM 的 D-Bus 接口。
我只想直接尝试 realm join mems.local,这样可行吗?