similar to: NT_STATUS_BAD_NETWORK_NAME

Displaying 20 results from an estimated 500 matches similar to: "NT_STATUS_BAD_NETWORK_NAME"

2012 Feb 20
11
btrfs-convert processing time
Hi, I''m trying to convert two ext4 FS to btrfs, but I''m surprised by the time needed to do that conversion. The first FS is on a 500GiB block device, and btrfs-convert is running since more than 48h : root 1978 25.6 47.7 748308 732556 ? D Feb18 944:44 btrfs-convert /dev/vg-backup/backup The second is on a 340GiB block device, and the processing time is similar
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
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
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
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 =
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
2009 Dec 29
1
FW: tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Hi Dominic, I wanted to wait for the original mail to pop up on the list. But somehow it did not appear yet. So while the problem seems to be solved meanwhile, I wanted to comment on the relevant log portion below (see inline): Dominic Gamble wrote: > Hi Michael, > > As I mentioned, here is the full log file. > > Thanks for your time. > > Cheers, > Dominic. > >
2010 Jul 06
0
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Hi all, I have deleted and reinstalled samba 3.4.0 and then I got a failure at starting samba .I guess that was because of lacking of smb.conf ( I have deleted it manually and it didn't install it back) And I have decided to install samba4 which gave me also the same failure so I have again installed samba 3.4.0 and I found out an smb.conf file from
2005 Jul 07
0
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Hello everyone! I've searched the archives and seen this problem crop up a couple of different times. None of the solutions I've found seemed to have worked. Here's the synopsis: I've recently installed FC4 and samba shares for home directories should work right out of the box. Default settings, etc... I get this error: sohmc@bart:~$ smbclient //127.0.0.1/sohmc added
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
2007 Jan 15
0
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Dear all, Since this morning my samba server is acting weird. I have searched on the web for response on how to resolve this, but could not find any solution, and only little relevant information. I need your help. My samba server version is 3.0.9-1.3E.10 running on RedHat ES 3 (2.4.21-47.0.1.ELsmp) I wanted to add a share to my smb.conf. Made a copy of it, added the share and restarted smb.
2007 Feb 28
0
How to get rid of: tree connect failed: NT_STATUS_BAD_NETWORK_NAME ?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Now the network is unaccesible, i am not able to print from this machine, and no-one has acces to the music, movies, artwork and executables which are stored on this machine... What causes this, and how to change it? - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.18.2-34-default x86_64 Huidige
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:
2006 Aug 02
0
samba-3.0.23a: NT_STATUS_BAD_NETWORK_NAME and swat: no log out button (?)
Hello! I have two questions regarding SWAT. 1) Where is the logout button? 2) How can I set administrative privileges for a user ? ---------------------------------------------------------------------------------------- And a problem with samba: I run gentoo linux, the test version and since my last upgrade to samba-3.0.23a I can't access my server. Until yesterday WindowsXP from another
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
2001 Mar 09
1
SAMBA 2.0.7 supports solaris 8
I want to find out that is SAMBA 2.0.7 supports Solaris 8? Please let me know. Thanks, Vijay
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