我有一个Samba 4.6.2的CentOS 7服务器,join到Windows Server 2008 R2域,并且不能使用服务器的主机名或FQDN访问任何共享,只能通过IP地址访问。
我已经validationDNS正在使用nslookup服务器到客户端,客户端到服务器,并在samba服务器上validationADparsing的所有SRVlogging。
当我尝试使用主机名或FQDN时,Windows将显示错误“login失败:目标帐户名称不正确”,客户端的samba日志显示:
[2017/09/28 13:04:00.119699, 3] ../source3/smbd/oplock.c:1322(init_oplocks) init_oplocks: initializing messages. [2017/09/28 13:04:00.119899, 3] ../source3/smbd/process.c:1957(process_smb) Transaction 0 of length 159 (0 toread) [2017/09/28 13:04:00.119956, 3] ../source3/smbd/process.c:1538(switch_message) switch message SMBnegprot (pid 15584) conn 0x0 [2017/09/28 13:04:00.120920, 3] ../source3/smbd/negprot.c:603(reply_negprot) Requested protocol [PC NETWORK PROGRAM 1.0] [2017/09/28 13:04:00.120968, 3] ../source3/smbd/negprot.c:603(reply_negprot) Requested protocol [LANMAN1.0] [2017/09/28 13:04:00.120999, 3] ../source3/smbd/negprot.c:603(reply_negprot) Requested protocol [Windows for Workgroups 3.1a] [2017/09/28 13:04:00.121026, 3] ../source3/smbd/negprot.c:603(reply_negprot) Requested protocol [LM1.2X002] [2017/09/28 13:04:00.121053, 3] ../source3/smbd/negprot.c:603(reply_negprot) Requested protocol [LANMAN2.1] [2017/09/28 13:04:00.121080, 3] ../source3/smbd/negprot.c:603(reply_negprot) Requested protocol [NT LM 0.12] [2017/09/28 13:04:00.121107, 3] ../source3/smbd/negprot.c:603(reply_negprot) Requested protocol [SMB 2.002] [2017/09/28 13:04:00.121133, 3] ../source3/smbd/negprot.c:603(reply_negprot) Requested protocol [SMB 2.???] [2017/09/28 13:04:00.121348, 3] ../source3/smbd/smb2_negprot.c:290(smbd_smb2_request_process_negprot) Selected protocol SMB2_FF [2017/09/28 13:04:00.124041, 3] ../source3/smbd/negprot.c:730(reply_negprot) Selected protocol SMB 2.??? [2017/09/28 13:04:00.135575, 3] ../source3/smbd/smb2_negprot.c:290(smbd_smb2_request_process_negprot) Selected protocol SMB2_10 [2017/09/28 13:04:00.150178, 1] ../source3/librpc/crypto/gse.c:646(gse_get_server_auth_token) gss_accept_sec_context failed with [Unspecified GSS failure. Minor code may provide more information: Request ticket server cifs/[email protected] not found in keytab (ticket kvno 10)] [2017/09/28 13:04:00.161945, 3] ../source3/smbd/server_exit.c:246(exit_server_common) Server exit (NT_STATUS_CONNECTION_RESET) [2017/09/28 13:04:00.179981, 3] ../source3/smbd/oplock.c:1322(init_oplocks) init_oplocks: initializing messages. [2017/09/28 13:04:00.180172, 3] ../source3/smbd/process.c:1957(process_smb) Transaction 0 of length 108 (0 toread) [2017/09/28 13:04:00.198458, 3] ../source3/smbd/smb2_negprot.c:290(smbd_smb2_request_process_negprot) Selected protocol SMB2_10 [2017/09/28 13:04:00.214297, 1] ../source3/librpc/crypto/gse.c:646(gse_get_server_auth_token) gss_accept_sec_context failed with [Unspecified GSS failure. Minor code may provide more information: Request ticket server cifs/[email protected] not found in keytab (ticket kvno 10)] [2017/09/28 13:04:00.227012, 3] ../source3/smbd/server_exit.c:246(exit_server_common) Server exit (NT_STATUS_CONNECTION_RESET)
Sambaconfiguration:
[global] workgroup = DOMAIN realm = DOMAIN.LOCAL security = ads template homedir = /home/%U template shell = /bin/bash kerberos method = secrets and keytab winbind use default domain = true winbind offline logon = true idmap config * : backend = nss idmap config * : range = 3000-7999 idmap config DOMAIN : backend = ad idmap config DOMAIN : default = yes idmap config DOMAIN : range = 10000-1000000 idmap config DOMAIN : schema_mode = rfc2307 winbind nss info = rfc2307 winbind enum users = yes winbind enum groups = yes winbind nested groups = yes log file = /var/log/samba/log.%m log level = 3 max log size = 50 client use spnego = yes load printers = no cups options = raw printcap name = /dev/null
我不知道我缺less什么或解决什么问题。 重新join域,甚至擦除sambaconfiguration没有帮助。 我也手动添加到密钥表的cifs,但然后窗口将保持提示用户名和密码,即使正确。 有任何想法吗?
您的Kerberos安装程序已损坏。
从日志中: Request ticket server cifs/[email protected] not found in keytab (ticket kvno 10) 。
如果Kerberos不可行,似乎还有第二种身份validation方法。 如果您通过IP地址访问,则使用第二种方法。 这是因为Kerberos只能与DNS连接。
如果您通过DNS名称访问Kerberos尝试身份validation并失败。
我想你检查所有maschines(客户端,服务器,Kerberos服务器)的DNS条目。 同时检查DNS反向条目。 之后生成一个新的密钥表。