brucehohl@access-4-free.com
2004-Dec-01 22:37 UTC
[Samba] Can not connect to share "NT_STATUS_BAD_NETWORK_NAME"
I have Suse 9.1 + Samba 3.0.9 + winbind joined to a Windows 2000 AD domain "MyCompany". Yesterday for some unknown reason (appears to be Win2K issue) connections to Samba and the ability to browse the domain "MyCompany" from Win2K/XP workstations failed but connections to the public share offered by the Win2K server were OK. Also, all Win98 workstations and were unable to "reconnect" to the Domain "MyCompany". The Win98 workstations were reset to "workgroup" mode and a drive was mapped to the Win2K public share; connections to Samba shares could not be made. Samba provides the following feed back: The following commands succeed: wbinfo -u wbinfo -g getent passwd getent group net ads info (clocks within seconds) The following commands fail: filesrv1:~ # wbinfo -t checking the trust secret via RPC calls failed error code was NT_STATUS_BAD_NETWORK_NAME (0xc00000cc) Could not check secret filesrv1:~ # smbclient //filesrv1/public -U bhohl -d 4 lp_load: refreshing parameters Initialising global parameters params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf" Processing section "[global]" doing parameter workgroup = MYCOMPANY doing parameter realm = MYCOMPANY.COM doing parameter security = ADS doing parameter map to guest = Bad User doing parameter password server = 192.168.1.201 doing parameter socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 doing parameter preferred master = No doing parameter local master = No doing parameter domain master = No doing parameter wins server = 192.168.1.201 doing parameter ldap ssl = no doing parameter idmap uid = 10000-20000 doing parameter idmap gid = 10000-20000 doing parameter winbind separator = / doing parameter winbind use default domain = Yes doing parameter printer admin = @ntadmin, root, administrator pm_process() returned Yes added interface ip=192.168.1.53 bcast=192.168.1.255 nmask=255.255.255.0 Client started (version 3.0.9-1.1-SUSE). Connecting to 192.168.1.53 at port 445 session request ok Serverzone is 18000 Password: Doing spnego session setup (blob length=102) got OID=1 2 840 113554 1 2 2 got OID=1 2 840 48018 1 2 2 got OID=1 3 6 1 4 1 311 2 2 10 got principal=filesrv1$@MYCOMPANY.COM Got challenge flags: Got NTLMSSP neg_flags=0x60890215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_NTLM2 NTLMSSP_CHAL_TARGET_INFO NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH NTLMSSP: Set final flags: Got NTLMSSP neg_flags=0x60080215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_NTLM2 NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH NTLMSSP Sign/Seal - Initialising with flags: Got NTLMSSP neg_flags=0x60080215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_NTLM2 NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH SPNEGO login failed: NT_STATUS_BAD_NETWORK_NAME session setup failed: NT_STATUS_BAD_NETWORK_NAME Please help save my Samba server! Thanks.