Results 1 to 2 of 2
Hey there,
I'm attempting to setup a new samba machine for our office to use. This box's role is essentially just one big file share for all in the office ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 03-22-2007 #1Just Joined!
- Join Date
- Mar 2007
- Posts
- 2
Samba NT_STATUS_BAD_NETWORK_NAME error
Hey there,
I'm attempting to setup a new samba machine for our office to use. This box's role is essentially just one big file share for all in the office to use, so it's got one share, anonymous access, about as simple as it gets. I've never run into a problem getting samba working on other machines, but I'm getting the followiung when I try to connect:
[tabacco@specs ~]# smbclient //specs/vss
Password: (there is no password, so I hit [Enter] at this point)
Domain=[COLEFAX] OS=[Unix] Server=[Samba 3.0.10-1.4E.11]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
I get a similar but much less verbose error message if I try this from my Windows box.
Doing a google search for this error turns up about ten million hits, but I haven't been able to find a relevent solution. I've tried a few different variations on smb.conf, and finally ended up on one from the RHEL manual on Samba, which is about as bare-bones as it gets:
This is a brand new install of CentOS4. I just installed CentOS on another box and had no problems getting a share working, so I'm not 100% sure what I've done wrong here. Any ideas?Code:[global] workgroup = COLEFAX netbios name = specs security = share [vss] comment = control your source path = /usr/local/telltale/vss force user = nobody force group = nobody read only = No guest ok = Yes
- 03-22-2007 #2Just Joined!
- Join Date
- Mar 2007
- Posts
- 2
Aha... I ended up figuring it out. The permissions on the path for the 'vss' share were wrong. Always nice to see an error message that really describes the problem ¬¬


Reply With Quote
