samba: NT_STATUS_BAD_NETWORK_NAME

sohmc · 07-05-2005, 01:55 PM

I'm having some weird issues with samba.

I've recently reinstalled linux to fedora core 4. Using default settings, I should be about to mount my home directory on windows...but I get this:

Code:

sohmc@bart:~$ smbclient //127.0.0.1/sohmc
added interface ip=192.168.1.201 bcast=192.168.1.255 nmask=255.255.255.0
Client started (version 3.0.14a-2).
Connecting to 127.0.0.1 at port 445
Password: 
Doing spnego session setup (blob length=58)
got OID=1 3 6 1 4 1 311 2 2 10
got principal=NONE
Got challenge flags:
Got NTLMSSP neg_flags=0x608a0215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60080215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60080215
Domain=[BART] OS=[Unix] Server=[Samba 3.0.14a-2]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

my smb.conf:

Code:

[global]
        workgroup = MYGROUP2
        server string = Samba Server
        log level = 3
        log file = /var/log/samba/%m.log
        max log size = 50
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        printcap name = /etc/printcap
        dns proxy = No
        idmap uid = 16777216-33554431
        idmap gid = 16777216-33554431
        cups options = raw

[homes]
        comment = Home Directories
        read only = No
        browseable = No

[printers]
        comment = All Printers
        path = /var/spool/samba
        printable = Yes
        browseable = No

[tmp]
        comment = Temporary file space
        path = /tmp
        read only = No
        guest ok = Yes

When I mount tmp, I can see the directories, but I cannot see individual files, even the ones I created and own and permissions to.

I've searched on google and on LQ and cannot seem to find a solution that fixes this problem. I don't think it's a permissions issue because Iv'e tried making my home directory and files in tmp world readable to no avail.

I've also copied this smb.conf from a working linux computer and still does not work.

If you have any suggestions, I'm open!!

thanks!

trickykid · 07-05-2005, 02:24 PM

What I'm confused with is your command 'smbclient //127.0.0.1/sohmc'

Are you connecting using two machines on a network or the same machine? Why would you need to use smbclient on a linux host to connect to itself? 127.0.0.1 is a loopback address

sohmc · 07-05-2005, 02:50 PM

I use the loopback address to test the samba mounts on my local machine.

the results are the same if I use the actual address or when I attempt to get the samba share from another computer.

sohmc · 07-08-2005, 05:19 AM

http://www.linuxquestions.org/questi...hreadid=335899

This thread solves the problem. SELinux blocks accessing home directories...

Quote:

Originally posted by HomeBrewer
Well, I figured this out. Fedora Core 4 blocks home shares in Samba by default through SELinux policies...

For the benefit of Google, here's how to fix it:

Solution 1 (temporary; won't survive a re-boot):

Issue the command:

[root]# setsebool samba_enable_home_dirs=1

Solution 2 (might survive a reboot; I didn't actually try this one):

[root]# setsebool -P samba_enable_home_dirs=1

Solution 3 (survives a reboot):

This is the solution I ultimately settled on. Go to the /etc/selinux/targeted directory. Create a text file called booleans.local, and put the "samba_enable_home_dirs=1" line in it (without the quotes, of course).

Solution 4 (surives a reboot, but removes all SELinux protection):

Edit /etc/selinux/config. Change the line SELINUX=enforcing to SELINUX=permissive or SELINUX=disabled.

ebo · 09-20-2005, 01:36 PM

Hi all,

I have a similar problem. I got a FC4 Server running samba. I solved the problem with the home directory like written here. But I also got a HDD in the server which is NTFS formatted. I mount it (with the ntfs kernel module) and share it with samba as public. When I try to connect, I get the same error as the SELinux-Homedirectory error (which I got fixed, thanks).

Quote:

Domain=[JESSICA] OS=[Unix] Server=[Samba 3.0.14a-2]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Isn´t it possible to share an NTFS folder with samba? (The NTFS HDD did belong to a Win 2003 Server with Domain etc. But the HDD with the Win Sys crashed and now only the data hdd left)

Thanks for your help.

br

René

jcbparry · 01-20-2007, 07:06 PM

I get the same problem too.

Code:

# smbclient //192.168.2.13/

Domain=[PHIL-2AE3A13399] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME



# smbclient //192.168.2.11/

Domain=[JOE] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME



#smbclient //127.0.0.1/

Domain=[JACOB] OS=[Unix] Server=[Samba 3.0.20]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Please Help!

veggiebenz · 12-20-2007, 05:39 PM

I was getting:

"tree connect failed: NT_STATUS_BAD_NETWORK_NAME", and now I've fixed it.

This may or may not work for you, but it fixed my problem.

I could LIST the shared resources like this:

Code:

smbclient -L 127.0.0.1 -U chris

but I could not CONNECT like this:

Code:

smbclient //127.0.0.1/Pubshare -U chris%password

finally with some help from gradin on #samba, we identified the problem in my smb.conf:

Code:

msdfs proxy = no     # dont know what this is but it messed me up bad

Now that this line is gone, everything works fine!

Here's a link on this bug / problem:

http://bugs.centos.org/view.php?id=2554

Hope somebody else can benefit from this.

Thanks

veggiebenz · 12-21-2007, 11:49 AM

I should add that the offending "msdfs" line was placed in my smb.conf by "kcontrol" kde app from "kdenetwork-filesharing" package.

If you are using kcontrol, you can set the defaults in the advanced | VFS section to disable this problematic setting.

or just remove it manually, and be sure to restart samba before trying again