similar to: netlogon problems

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:

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

Gentlemen: This is an embarrassingly basic problem; I'm obviously doing something fundamentally wrong. I'm running SUSE Professional 9.3 and Samba 3.0.13 (I'm trying to upgrade to 3.0.20b, but I get a dependency error--that's another story). My problem is this: I'm trying to set up John Terpstra's Example 1.2.1 from his Samba by Example (I told you this was basic),

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

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

>Date: Sat, 26 Nov 2005 21:39:28 -0600 >To: Craig White <craigwhite@azapple.com> >From: Eric Hines <eehines@comcast.net> >Subject: Re: [Samba] Basic Setup Problem > ><snip> >> > >> > 1) your point is valid about the password; I was following the example >> > as exactly as I could. >> > 2) there is no difference between

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

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

# 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 learning samba on SUSE 9.3 linux box. I followed the Samba "Small Office Networking" example to configure the server, but I have problem to access the share "accounts" / finsvcs until I changed the valid users from %G to @acctsdep. Here are the output from the console when I accessing the share "accounts" server01:~ # smbclient //server01/accounts -U

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

[ Rowland, i know, i need to upgrade. ;-) ] Some month ago, with a relative big bunch of fix&tweaks, i was able to put a Win10 1903 client in join to a 'NT mode' Samba domain. Now i'm trying to do the same with a 1909 version; all seems to work as before, BUT netlogon script (defined in smb.conf with: logon script = startup.bat ) simply seems does not run. No log event in

Hi, I want to set up SaMBa PDC and BDC with LDAP. I read the TOSHARG2, but don't understand something: >Samba-3 cannot participate in true SAM replication and is therefore not able to employ >precisely the same protocols used by MS Windows NT4. A Samba-3 BDC will not create >SAM update delta files. Ok, I understand until that, but: >It will not interoperate with a PDC (NT4 or

Hello, I use Samba 3 as a PDC. When a user logs in, a user-specific script is executed for him/her, as stated in smb.conf: logon script = %U.bat This is handy when it comes to do some minor tweaks, but can become pain when one have to do bigger changes. Is it possible to execute also a "machine script" (for installing software etc.), and "group script" (users belonging

Hi List, maybe i missed a hint on google, but i didn?t find a answer to following question: is it possible to cascade the logon scripts...? for example: there is a standard script for all client-pc?s called: netlogon.bat and in addition there is for some client-pc?s a additional script called by the %m switch in smb.conf kind regards Arno