NT_STATUS_BAD_NETWORK_NAME after Samba 3.0.23

patrokov · 07-16-2006, 12:10 AM

I keep getting the following error after upgrading Samba to 3.0.23 using slackpkg in -current:
"tree connect failed: NT_STATUS_BAD_NETWORK_NAME"

Code:

smbclient -L hostname                 :gave the error
smbclient //hostname/username         :connected (home directory)
smbclient //share/music               :gave the error
smbclient //share/movies              :gave the error
smbclient //share/pub                 :gave the error

After some reading in the nonexistent error code section of the samba documentation and various mail lists, I determined that it probably had something to do with permissions on the music, movies, and pub folders. Of course due to the stellar non-documentation regarding this error, I'm still in the dark as to what the exact permissions should be. Here's what they are now:

Code:

drwxr-xr-x 14 username users 4096 2006-06-18 21:01 movies
drwxr-xr-x 43 username users 4096 2006-06-21 01:37 music

Code:

[global]
        workgroup = WORKGROUP
        passdb backend = tdbsam
        log file = /var/log/samba.%m
        max log size = 50
        server signing = auto
        preferred master = No
        domain master = No
        dns proxy = No
        ldap ssl = no
        read only = No
        hosts allow = 192.168.1., 127.
        case sensitive = No
        msdfs proxy = no

[homes]
        comment = Home Directories
        browseable = No

[music]
        path = /share/music

[movies]
        path = /share/movies

[pub]
        path = /share/pub

Please note that this worked flawlessly in 3.0.22. I really don't have time to experiment very long with a non-working Samba server, so for now I've gone back to 3.0.22 and samba is now in the blacklist for slackpkg.

davidsrsb · 07-16-2006, 10:10 PM

I have just upgraded and so far so good.
I did get an unexpected request to install dmapi, which I did
This reminds me that samba also depends on acl and attr??
These are newish packages split from xfsprogs so you may well have one of these missing.

theoffset · 07-16-2006, 10:49 PM

I've been also getting this error from random hosts, even before 3.0.23. But the funny thing is that Windos can connect flawlessly.

Indeed, the lack of documentation of this error has made me wonder several times a big WTF?! The only references I can find on the net seem to point at a permissions problem, but I haven't been able to figure out what's wrong with my config...

Since I can connect with Windos, I'd suspect that its a Samba bug. I'll dig deeper when I find another host which gives me the error.

ExplodingTurnip · 07-16-2006, 11:56 PM

Quote:

Originally Posted by davidsrsb

I have just upgraded and so far so good.
I did get an unexpected request to install dmapi, which I did
This reminds me that samba also depends on acl and attr??
These are newish packages split from xfsprogs so you may well have one of these missing.

You're lucky. I had to download all of the following before I was able to get Samba working again:

acl-2.2.34-i486-1.tgz
attr-2.4.28-i486-1.tgz
cyrus-sasl-2.1.22-i486-1.tgz
dmapi-2.2.3-i486-2.tgz
openldap-client-2.3.24-i486-1.tgz

I'm still running Slackware 10.0, though. So that's probably why.