Home / server / Questions / 137135
Accepted
Neil
Asked: 2010-04-30 10:56:46 +0800 CST

What does NT_STATUS_BAD_NETWORK_NAME mean in Samba?

  • 772

I set up a share like this:

[global]
    security = user
    map to guest = Bad Password
    usershare allow guests = yes

[vms]
    comment = VirtualBox Virtual Machines
    path = /home/neil/VirtualBox/HardDisks
    guest ok = yes
    read only = yes

And when I access the share as myself, and type in my password, it works fine:

$ smbclient //neil-ubuntu/vms -U neil
Enter neil's password: 
Domain=[SHUTTERSTOCK] OS=[Unix] Server=[Samba 3.4.0]
smb: \>

But when I access it as guest, it doesn't work:

$ smbclient //neil-ubuntu/vms -U guest
Enter guest's password: 
Domain=[SHUTTERSTOCK] OS=[Unix] Server=[Samba 3.4.0]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Regardless of what password I type in.

Does anyone know why?

Also, why does smbclient print such useless error messages?

linux file-sharing samba

4 Answers

  1. Best Answer

    I recall a problem like this. I think it was caused by a directory permission somewhere in the path missing read. Check the directory perms are 755 for the path.

    This error is also returned if the path does not exist.

    • 19

  2. I'll just chime in here with a different problem, but same error message. If you're using Samba < 3.2, you cannot connect to Windows Server 2008 AD servers. This includes the version of Samba included in CentOS (and presumably RHEL) 5, currently Samba 3.0.23. As of August 2011, the current version of Samba is 3.6.

    I used the Samba repositories for CentOS 5 hosted by Sernet at http://www.enterprisesamba.org/index.php?id=125 to install Samba 3.4 and connect to a Win 2008 server. Don't forget to install/update winbind (yum install samba3-winbind after you add the repository) and you may need to update /etc/krb5.conf (I just moved it to a /etc/krb5.conf.bak and things work fine).

    I also received Got NTLMSSP neg_flags=0x62898215 frequently in the smbclient logs.

    • 1

  3. try #sudo smbpasswd -a guest

    just a shot there. If that doesn't work, try adding "guest' to the line "valid users" in /etc/samba/smb.conf like so,

    valid users = user1, guest
    • 0

  4. At the risk of raking up an old topic, the "permissions" comment is almost right. I was going mad checking things, everything looked right and it still wouldn't work.

    The obvious answer : I had SElinux turned on and denying any access to the (non standard) location I was trying to share.

    setenforce 0

    And it suddenly works. Of course, now I will turn it back on and fix the config properly. Honest....

    • 0