tree connect failed: NT_STATUS_BAD_NETWORK_NAME

nilantha · 03-19-2003, 01:58 AM

I am a newbie to samba and linux. I configured smb.conf and now I can browse Linux share from NT and windows machines. But when I try to catch NT share trough linux it gives the following message. When browse through Nautilus I can go up to shared directories. From prompt I tried out smbclient as follws and it give the following message. Pl help me.

[root@nilantha samba]# smbclient //internal/slarmy -U nilantha
added interface ip=202.51.141.134 bcast=202.51.141.143 nmask=255.255.255.240
Got a positive name query response from 202.51.141.142 ( 202.51.141.142 202.51.141.141 )
Password:
Domain=[ITWEB] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Regards,

Nilantha

born4linux · 03-19-2003, 05:16 AM

try xsmbrowser, da?

get it from this link:

http://freshmeat.net/projects/xsmbrowser/?topic_id=150

pingram · 08-02-2003, 11:43 AM

you couldn't let us have a copy of your smb.conf file as a starters reference could you. ive been struggling with NT/Linux via Samba for some time and still can't get the ***** thing to work!

ppuru · 08-02-2003, 12:00 PM

either samba could not resolve the system name internal OR it could not find the slarmy share

edpowerzzz · 10-20-2003, 03:34 AM

yup had the same problem.. but after a lot of frustrating tweaks voila! it works now!.. don't even remember how i did it exactly.. just know that i fixed smbd and nmbd services... you might want to check that out too...

alpartis · 06-19-2008, 11:04 AM

Had the same problem ... spent the better part of a day trying to work through it. For me, the error message set me up for failure by leading me down the wrong path looking for a solution. The real underlying problem was directory permissions two directories above in the path.

Be sure the entire path has at least golbal 'read' permissions set!

A quick 'chmod 755 dir' solved the problem for me. Zounds!

-ap

wanghao · 11-06-2008, 12:14 AM

Thanks for you post ,i encounterd the same problem that you said the chmod the dir flag could resolv the issue.And which dir should be chmod the current?or the spcified?
Thanks in advznce!

All you best!

BassKozz · 12-09-2008, 12:57 AM

Quote:

Originally Posted by alpartis

Had the same problem ... spent the better part of a day trying to work through it. For me, the error message set me up for failure by leading me down the wrong path looking for a solution. The real underlying problem was directory permissions two directories above in the path.

Be sure the entire path has at least golbal 'read' permissions set!

A quick 'chmod 755 dir' solved the problem for me. Zounds!

-ap

ap,
thank you, Thank You, THANK YOU,

I've been racking my brain over this for the past 2 days: http://ubuntuforums.org/showthread.p...68#post6335168

and your post here solved my problem.
Thanks,
-BassKozz

dkrysak · 04-27-2009, 01:20 PM

Quote:

Originally Posted by alpartis

Had the same problem ... spent the better part of a day trying to work through it. For me, the error message set me up for failure by leading me down the wrong path looking for a solution. The real underlying problem was directory permissions two directories above in the path.

Be sure the entire path has at least golbal 'read' permissions set!

A quick 'chmod 755 dir' solved the problem for me. Zounds!

-ap

OMG, this issue was killing me until i saw this thread!