[Samba] NT_STATUS_BAD_NETWORK_NAME for Windows Server 2008
jra at samba.org
Thu Jun 6 09:35:18 MDT 2013
On Thu, Jun 06, 2013 at 04:10:46PM +0100, samuel.ferencik at barclays.com wrote:
> -----Original Message-----
> From: Jeremy Allison [mailto:jra at samba.org]
> Sent: Thursday, June 06, 2013 4:51 PM
> To: Ferencik, Samuel: Markets (PRG)
> Cc: samba at lists.samba.org
> Subject: Re: [Samba] NT_STATUS_BAD_NETWORK_NAME for Windows Server 2008
> On Wed, Jun 05, 2013 at 05:14:47PM +0100, samuel.ferencik at barclays.com wrote:
> > Hi,
> > 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
> > Is this post [ http://serverfault.com/a/303483 ] correct when it says that Samba cannot connect to Win2k8? (We have issues with smbclient versions 3.0 - 3.6.)
> What version of Samba are you running ? smbclient can
> certainly connect to W2K8.
> Hi Jeremy,
> Version 3.0.33-3.39.el5_8
> Version 3.6.9-151.el6
> The problem is reproducible in both.
Ignore the 3.0.x version, that's so out of maintanence
it's not worth following up on.
3.6.9 should connect. Open up a bug at bugzilla.samba.org
and attach a wireshare trace and debug level 10 log of
the connection attempt. That should help us track down
what config is incorrect.
More information about the samba