similar to: NT_STATUS_BAD_NETWORK_NAME

Folks, I'm trying to add a network interface card to my SUSE 9.3 box, and I'm not having much luck with a US Robotics version. What manufacturer do any of you use in your machines--either 10/100MB or GigE NIC? Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell

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

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

Hi, I've had a stable Samba-run LAN, with some active shares, for several months, with my PC and laptop also gaining access to the Internet through the Samba server. However, this morning, when I booted up my Samba server, I had no LAN--neither my PC nor my laptop could connect to any share. However, both still had access to the Internet. I confirmed that smb, named, winbindd, et al.,

One more thing I forgot to mention. The chapter calls for editing /etc/resolv.conf, but in my case it won't stay edited--it keeps getting set back to an original form (for searching my ISP) on every reboot. Thanks again. Eric Hines -------- Original Message -------- Subject: Samba-3 By Ex Chapt 3 Date: Tue, 05 Jul 2005 17:47:09 -0500 From: Eric Hines <eehines@comcast.net> To:

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]

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:

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

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

[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

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 --------- ---- -------

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

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

I've set the path for each user in pdbedit and created a login script with drive mapping etc etc The network drives aren't being mapped when I login each user: smb.conf [global] printcap name = cups cups options = raw map to guest = Bad User # include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile

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

Hi, ntsysv doesn't list the samba daemons (smbd, nmbd), and while I could use chkconfig, it appears, to add the daemons, I'd rather do this via the rcx.d links so I can understand what's going on. Eric Hines -------- Forwarded Message -------- From: Sp0oKeR Labs <spooker@gmail.com> <snip>Date: Sun, 27 Feb 2005 21:35:32 -0300 Did u try ntsysv ou chkconfig? Are you using

Actually, my problem turns out to be even more basic and foolish than that. I assumed that since the relevant Kill files were present in the ls listing, then the Start files would be, too. Nope. I had to make those soft links; when I did, everything worked properly. Eric Hines -------- Forwarded Message -------- From: Paul Gienger <pgienger@ae-solutions.com> <snip> Date: Sun, 27

# Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2005/05/29 15:30:50 # Global parameters [global] workgroup = DOM_TEST interfaces = eth1, lo bind interfaces only = Yes passdb backend = tdbsam pam password change = Yes passwd program = /usr/bin/passwd %u passwd chat = *New*Password* %n\n *Re-enter*new*password* %n\n *Password*changed* username map =

Greetings, Running FC3, kernel 2.6.9-1.667.i686, Samba v 3.0.11. I have been able to guts up Samba by adding a procedure to /etc/rc.d/rc.local, but I can't get the system to start from the /etc/rc.d/rcx.d directories. I have an smb script in /etc/rc.d/init.d that is soft-linked from the rcx.d directories, and that runs just fine when I invoke it from the command line, but apparently the

Folks, I realize this is off topic, and if anyone can suggest a better source for the question, I'd be glad to go there. Novell SUSE's support is unresponsive, however. My problem is this: I'm running 9.3 Pro on an Intel server board that has two NIC chips built in (a 10/100 and a GigE). I've since added a Netgear GigE NIC. However, every time I reboot, the NICs assigned to