similar to: Two Locations, One Domain

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 Dirk, thanks for your reply! I definatly want to go down the BDC route so that I always log on to the nearest server. The link between the two isn't really an issue - both have a DSL connection to the internet. I started by modifying my smb.conf files so that each server is a local master for their subnet, but only the uni box is domain master. After fiddling with the 'remote

smbldap-tools in a working environment suddenly unable to add or modify users. smbldap-useradd kenh Use of uninitialized value in die at /usr/lib/perl5/vendor_perl/5.8.6/Convert/ASN1/_decode.pm line 111. Perl debug trace [root@steel ~]# perl -d /usr/sbin/smbldap-useradd jimh Loading DB routines from perl5db.pl version 1.28 Editor support available. Enter h or `h h' for help, or `man

Hi. I'm having a helluva time trying to replace my Samba PDC machine with new hardware, and I'd really appreciate some pointers about how I should be doing it. I'm sorry, I wrote a lot of detail in this email - trying to mention everything that might be relevant. Here's the detail: I've a perfectly functional PDC running on older hardware under RedHat 9 and Samba 3.0.2.

Hi, I'm trying to setup samba 3.0.14a as domain member on AIX 5.3. My test environment is: - PDC and ldap master on RH8.0 (samba 3.0.14a, openldap 2.1.29) - Ldap slave on FC3 (openldap 2.2.13) - Samba domain member on FC4 (samba 3.0.14a) - XP clients - and Samba domain member on AIX 5.3 (samba 3.0.14a) This is what I did: - Compiled samba ./configure --with-fhs --with-quotas

When I took over as the IT guy in September, there were 2 separate locations with different domains each managed by a SBS 2003 machine. The connection between them was an OpenVPN tunnel. The network was fine and one could see 2 domains in the network. Local and Local2 are working names. From a workstation on Local one could see Local2 in the Microsoft Windows Network, and vice versa from Local2

I am hoping someone can help here. I noticed a really odd issue. WINS resolution doesn't seem to work between my PDC and BDC, both Samba 3.0.14a boxes running on Debian. I have nsswitch.conf configured properly, I think. Here are the nsswitch.conf settings. PDC: hosts: files dns wins BDC: hosts: files dns wins On the BDC, I have the parameter wins server = 192.168.0.2, the address

Este correo no es de yanier ----- Original Message ----- From: <samba-request@lists.samba.org> To: <samba@lists.samba.org> Sent: Wednesday, May 11, 2005 1:18 AM Subject: samba Digest, Vol 29, Issue 14 > Send samba mailing list submissions to > samba@lists.samba.org > > To subscribe or unsubscribe via the World Wide Web, visit >

Hello everyone! I've searched the archives and seen this problem crop up a couple of different times. None of the solutions I've found seemed to have worked. Here's the synopsis: I've recently installed FC4 and samba shares for home directories should work right out of the box. Default settings, etc... I get this error: sohmc@bart:~$ smbclient //127.0.0.1/sohmc added

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

Hi there, I have a Samba PDC and BDC migrated from NT4 using ldapsam with an interdomain trust to a 2k3 domain. The trust is established both ways and was made from the pdc. Using samba 3.0.14a-sernet on Suse 9.1 The trust is working. I can pull users from the trusted domain and apply them to acls on my samba DMS. Winbind adds the idmap entry correctly. What is not working, is authentication from

Hi, I just can't seem to get winbind to work on my BDC. I'm using FC3 and samba 3.0.20rc2. My PDC is RHEL4 running Samba 3.0.14a. / Openldap. I can join the BDC to the domain successfully using "net rpc join..." , but when i enter wbinfo -t to check the trust relationship i get checking the trust secret via RPC calls failed error code was (0x0) Could not check secret I

I am trying to share a directory with samba-3.0.14a and FC4. readable and writable to everyone. The directory is /data/public : 2777 root:root This is my smb.conf: [global] workgroup = HOMENETWORK server string = Samba Server security = SHARE hosts allow = 127.0.0.1, 192.168.0.0/24 hosts deny = 192.168.0.1/24 [public] comment = Public Stuff

Hi, I have an old system running Samba 3 with default passwd backend for about 30 users. Not I set up a new Samba 3.0.14a with mysql backend on another machine. I'd like to migrate the users from old system to the new system! I read through the official Samba HOWTOS and googled, but no useful concept of migration found. At the weekend I tested the following concept: - Configure the new

hi everyone, I've been subscribed to the mailing lists for about 18 months to 2 years but have never had the opportunity to post. One of our clients has a box that is a 3Ghz Pentium 4 running FC1 and 512 MB of memory. An upgrade was performed to FC4 [2 make use of ACL's]. We haven't yet started to implement ACL's [or made any changes to the Samba configuration]. The problem we

Hi list, This is driving me to distraction. I have installed the 3.0.14a RPMS on SLES8, and am following chapter 9 of the 'By Example' documentation, to migrate from an NT domain to a Samba domain backed by LDAP. I have followed the instructions up to the point where I enter: net rpc join -S pdc_it -U Administrator%password Unfortunately, this responds with: Creation of workstation

Hi, Hoping you can help. I've updated my samba server (PDC) from 3.0.10 to 3.0.14a as part of updating from FC3 to FC4. I now find I cant see inside any of the shares, even though I can see the share names themselves and the directories are quite readable to Linux processes. So, e.g. I can see that I have a share "Users", but not the contents of it. With one exception all shares

We have SuSE SLES9 servers with LDAP master/slave replication (24 replications/BDC's) All working fine -joining domain etc. The problem I am having is PC's at remote sites (BDC) with a local replica (OpenLDAP) periodically change the sambaNTPassword/sambaLMPassword on there own and write to the local LDAP server and do NOT follow the referral to the master. I have written scripts to

Additional Info... I am beginning to think that a file called 'secrets.tdb' might be what I am looking for. Inside that file is something mentioning SID. Of course, it also mentions the name of the PDC. If that is the file I am supposed to copy over. Then it is done. However, I still need a little more input for setting up a Samba BDC. With a Samba BDC, should I leave the

Hi. Can anyone give me some help on migrating my Samba PDC from old hardware to a new box? Old hardware is running RedHat 9, with Samba 3.0.2a-1. New hardware is running Fedora Core 4 with Samba 3.0.14a-2. Old (fully working) PDC is using tdbsam backend for passwords. For simplicity, I'd like to do the same on the new one, although I could also move to LDAP it that's what's