similar to: [Nearly Resolved] Samba-3 by Example, Ex 2.4

I have a 2Win2k, 1Linux (server) LAN; the server is running FC3 and Samba 3.0.14a. I am unable to get both users access to their individual shares. Essentially, I'm working through the Accounting Office example (pgs 31-35) of John Terpstra's 2004 Samba-3 By Example, and I'm doing something foolish and wrong on a basic level. I can get access to, and manipulate the files in, my

I'm running FC3 with Samba v 3.0.14a, and I'm trying to implement Example 2.4 from JHT's 2004 ed. of Samba-3 by Example. I have lserver1 as my Linux box and jupiter (user annlee) and mustelidae (ehines) as Win2k boxes. ehines has access to his share (path /archive/ehines (/archive/%U in smb.conf)), but annlee does not to her share (/archive/annlee). If I add annlee as a valid user

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:

I've still not quite got things right. I'm running FC3 with Samba v 3.0.14a, and I'm trying to implement Example 2.4 from JHT's 2004 ed. of Samba-3 by Example. I have lserver1 as my Linux box and jupiter (user annlee) and mustelidae (ehines) as Win2k boxes. ehines has access to his share (path /archive/ehines (/archive/%U in smb.conf)), but annlee does not to her share

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

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

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

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 >

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, maybe it's a bug, maybe not. I added some groups in the field "valid users" in SWAT and committed my changes. After that, this option disappears. When I manually delete all groups in the smb.conf, in SWAT this option is available again. I'm running Samba 3.0.14a (SerNet). Greetings, Holger -----BEGIN PGP SIGNATURE-----

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

Sorry for the direct post.... Eric Hines -------- Original Message -------- Subject: Re: [Samba] can't connect to swat Date: Sun, 16 Apr 2006 08:51:45 -0500 From: EHines <eehines@comcast.net> To: Larry Weldon <lweldon@weldoncomputers.com> References: <02a201c66148$c8925290$0c46a8c0@jshinotebook> <1145194206.20034.72.camel@tiger.home.welcoin.com> Larry Weldon

John, This isn't entirely fair. There are three kinds of newbies, and I'll say for the purposes of this thread that newbies also may be new to Linux/UNIX, not just to Samba: the first kind is lazy and goes running for help at the drop of a bug and doesn't bother to read the docs first. This kind deserves your rant. The second kind doesn't know documentation exists--they

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

Greetings, I have a technical question about update_va_mapping_otherdomain....... I have two components: a C program linked against libxc and a kernel module which performs the following simple sequence of events from domain zero: 1. Pause guest (unprivileged) 2. Grabs the PTE associated with a random (but present) page within the guest''s kernel''s address space (using a

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 am having the same problem. Did you figure out how to do this? Any help in how to remove stale WINS entries from Samba would be greatly appreciated. Cheers, -farshad

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