Displaying 20 results from an estimated 1000 matches similar to: "tree connect failed: NT_STATUS_BAD_NETWORK_NAME"
2005 Sep 10
2
Yum configuration and freshrpms
(Moved over from "Re: [CentOS] Why is yum not liked by some?")
>As a matter of interest, what baseurl are you using for freshrpms?
>
>
It took me a while, but I found this in my yum.conf file:
[freshrpms]
name=Fedora Core 1 - Freshrpms
baseurl=http://ayo.freshrpms.net/fedora/linux/1/$basearch/freshrpms/
mirrorlist=http://ayo.freshrpms.net/fedora/linux/1/mirrors-freshrpms
2009 Sep 06
1
NT_STATUS_BAD_NETWORK_NAME
Hi i'm trying to list the shares on my Brother HL-5250DN printer with the
smbtree command on linux but i keep getting the NT_STATUS_BAD_NETWORK_NAME
error message. I can however print to one of the shared printing services with
cups through the Device URI: smb://BRN_E1BEFA/BINARY_P1. Does anyone know what
the problem could be?
linux-wick:~ # smbtree
Password:
WORKGROUP
2002 Jun 23
2
NT_STATUS_BAD_NETWORK_NAME
What is the cause of this particular error.
# smbclient -L localhost
will either work or return this
added interface ip=192.168.0.16 bcast=192.168.0.255 nmask=255.255.255.0
Got a positive name query response from 192.168.0.16 ( 192.168.0.16 )
Anonymous login successful
Domain=[HOME] OS=[Unix] Server=[Samba 2.2.4]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
It working is an intermittent
2006 Mar 29
1
NT_STATUS_BAD_NETWORK_NAME
Hello,
I could use a bit of help with a samba install.
Installation is Samba 3.0.21c on fedora 4
No major changes to smb.conf just added a share point.
[disk]
comment = Disk shares
path =/disk
public = yes
writable = yes
printable = no
guest ok = yes
I opened my share up wide.
ls -l
drwxrwxrwx 10 bob users 1024 Mar 21 16:07 disk
I get my share
2007 Jun 09
1
smbclient error: NT_STATUS_BAD_NETWORK_NAME, on shared foler with a Chinese name
Hi folks,
I am trying to access the shared folders on a Windows XP PC from a Linux (FC5) PC using smbclient.
Linux config info:
$ locale
LANG=en_US.UTF-8
$ rpm -q samba
samba-3.0.24-6.fc5
smb.conf:
[global]
dos charset = CP936 <--- Simplified Chinese
unix charset = UTF-8
display charset = LOCALE
Now, here is the problem:
2009 Dec 28
1
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
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"
I'm
2005 Jul 08
1
fwd: tree connect failed: NT_STATUS_BAD_NETWORK_NAME
I sent this out yesterday. Can anyone offer any advice? I'm really at a
loss on what to do.
thanks!
----- Forwarded message from Mike Soh <sohmc@cs.umd.edu> -----
From: Mike Soh <sohmc@cs.umd.edu>
To: samba@lists.samba.org
Subject: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Date: Thu, 7 Jul 2005 08:27:33 -0400
User-Agent: Mutt/1.4.1i
X-Spam-Status: No, score=-2.6
2002 Jun 20
1
NT_STATUS_BAD_NETWORK_NAME - Samba 2.2.5
[spstarr@coredump]# smbclient //coredump/ -U spstarr
added interface ip=192.168.10.2 bcast=192.168.10.255 nmask=255.255.255.0
Password:
Domain=[SH0N.NET] OS=[Unix] Server=[Samba 2.2.5]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Yet, if I do smbclient -L coredump -U spstarr, it displays the list of
shares!
I've never seen this before and I'm not sure why this is occuring, When
2007 Aug 29
1
samba-error: tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Hi everyone!
I'm getting mad: On a running debian-edu/skolelinux 3 with samba
3.0.24-6etch4 my win clients lost their server-shares during work and
can't get them back. Tried smbclient
and got:
tjener:~# smbclient -U frank -L tjener
Password:
Domain=[SKOLELINUX] OS=[Unix] Server=[Samba 3.0.24]
Sharename Type Comment
--------- ---- -------
2013 Jun 05
1
NT_STATUS_BAD_NETWORK_NAME for Windows Server 2008
Hi,
Our smbclient calls have started failing on connections to Windows 2008 AD servers. (Previously there were only Windows 2003 Servers, so we had no issues.)
Domain=[INTRANET] OS=[Windows Server 2008 R2 Enterprise 7601 Service Pack 1] Server=[Windows Server 2008 R2 Enterprise 6.1]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Is this post [ http://serverfault.com/a/303483 ] correct when
2008 Aug 07
1
smbclient failed --> NT_STATUS_BAD_NETWORK_NAME
I make all steps in the guide:
http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/install.html#id2546028
but command (exetuded in the same computer where is samba):
smbclient //fc9/tester -Utester%test
gives error:
Domain=[DZTI] OS=[Unix] Server=[Samba 3.2.0-17.fc9]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
The user tester have been created by commands:
useradd tester
smbpasswd -a
2008 Mar 10
1
NT_STATUS_BAD_NETWORK_NAME
I am trying to run Samba 3.0.24-11.fc6 on Fedora Core 6. I've run across
two problems that are keeping me from being successful.
1. IPTables. Even when I configure it through Webmin to not run at
startup, it does anyway. I consider this a minor problem, at least for now,
although I wouldn't mind some input on how to configure it to allow Samba.
2. Access to shares. We are running
2005 Feb 01
1
gcc, libkrb4 problem
I'm trying to recompile the source RPM from the FC3 version of cvs
(http://ayo.freshrpms.net/fedora/linux/3/i386/SRPMS.updates/cvs-1.11.17-4.src.rpm),
as the version shipped on RHEL/CentOS/etc has a known bug (version
1.11.2-unix "cvs watch on" doesn't work).
The initial configure is failing with this obscure error:
configure:2257: checking for C compiler default output file
2006 Jul 31
2
NT_STATUS_BAD_NETWORK_NAME
Hello,
I installed samba 3.0.23 on Fedora Cora 4 and I configured it with this smb.conf file:
[global]
dos charset = UTF-8
workgroup = OAF_ADMIN
server string = OAF Samba PDC Server
passdb backend = tdbsam
username map = /etc/samba/smbusers
password level = 1
log level = 13
log file = /var/log/samba/log.%m
max log size = 50
2005 Jun 18
2
Yum repository info
Hi All
Would like to know where I could find repo info to be able to install
frozen-bubble and/or supertux please.
Thanks in advance,
Phil
2008 Dec 18
6
how to install yum by apt
Hi all!
Becaule i heard that the apt was great,i wanted to try it.And when i tried to update my system,the yum faid,i installed the apt which came from dag repo by yum. After that i did:sudo apt-get update and sudo apt-get upgrade.There are some problem and i did as apt suggested:sudo apt-get --fix-broken install.Then apt said should remove 11 softwares insclude yum.I thougt even i removed the
2009 Aug 29
3
how to install rrdtool, if it keeps failing?
Hi all,
I'm trying to install rrdtool on CentOS 5.3 x64, but it keeps failing
with dependency problems:
root at pluto:[~]$ yum install rrdtool*
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* freshrpms: ayo.uk3.freshrpms.net
* rpmforge: ftp-stud.fht-esslingen.de
Excluding Packages in global exclude list
Finished
Setting up Install Process
Parsing package
2004 Dec 01
0
Can not connect to share "NT_STATUS_BAD_NETWORK_NAME"
I have Suse 9.1 + Samba 3.0.9 + winbind joined to a Windows
2000 AD domain "MyCompany". Yesterday for some unknown
reason (appears to be Win2K issue) connections to Samba and
the ability to browse the domain "MyCompany" from Win2K/XP
workstations failed but connections to the public share
offered by the Win2K server were OK. Also, all Win98
workstations and were unable to
2008 Apr 15
0
diagnosing cause of NT_STATUS_BAD_NETWORK_NAME error
I'm trying to find out why I am unable to access public shares on host
mythbe (from host mythbe) due to a NT_STATUS_BAD_NETWORK_NAME error.
I am able to access home shares. I've checked all of the host setup
issues I know about (smb.conf, directory permissions, iptables,
selinux) but I don't see any problems. Can anyone spot a problem or
suggest where I could investigate? Below is
2004 Aug 09
0
Error 4617: SMB connection failed & NT_STATUS_BAD_NETWORK_NAME
Hi folks,
I'm trying to access a share on a RedHat 9 server from a Fedora Core 1
workstation. Here is the environment (pretty vanilla), the error I'm getting,
and what I've done to try hunt down the problem.
Server, 192.168.1.100, has a share of /home/users/herman
Workstation, 192.168.1.101, has a mount point of /home/herman/serverdata
smb.conf on server has
[global]
hosts deny =