[Samba] SAMBA v3.6.8 on Solaris 10 NOT working after Windows Server 2008 AD updated

[albert samba]

Hello,

My Samba has been working well until I recently run Windows update for DC.

I got the error message below on my client (Windows 8.1 Enterprise
Evaluation OS) when accessing the Samba shares.
" *\\pinnacle** is not accessible.  You might not have permission to use
this network resource.  Contact the administrator of this server to find
out if you have access permissions.* "

I can ping the Samba host and the hostname(pinnacle) is able to be resolved
by DNS.  The network is no problem at all.

Here is my smb.conf:
*[glocal]*
*workgroup = pmh*
*bind interfaces only = yes*
*wins server = 192.168.136.150*
*interfaces = pinnacle/255.255.255.0 <http://255.255.255.0>*
*netbios name = pinnacle*
*security = domain*
*encrypt passwords = yes*
*pid directory = /local/samba/pinnacle/var/locks*
*lock dir = /local/samba/pinnacle/var/locks*
*log file = /local/samba/pinnacle/logs/log.%m*
*log level = 3*
*[share]*
*comment = Shared Resources*
*path = /shared*
*guest only = no*
*mangled names = no*
*public = yes*
*writable = yes*
*create mask = 0664*

I turned on the Samba log and set the 'log level' to 3 for further
troubleshooting, and I got logs as below:
























*[2017/05/24 11:23:25.800563,  3] libsmb/namequery.c:2533(get_dc_list)
get_dc_list: preferred server list: ", *"[2017/05/24 11:23:25.800703,  3]
libsmb/namequery.c:1741(resolve_lmhosts)  resolve_lmhosts: Attempting
lmhosts lookup for name PMH<0x1c>[2017/05/24 11:23:25.800746,  3]
../libcli/nbt/lmhosts.c:185(resolve_lmhosts_file_as_sockaddr)
resolve_lmhosts: Attempting lmhosts lookup for name PMH<0x1c>[2017/05/24
11:23:25.800779,  3] libsmb/namequery.c:1616(resolve_wins)  resolve_wins:
Attempting wins lookup for name PMH<0x1c>[2017/05/24 11:23:25.800872,  3]
libsmb/namequery.c:1672(resolve_wins)  resolve_wins: using WINS server
192.168.136.150 and tag '*'[2017/05/24 11:23:25.801597,  2]
libsmb/namequery.c:1327(name_query_validator)  Got a positive name query
response from 192.168.136.150 ( 192.168.136.150 )[2017/05/24
11:23:35.802771,  3] libsmb/trusts_util.c:166(enumerate_domain_trusts)
enumerate_domain_trusts: can't locate a DC for domain PMH[2017/05/24
11:23:35.802882,  3] auth/auth.c:219(check_ntlm_password)
check_ntlm_password:  Checking password for unmapped user
[PMH]\[azhou]@[SMBCLIENT] with the new password interface[2017/05/24
11:23:35.802905,  3] auth/auth.c:222(check_ntlm_password)
check_ntlm_password:  mapped user is: [PMH]\[azhou]@[SMBCLIENT][2017/05/24
11:23:35.803092,  3] libsmb/namequery.c:2533(get_dc_list)  get_dc_list:
preferred server list: ", *"[2017/05/24 11:23:45.804975,  2]
auth/auth.c:319(check_ntlm_password)  check_ntlm_password:  Authentication
for user [azhou] -> [azhou] FAILED with error
NT_STATUS_NO_LOGON_SERVERS[2017/05/24 11:23:45.805094,  3]
smbd/error.c:81(error_packet_set)  error packet at smbd/sesssetup.c(124)
cmd=115 (SMBsesssetupX) NT_STATUS_NO_LOGON_SERVERS*

Here is my virtualized env.:

Only DC - Windows Server 2008 evaluation version with the latest update

Samba version 3.6.8 as a file server running Solaris 10 x86 update 8

Client - Windows 8.1 Enterprise Evaluation OS

I doubted something was changed during the Windows update, but am not sure
what they are.  How to get my Samba back to work?


Thanks,
Albert.