similar to: Can't Get to Shares

I'm running SUSE 9.3 with Samba 3.0.21a, but I can't connect to some shares, even though I can connect to others just fine. I get into my home share, netlogon share, printer shares, etc, but three shares all get me the same answer in response to <smbclient -L //server/share>: I get back an NT_STATUS_BAD_NETWORK_NAME error. All users are correctly in passdb, passwd, etc. I have

Folks, I'm having a problem connecting to some shares, and not to others. I'm running SUSE 9.3 and Samba 3.0.22pre1 with a Win2k PC on one subnet and an XP laptop on a separate subnet. The problem is that with three shares out of eight, I get a "tree connect failed: NT_STATUS_BAD_NETWORK_NAME" error message; I get appropriate accesses to the remaining five. Googling the

List, I'm having trouble accessing shares, and I'm getting conflicting indications on whether I've successfully joined the domain with my PC and Samba server (which may bear on the share problem). I really could use some help; I've not been able to recognize anything in the docs or via Google that helps. I'm running SUSE 9.3 and Samba 3.0.21a, and I'm trying to

Hi! All: How can i get domain members of a domain group? I tried getent group, but only get the gid infomation. There isn't member infomation at the last field as local group is. Thanks for your help. Best, LatrellFrom eehines at comcast.net Fri Dec 9 01:43:02 2005 From: eehines at comcast.net (Eric Hines) Date: Fri Dec 9 01:34:48 2005 Subject: [Samba] netlogon problems In-Reply-To:

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

And my last post on the matter. This is why I won't do business with USR again anytime soon. They couldn't even be bothered to tell me this on my first query to them. Eric Hines >X-Originating-IP: [63.169.70.144] >Date: Tue, 20 Dec 2005 18:44:48 -0500 >From: usr_amr_eng@aqinc.com >Subject: In response to your USRobotics technical support questions, >your case

Folks, ><snip> >Folks, > >I'm running SUSE Pro 9.3 with Samba 3.0.13, and I have LAN with 2 >subnets. The problem (or the symptom; I may actually have two problems) >is that I can't get into some of the shares from my Win2k box (one subnet) >or from my XP laptop (other subnet). The directory structure is > /data > /data/accounts >

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

>Folks, > >I've gone and screwed something up, and I cannot add users to passdb database. > >I've set passdb backend to tdbsam in my [global]. I've added users >to passwd (useradd -m <user>). However, when I try to add smb >users, I get errors and failures to add the users. > > smbpasswd -a root (and supply the password in response to >

Folks, I'm running SUSE Pro 9.3 with Samba 3.0.13, and I have LAN with 2 subnets. The problem (or the symptom; I may actually have two problems) is that I can't get into some of the shares from my Win2k box (one subnet) or from my XP laptop (other subnet). The directory structure is /data /data/accounts /data/finsvcs and the shares are accounts and

Dumb question time; I can't find the answer in the Samba-3 or HOWTO docs: how do you add users to the passdb.tdb (tdbsam's db)? Is pdbedit the only way? I ask because the Chapt 3 Samba-3 example has passdb = tdbsam in the samba config file, but the instructions for adding users are to use useradd and smbpasswd, which leave passdb.tdb empty (except for root--I have no idea how that

I'm currently running SUSE Pro 9.3 with samba-3.0.13-1.1-SUSE, and I'm trying to upgrade to 3.0.20b. When I try to rpm -Uvh samba-3.0.20b and samba-client-3.0.20b, I get the failed dependency "samba = 3.0.13 is needed by (installed) samba-vscan-0.3.5-37.2." How do I resolve this dependency? I'd prefer not to force it in, as that often generates more problems than it

Folks, I'm running a Samba server (SUSE 9.3 and Samba 3.0.22pre1) on a 2-subnet LAN, with a Win2k PC on one subnet and an XP laptop on the other. When I boot up the server and then the two windows devices at the start of a day, everything comes up just fine, the server appears in Network Neighborhood and in Explorer, and I have access to my shares normally. However, my problem is this:

I'm at my wit's end on this, and I hope someone can help. I'm running SUSE Pro 9.3 with Samba 3.0.13, and I can't get connected to my shares properly. Valid users (e.g., for [accounts]) is set to %G, and I've confirmed that the users are members of the owning groups for the shares and that they are in the passwd and smbpasswd files with the same passwords as on the Win2k

Folks, I'm having trouble connecting to my Samba server. The immediate symptom is that I cannot see my Samba server in my Windows Network Neighborhood, and so I cannot connect to it to check my share connections. I'm running SUSE 9.3 on the server, which is running Samba (3.0.22) , a dhcp server (which seems to be running correctly--everyone gets an address when they ask for one),

Folks, I'm trying to achieve control over who logs into a share according to the group to which that person belongs, but with no luck. I'm running SUSE Pro 9.3 and Samba 3.0.13, with a Win2k machine on one subnet and an XP laptop on another subnet. In all cases, the user, instead of getting into his share transparently, gets invited to log in, and then the login is rejected.

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

I have just recently installed Samba. I have two WinXP Pro machines networked to a FreeBSD 5.4 computer. The Printer is connected to one of the WinXP machines currently. This is the output of the 'smbclient' command. smbclient -U user-name -L winxp Password: Domain=[winxp] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment ---------

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

H! I am getting such messages in log.samba: ../source4/nbt_server/dgram netlogon.c:198(nbtd_mailslot_netlogon_handler) nbtd netlogon handler failed from 192.168.0.125:138 to DOMAIN<1c> - NT_STATUS_BAD_NETWORK_NAME What means that <1c>? seems like special char... There are two domains sharing one network - one - NT-style named DOMAIN and the second, AD, named DOMAIN2 (samba