The Samba-Bugzilla – Bug 9937
NT_STATUS_BAD_NETWORK_NAME from Win2k AD servers
Last modified: 2013-07-25 07:37:37 UTC
Created attachment 8948 [details]
a debug-level 10 log
Our smbclient calls have started failing on connections to Windows 2008 AD servers. (Previously there were only Windows 2003 Servers, so we had no issues.)
Domain=[INTRANET] OS=[Windows Server 2008 R2 Enterprise 7601 Service Pack 1] Server=[Windows Server 2008 R2 Enterprise 6.1]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
I'm attaching the -d 10 log. I was also asked to provide a wireshark trace, but I don't know how to do that.
Happy to provide more info if needed.
I have tried to capture the traffic with tcpdump on the client, but unfortunately lack the required privileges. The capture on the server is not an option according to our engineering team.
Perhaps the share name is no longer valid? Use VI (I) instead of I$ for example. Just a thought...
The share name is definitely valid. The same smbclient command-line actually succeeds in 3/4 cases.
I don't know SMB, so here is what happens in lay terms:
* in about 1/4 cases I get NT_STATUS_BAD_NETWORK_NAME, and this is 100% correlated with a Windows Server 2008 being contacted (as seen in my output snippet)
* in the remaning 3/4 cases, a Windows Server 2003 is involved and the same commands succeeds.
I am guessing the network has 3/4 of 2003 servers and 1/4 of 2008 servers, hence the success rate of 3/4.
To clarify: I don't connect to these servers directly. They are involved behind the scene as (I believe) AD servers. My command line would be "smbclient //intranet/..." and behind the scene that involves other servers (for AD?) some of which are 2003 and some 2008.
So again, the share name is definitely correct.