Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

[Ayo Adeyeri]

I would like to thank everyone who assisted me with this problem.  It turns out 
that the problem was caused by the fact that we were running selinux on the 
server.  Once it was disabled the share was accessible.

Thanks
Ayo

-Original Message-
From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On 
Behalf Of Ayo Adeyeri
Sent: Thursday, November 11, 2010 9:37 AM
To: John Drescher; samba
Subject: Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Thanks John,

I just removed the "." , changed the workgroup name to covecapcom but I am 
still getting the same errors in the log file when I attempt to connect to 
either of the shares from a windows client.

Thanks,
Ayo Adeyeri


-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Thursday, November 11, 2010 9:30 AM
To: Ayo Adeyeri; samba
Subject: Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Network names with a . in them are not supported. Well unless you are
talking about an ads realm.

John

This e-mail message, and any enclosures, is intended only for the persons to 
whom it is addressed, and may contain confidential information. Any use, 
distribution, modification, copying or disclosure by any other person is 
strictly prohibited. If you receive this message in error, please notify the 
sender by return e-mail and delete this message from your computer.  InfoHedge 
disclaims all responsibility from and accepts no liability  whatsoever for any 
incorrect, misleading or altered information contained herein, or for the 
consequences of any unauthorized person acting, or refraining from acting, on 
any information contained in this message.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

[John Drescher]

On Thu, Nov 11, 2010 at 9:36 AM, Ayo Adeyeri  wrote:
> Thanks John,
>
> I just removed the "." , changed the workgroup name to covecapcom but I am 
> still getting the same errors in the log file when I attempt to connect to 
> either of the shares from a windows client.
>

Are the windows clients windows 7?

Also share level security is being discouraged for some time.

John
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

[Ayo Adeyeri]

Thanks John,

I just removed the "." , changed the workgroup name to covecapcom but I am 
still getting the same errors in the log file when I attempt to connect to 
either of the shares from a windows client.

Thanks,
Ayo Adeyeri


-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Thursday, November 11, 2010 9:30 AM
To: Ayo Adeyeri; samba
Subject: Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Network names with a . in them are not supported. Well unless you are
talking about an ads realm.

John

This e-mail message, and any enclosures, is intended only for the persons to 
whom it is addressed, and may contain confidential information. Any use, 
distribution, modification, copying or disclosure by any other person is 
strictly prohibited. If you receive this message in error, please notify the 
sender by return e-mail and delete this message from your computer.  InfoHedge 
disclaims all responsibility from and accepts no liability  whatsoever for any 
incorrect, misleading or altered information contained herein, or for the 
consequences of any unauthorized person acting, or refraining from acting, on 
any information contained in this message.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

[John Drescher]

Network names with a . in them are not supported. Well unless you are
talking about an ads realm.

John
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

[Ayo Adeyeri]

Bump

-Original Message-
From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On 
Behalf Of Ayo Adeyeri
Sent: Wednesday, November 10, 2010 7:17 PM
To: samba@lists.samba.org
Subject: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

Let me start off by apologizing for this rambling post.  I have been working on 
this problem all day and have not gotten anywhere.
This is my first time working with samba and I have been tasked to set up a 
share that does not require a password for access.  I have been tinkering with 
the configuration file but I cannot get it to work.  Here is my current 
smb.conf file that I have:

global]
security = share
workgroup = somedomain.com
guest account = murex
log file = /var/log/samba/%m.log


[Murex]
comment = Murex pickup
path = /apps/murex/pickup
writable = yes
read only = no
guest ok = yes


[testdir]
comment = Troubleshooting area
path = /sambatest
writable = yes
read only = no
guest ok = yes
guest only = yes

When I try to access it either of the shares (Murex or testdir) using 
smbclient, I get the following:
# smbclient //localhost/murex
Password:
Domain=[SOMEDOMAIN.COM] OS=[Unix] Server=[Samba 3.0.28-0.el5.8]
Server not using user level security and no password supplied.
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
#
Not sure why it is stating that no password was supplied because I entered a 
password.  I tried both the root password since that is what I was logged in as 
and the password for the user murex.  The murex user is a valid unix account.  
I also created a samba password for the murex user (I used smbpasswd -a murex). 
 This was done recently but it did not change anything.

I can see the shares from our windows clients but when I try and open up a 
share (by double clicking on it) or map a drive to the share I get the 
following errors in the log files:
[2010/11/10 18:49:35, 0] smbd/service.c:make_connection_snum(1003)
  '/apps/murex/pickup' does not exist or permission denied when connecting to 
[Murex] Error was Permission denied
[2010/11/10 18:49:36, 0] smbd/service.c:make_connection_snum(1003)
  '/sambatest' does not exist or permission denied when connecting to [testdir] 
Error was Permission denied

I also see these same errors in the log files when I run the smbclient command 
from above.  The unix permissions on these directories are set at 777.

This is driving me nuts because I think it has got be a pretty minor 
configuration error but I can't figure out what it is.  Does anyone have any 
ideas of what I am missing or doing wrong?

Thanks,
Ayo Adeyeri
InfoHedge Technologies LLC
747 Third Avenue, 4th Floor, New York, NY 10017
ayo.adey...@infohedge.net
Office: (212) 531-5835



This e-mail message, and any enclosures, is intended only for the persons to 
whom it is addressed, and may contain confidential information. Any use, 
distribution, modification, copying or disclosure by any other person is 
strictly prohibited. If you receive this message in error, please notify the 
sender by return e-mail and delete this message from your computer. InfoHedge 
disclaims all responsibility from and accepts no liability whatsoever for any 
incorrect, misleading or altered information contained herein, or for the 
consequences of any unauthorized person acting, or refraining from acting, on 
any information contained in this message.
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

This e-mail message, and any enclosures, is intended only for the persons to 
whom it is addressed, and may contain confidential information. Any use, 
distribution, modification, copying or disclosure by any other person is 
strictly prohibited. If you receive this message in error, please notify the 
sender by return e-mail and delete this message from your computer.  InfoHedge 
disclaims all responsibility from and accepts no liability  whatsoever for any 
incorrect, misleading or altered information contained herein, or for the 
consequences of any unauthorized person acting, or refraining from acting, on 
any information contained in this message.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

[Dominic Gamble]

Hi Rob,

After a reboot, everything works (both the /test share and the /tmp share,
and it now shows the files in them). It doesn't make any sense, but THANK
YOU!

I used chkconfig to ensure that both smb and ldap started at runlevels 3 and
5, and then rebooted.

I don't know how many times I restarted smb and slapd, and I don't quite
understand why a full reboot was required, but there you go!

Best regards,
Dominic.

-Original Message-
From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org]
On Behalf Of Rob Townley
Sent: Tuesday, 29 December 2009 4:45 AM
To: samba@lists.samba.org
Subject: Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

On Mon, Dec 28, 2009 at 4:03 AM, Michael Adam  wrote:
> Hi Dominic,
>
> Dominic Gamble wrote:
>> Hi,
>>
>> I can't get access to any shares when running "smbclient //DUCK/test -U
>> Dominic". I'm getting the message:
>> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>>
>> I'm pretty sure it's authenticating properly as it says "session setup
ok"
>> in the debug output. If I enter the wrong password I get:
>> "session setup failed: NT_STATUS_LOGON_FAILURE"
>
> This is correct.

Starting from a fresh boot up, try to use the /test share first, does it
work?
Does /tmp then fail?
If so, look under /var/cache/samba/

i don't remember exactly what i came across the
NT_STATUS_BAD_NETWORK_NAME error on CentOS 5.4 and what i did to fix
it, but do remember it wasn't what i expected.

>
>> I'm running CentOS 5.4 with the following samba packages
>>
>> samba-common-3.0.33-3.15.el5_4.1
>> samba-3.0.33-3.15.el5_4.1
>> samba-swat-3.0.33-3.15.el5_4.1
>> samba-client-3.0.33-3.15.el5_4.1
>>
>> My samba setup uses LDAP for authentication. All logging seems to
indicate
>> that authentication and LDAP is working well.
>>
>> My /etc/samba/smb.conf was generated with SWAT and has the following
shares:
>>
>> [tmp]
>>         comment = temporary files
>>         path = /tmp
>>         hosts allow =
>>         hosts deny =
>>
>> [test]
>>         comment = test files
>>         path = /test
>>         hosts allow =
>>         hosts deny =
>>
>>
>> Both shares contain a file called myfile.txt.
>>
>> When I connect to the "tmp" share, I don't get the "tree connect failed:
>> NT_STATUS_BAD_NETWORK_NAME", but I can't list any files:
>>
>> [r...@duck cache]# smbclient //DUCK/tmp -U dominic
>> Password:
>> Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
>> smb: \> ls
>>   .                                   D        0  Mon Dec 28 04:02:13
2009
>>   ..                                  D        0  Sun Dec 27 21:16:53
2009
>>
>>                 36224 blocks of size 8388608. 34082 blocks available
>> smb: \>
>>
>> When I connect to the "test" share I get the "tree connect failed:
>> NT_STATUS_BAD_NETWORK_NAME":
>> [r...@duck cache]# smbclient //DUCK/test -U dominic
>> Password:
>> Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
>> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>>
>> The permissions on the /tmp and /test folders are the same:
>>
>> drwxrwxrwt 2 root root 4096 Dec 27 21:35 test
>> drwxrwxrwt 4 root root 4096 Dec 28 04:02 tmp
>>
>> There are no complex acls on them either:
>>
>> [r...@duck /]# getfacl tmp
>> # file: tmp
>> # owner: root
>> # group: root
>> user::rwx
>> group::rwx
>> other::rwx
>>
>> [r...@duck /]# getfacl test
>> # file: test
>> # owner: root
>> # group: root
>> user::rwx
>> group::rwx
>> other::rwx
>>
>> I've tried getting more debug info by setting log levels to 10 in both
>> smb.conf and using the -d10 parameter on the command line, but it gives
me
>> nothing useful in the logs or in the output.
>>
>> I've been through 'The Samba Checklist'
>>
(http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html)
>> and had no other problems.
>>
>> Here is the rest of my smb.conf:
>>
>> [global]
>>         workgroup = ORANDA
>>         server string = Duck
>>         passdb backend = ldapsam:ldap://localhost/
>>         pam password change = Yes
>>         passwd program = /usr/sbin/smbldap-passwd %u
>>         passwd chat = *New*password* %n\n *Retype*new*password* %n\n
>> *all*authentication*tokens*updated*
>>         unix password sync = Yes
>&g

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

[Rob Townley]

On Mon, Dec 28, 2009 at 4:03 AM, Michael Adam  wrote:
> Hi Dominic,
>
> Dominic Gamble wrote:
>> Hi,
>>
>> I can't get access to any shares when running "smbclient //DUCK/test -U
>> Dominic". I'm getting the message:
>> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>>
>> I'm pretty sure it's authenticating properly as it says "session setup ok"
>> in the debug output. If I enter the wrong password I get:
>> "session setup failed: NT_STATUS_LOGON_FAILURE"
>
> This is correct.

Starting from a fresh boot up, try to use the /test share first, does it work?
Does /tmp then fail?
If so, look under /var/cache/samba/

i don't remember exactly what i came across the
NT_STATUS_BAD_NETWORK_NAME error on CentOS 5.4 and what i did to fix
it, but do remember it wasn't what i expected.

>
>> I'm running CentOS 5.4 with the following samba packages
>>
>> samba-common-3.0.33-3.15.el5_4.1
>> samba-3.0.33-3.15.el5_4.1
>> samba-swat-3.0.33-3.15.el5_4.1
>> samba-client-3.0.33-3.15.el5_4.1
>>
>> My samba setup uses LDAP for authentication. All logging seems to indicate
>> that authentication and LDAP is working well.
>>
>> My /etc/samba/smb.conf was generated with SWAT and has the following shares:
>>
>> [tmp]
>>         comment = temporary files
>>         path = /tmp
>>         hosts allow =
>>         hosts deny =
>>
>> [test]
>>         comment = test files
>>         path = /test
>>         hosts allow =
>>         hosts deny =
>>
>>
>> Both shares contain a file called myfile.txt.
>>
>> When I connect to the "tmp" share, I don't get the "tree connect failed:
>> NT_STATUS_BAD_NETWORK_NAME", but I can't list any files:
>>
>> [r...@duck cache]# smbclient //DUCK/tmp -U dominic
>> Password:
>> Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
>> smb: \> ls
>>   .                                   D        0  Mon Dec 28 04:02:13 2009
>>   ..                                  D        0  Sun Dec 27 21:16:53 2009
>>
>>                 36224 blocks of size 8388608. 34082 blocks available
>> smb: \>
>>
>> When I connect to the "test" share I get the "tree connect failed:
>> NT_STATUS_BAD_NETWORK_NAME":
>> [r...@duck cache]# smbclient //DUCK/test -U dominic
>> Password:
>> Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
>> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>>
>> The permissions on the /tmp and /test folders are the same:
>>
>> drwxrwxrwt 2 root root 4096 Dec 27 21:35 test
>> drwxrwxrwt 4 root root 4096 Dec 28 04:02 tmp
>>
>> There are no complex acls on them either:
>>
>> [r...@duck /]# getfacl tmp
>> # file: tmp
>> # owner: root
>> # group: root
>> user::rwx
>> group::rwx
>> other::rwx
>>
>> [r...@duck /]# getfacl test
>> # file: test
>> # owner: root
>> # group: root
>> user::rwx
>> group::rwx
>> other::rwx
>>
>> I've tried getting more debug info by setting log levels to 10 in both
>> smb.conf and using the -d10 parameter on the command line, but it gives me
>> nothing useful in the logs or in the output.
>>
>> I've been through 'The Samba Checklist'
>> (http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html)
>> and had no other problems.
>>
>> Here is the rest of my smb.conf:
>>
>> [global]
>>         workgroup = ORANDA
>>         server string = Duck
>>         passdb backend = ldapsam:ldap://localhost/
>>         pam password change = Yes
>>         passwd program = /usr/sbin/smbldap-passwd %u
>>         passwd chat = *New*password* %n\n *Retype*new*password* %n\n
>> *all*authentication*tokens*updated*
>>         unix password sync = Yes
>>         log level = 10
>>         log file = /var/log/samba/log.%m
>>         load printers = No
>>         printcap name = /dev/null
>>         disable spoolss = Yes
>>         add user script = /usr/sbin/smbldap-useradd -m "%u"
>>         delete user script = /usr/sbin/smbldap-userdel "%u"
>>         add group script = /usr/sbin/smbldap-groupadd -p "%g"
>>         delete group script = /usr/sbin/smbldap-groupdel "%g"
>>         add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
>>         delete user from group script = /usr/sbin/smbldap-groupmod -x "%u"
>> "%g"
>>         set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u"
>>         add machine script = /usr/sbin/smbldap-useradd -w "%u"
>>         logon script = login.cmd
>>         logon path = \\%N\profiles\%U
>>         logon drive = H:
>>         domain logons = Yes
>>         os level = 127
>>         wins support = Yes
>>         ldap admin dn = cn=admin,dc=oranda,dc=internal
>>         ldap delete dn = Yes
>>         ldap group suffix = ou=Group
>>         ldap idmap suffix = ou=Idmap
>>         ldap machine suffix = ou=Computers
>>         ldap passwd sync = Yes
>>         ldap suffix = dc=oranda,dc=internal
>>         ldap user suffix = ou=People
>>         panic action = /usr/share/samba/panic-action %d
>>         admin users = dominic
>>         hosts allow = 192.168.10., 127.
>>         hosts deny = ALL
>>         printing = bsd
>>       

Re: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

[Michael Adam]

Hi Dominic,

Dominic Gamble wrote:
> Hi,
> 
> I can't get access to any shares when running "smbclient //DUCK/test -U
> Dominic". I'm getting the message:
> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
> 
> I'm pretty sure it's authenticating properly as it says "session setup ok"
> in the debug output. If I enter the wrong password I get:
> "session setup failed: NT_STATUS_LOGON_FAILURE"

This is correct.

> I'm running CentOS 5.4 with the following samba packages
> 
> samba-common-3.0.33-3.15.el5_4.1
> samba-3.0.33-3.15.el5_4.1
> samba-swat-3.0.33-3.15.el5_4.1
> samba-client-3.0.33-3.15.el5_4.1
> 
> My samba setup uses LDAP for authentication. All logging seems to indicate
> that authentication and LDAP is working well.
> 
> My /etc/samba/smb.conf was generated with SWAT and has the following shares:
> 
> [tmp]
> comment = temporary files
> path = /tmp
> hosts allow =
> hosts deny =
> 
> [test]
> comment = test files
> path = /test
> hosts allow =
> hosts deny =
> 
> 
> Both shares contain a file called myfile.txt.
> 
> When I connect to the "tmp" share, I don't get the "tree connect failed:
> NT_STATUS_BAD_NETWORK_NAME", but I can't list any files:
> 
> [r...@duck cache]# smbclient //DUCK/tmp -U dominic
> Password:
> Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
> smb: \> ls
>   .   D0  Mon Dec 28 04:02:13 2009
>   ..  D0  Sun Dec 27 21:16:53 2009
> 
> 36224 blocks of size 8388608. 34082 blocks available
> smb: \>
> 
> When I connect to the "test" share I get the "tree connect failed:
> NT_STATUS_BAD_NETWORK_NAME":
> [r...@duck cache]# smbclient //DUCK/test -U dominic
> Password:
> Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1]
> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
> 
> The permissions on the /tmp and /test folders are the same:
> 
> drwxrwxrwt 2 root root 4096 Dec 27 21:35 test
> drwxrwxrwt 4 root root 4096 Dec 28 04:02 tmp
> 
> There are no complex acls on them either:
> 
> [r...@duck /]# getfacl tmp
> # file: tmp
> # owner: root
> # group: root
> user::rwx
> group::rwx
> other::rwx
> 
> [r...@duck /]# getfacl test
> # file: test
> # owner: root
> # group: root
> user::rwx
> group::rwx
> other::rwx
> 
> I've tried getting more debug info by setting log levels to 10 in both
> smb.conf and using the -d10 parameter on the command line, but it gives me
> nothing useful in the logs or in the output.
> 
> I've been through 'The Samba Checklist'
> (http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html)
> and had no other problems.
> 
> Here is the rest of my smb.conf:
> 
> [global]
> workgroup = ORANDA
> server string = Duck
> passdb backend = ldapsam:ldap://localhost/
> pam password change = Yes
> passwd program = /usr/sbin/smbldap-passwd %u
> passwd chat = *New*password* %n\n *Retype*new*password* %n\n
> *all*authentication*tokens*updated*
> unix password sync = Yes
> log level = 10
> log file = /var/log/samba/log.%m
> load printers = No
> printcap name = /dev/null
> disable spoolss = Yes
> add user script = /usr/sbin/smbldap-useradd -m "%u"
> delete user script = /usr/sbin/smbldap-userdel "%u"
> add group script = /usr/sbin/smbldap-groupadd -p "%g"
> delete group script = /usr/sbin/smbldap-groupdel "%g"
> add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
> delete user from group script = /usr/sbin/smbldap-groupmod -x "%u"
> "%g"
> set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u"
> add machine script = /usr/sbin/smbldap-useradd -w "%u"
> logon script = login.cmd
> logon path = \\%N\profiles\%U
> logon drive = H:
> domain logons = Yes
> os level = 127
> wins support = Yes
> ldap admin dn = cn=admin,dc=oranda,dc=internal
> ldap delete dn = Yes
> ldap group suffix = ou=Group
> ldap idmap suffix = ou=Idmap
> ldap machine suffix = ou=Computers
> ldap passwd sync = Yes
> ldap suffix = dc=oranda,dc=internal
> ldap user suffix = ou=People
> panic action = /usr/share/samba/panic-action %d
> admin users = dominic
> hosts allow = 192.168.10., 127.
> hosts deny = ALL
> printing = bsd
> print command = lpr -r -P'%p' %s
> lpq command = lpq -P'%p'
> lprm command = lprm -P'%p' %j
> use client driver = Yes
> 
> This has had me stumped for 3 days straight now and I don't know what else I
> can try. Samba just isn't giving me any more clues.
> 
> I've found lots of other posts like mine through google with no replies to
> them. Does anyone have any ideas of what to do next?
> 
> I would greatly appreciate if someone could point me in 

RE: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME

[Robert Mortimer]

 
> Hi,
> 
> I am running samba 2.2.12 on Freebsd 4.3, on an
> internal network, with no firewall.  I have a very
> simple smb.conf.  Here are the relevant entries:
> 
> [global]
>workgroup = Workgroup
>socket options = TCP_NODELAY
>printing = bsd
>guest account = nobody
>hosts allow = 192.168.1.0/24
> 

Where in the section above is the host name for your 
SAMBA machine? Do you have a line like
  
netbios name = HOTSTUFF

If the machine has no name I guess that may be why you
can not find it.



>  [tmp]
>comment = Temporary file space
>browseable = yes
>writeable = yes
>path = /temp
>read only = no
>public = yes
>create mode = 0777
> 
> /temp is owned by nobody, and has read / write
> privileges for everyone.
> 
> My windows machines can see the samba server, but they
> cannot browse to it.
> 
> When I run 
> 
> [EMAIL PROTECTED] smbclient //machinename/
> 
> I get the following output:
> 
> added interface ip=192.168.1.151 bcast=192.168.1.255
> nmask=255.255.255.0
> Password:
> Anonymous login successful
> Domain=[WORKGROUP] OS=[Unix] Server=[Samba 2.2.12]
> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
> 
> Help appreciated.
> 
> Charlie
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba
> 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba