similar to: [Fwd: Re: What happened to this list?]

I have just implemented an NT Domain using samba 3.0.4 on Slackware 9.1, a very simple LAN with 4 or 5 clients. Clients: Win XP Pro. Everything looks OK so far, apart from this issue: I create machine accounts for existing client machines using their existing names ... works fine, they can join domain. Except that we want to rename the existing machines using a new consistent format (client1,

I have a couple of questions about pdbedit. I am having trouble using pdbedit in shell scripts. First, on a freshly installed system with no-one in the tdbsam database, trying to add multiple machine accounts via a loop construct in a shell script fails with a message that the database can't be found/doesn't exist. I then added root manually just to get the system going, which solves

Having some major troubles with smb and making it a PDC For 2 weeks now I have been testing, and retesting. At one point I had it all working except for password changing. Has anyone goten Samba 3.0.4 to work correctly as a PDC with an smbpasswd back ground (not pam or ldap). If so could you please send me a working copy of your SMB file (only core components needed, no need for shares or

Hi Folks, I would really appreciate any words of wisdom people here could provide me. I have Samba 2.2.7a, as shipped with RH 9.0, running on a server, supporting about 25 W2k clients. The linux kernel is running in SMP mode to use the Hyper-Threaded Pentium-4 CPU. I have tried to create the simplest SAMBA setup possible, so have no LDAP, ACLS, etc. The 25 w2k clients are all architects

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi all, I got a new assignment today. My task is to install LDAP instead of NIS in our network, consisting of Solaris, Linux and W2k. Our actual setup is like this: Accounts are kept on a Solaris-server and served with samba and NFS. Two PCs serve as PDCs, running NOT samba on unix but a real W2k. Special MS-PAM-modules on the Solaris-server are used to synchronise accounts and passwords with

James: (Again someone correct me if I'm wrong) PAM allows local access to the Samba machine as well as authenticating Samba users. Winbind *only* allows for Samba access. This is why I chose *not* to use PAM in my setup. I don't want normal users to have local logon access to *MY* servers. <evil grin> With Winbind, you don't need PAM at all. If you're planning on

Hi Igor, Once again, thanks for keeping up with me. I have been migrating my master ldap server to 2.1 version so to keep it the same with the PDCs version of LDAP. Now they are the same. I have rectified such that "wbinfo -u" on both sides worked now. I am made "net rpc trustdom list" worked. It was not working before. I had to put "stuadmin = root" in the

The interesting part is that PAM nor the SMB auth plugin for Apache requires you to be a member of the domain. However, the caveat with pam_smb_auth is that you have to have a unix account for every windows user you want to authenticate. I guess the behavior I'm trying to achieve is the one achieved with the Apache plugin: 1) Doesn't require you to be a member of the domain 2)

Hi, I'm having some trouble connecting the SMB networks on two LANs that are connected over a "slow" (DSL) link: Network B: 172.16.0.0/24 Domain B: office Network A: 172.16.1.0/24 Domain A: home gate.office and gate.home are the respective networks' NAT gateways connecting to the internet over ADSL lines. The private IP spaces are connected to each other via an ipsec tunnel

Hey all, After setting up a migration server (a server which will act as a test for a Samba 3.x environment), so we can make sure our migration from Samba 2.2.x to 3.x goes as smoothly as possible, I've hit upon a problem, now I am not sure whether this is the fault of Samba (my configuration) or NT4 or whether this is infact designed behaviour for both/either servers. I'd like to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Date: Mon, 24 Mar 2003 09:45:11 -0800 > From: "Raj Saxena" <rajan@ipisland.com> > To: <SAMBA@LISTS.SAMBA.ORG> > Cc: steven_hatch@yahoo.com > Subject: [Samba] A samba document manual project > Message-ID: <002501c2f22d$1f016370$6501a8c0@ipisland.com> > In-Reply-To:

Hi, I apologise in advance for the length of this email and for the possible newbie-ishness of it but I'm having some trouble trying to get my head around the Windows NT "Local Groups" concept and was wondering if anyone on the list could shed some light on the subject. I have an NT4 BDC which I am trying to migrate to a Samba domain member server (I would like to migrate the

Greetings, I've been debugging the following scenario for some time now, and I'm slowly runing out of ideas. If anyone would suggest anything helpful... I'd be grateful. Anyway, here's the setup: windows 2003 AD domain running in 'windows 2003 native' mode + a few Solaris 8 servers with Samba 3.0.0. All sambas have computer accounts in windows' domain, and have

Like many, I administer multiple LANs connected together using NT trust relationships. This was implemented about 4 years ago. I now have the occasion to consider performing this same task again, but this time, I would like to implement it solely through samba - no Microsoft PDCs anywhere. I have read documentation on samba.org regarding NT-style trust relationships and am now wondering, can I

> > On 4 Aug 2016, at 14:20, Ben Lippmeier <benl at ouroborus.net> wrote: > > >> On 3 Aug 2016, at 12:38 PM, Dean Michael Berris via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi Everyone, >> >> Just trying my luck here but are there others in the list lurking that down under in Sydney? I'm happy to make something happen if

Hi Igor, I am no samba expert. Reading your email produce 2 thots. 1. If I have not read wrongly, you DID NOT managed to reproduce my scenario cos when you joined Domain A , login as user of DomB , you got the expected result, the Domain B's sambahomepath and drive gets map to the user B. Mine result was this: I joined Domain A, login as user of Dom B, I did NOT get Domain B's

Just a simple off topic but list related comment: The message headers in postings from this list seem to encourage off list responses since the list address only appears in the "To" header. The normal action when responding (at least by the uninitiated) is to simply reply which in many cases sends the response to the address in the "Reply-to" header if any or to the

In the headquarter of my Institution we have some 300 windows PCs, distributed like this: domain1: 100 clients in a consolidated samba 3.0.5-2 domain (RH 9.0) domain2: 20 clients in an incipient samba 3.0.14a-2 domain (FC4) 80 clients to be joined to domain2 without domain: 150 clients beloging to some three workgroups We outsourced the deployment of a LDAP server and we are in the

Hi, Here is my scenario:- 1. I got 1 LDAP server with two domains (A & B) configured to it. 2. Both domain PDCs are fully trusted to one another. I did the "trustdom establish" both ways. 3. I have 1 XP client that has joined Dom A. The login bar can allow you to login to 2 domains. 4. I can managed to login to both domains. 5. I got all the sambaHomePath and home drive