similar to: logon requests on the BDC

Hi, i'm probably not the first but i have found no concrete information about my problem... lots of information, nothing helped.. :S so, here's the thing.. i'm running a samba-3.0.22-13.16 server on SLES 9 kernel 2.6.16.21-0.8-default as an nt domain controller, there was a migration to Linux for the workstations so i had to implement WINBIND + PAM_MOUNT. after searching for the

Hello, I did the steps described below and I have a problem with machine RIDs. When I first join a machine, samba adds to my sambaDomainName ldap entry a sambaNextRid attribute with a value of 1000. Now samba uses this value (incremented each time) to give its RID to the machine. This is going to be a real problem as my current samba computes RDIs as 1000+2*UID. FWIW I'm using

Dear List, we've the following setup: login: PDC (Samba + Master LDAP with Slave LDAP) appserver: BDC (Samba + Master LDAP with Slave LDAP) fileserver: Samba domain member server Everything is running with Samba3 and OpenLDAP2 The following problem: when the PDC is not available (test shutdown) the clients can log into the domain (netlogon- script is running from BDC), but the fileserver

Hello, I have a centOS 5.5 box acting as as a PDC with samba 3.4.9 and openldap 2.4.22. Then I joined the domain with a centOS box (samba 3.4.17) which hosts the homes and profiles. I have no problem with XP clients. I can join a windows 7 client to my domain but it is unable to load the profile when logging in. See below a level 2 log.smdb from the file server when I log in with a domain

With samba 3.0.34 I have the issue described here http://webui.sourcelabs.com/samba/issues/5535 That is "smbpasswd -a joe" gives RID=2*UID+1000 while "net rpc user add joe" gives the value of the sambaNextRid attribute of the sambaDomainName LDAP entry. Also "smbpasswd -am machine" gives RID=2*UID+1000 while directly joining the domain gives RID=sambaNextRid This is

Hello, I'm upgrading my samba installation from 3.0.34 (FreeBSD 6.4) to 3.4.x (CentOS 5.5) from SerNet. I have LDAP based samba domain (PDC and BDC) and a homes/Profiles member server. I first upgraded my DCs to 3.4.9 with no problem. I have recently installed a new file server (samba 3.4.11 on CentOS 5.5). I have issues connecting to this server with old versions of smbclient which

>>> Ian Clancy <clancyian@cel.ie> 05/10/05 11:45 AM >>> Prakash Velayutham wrote: >>>>Ian Clancy <clancyian@cel.ie> 05/10/05 9:33 AM >>> >>>> >>>> >Prakash Velayutham wrote: > > > >>Hi, >> >>Sorry for posting again. I would really appreciate any help with this. >> >>I

I have a samba PDC with a master openldap server and a samba BDC with a slave openldap server. Replication is done with slurpd with a TLS connection and the slave ldap server has an updateref pointing to the master (I don't use ldaps). On each domain controller my smb.conf contains: passdb backend = ldapsam:ldap://localhost Now I'd like my ldap servers to reject non TLS connections

I have a PDC+LDAP as well as a BDC+LDAP in another subnet setup with a domain member in the same subnet as the BDC. From my understanding the domain member should be hitting the BDC for all authentication but watching the logs I see the PDC is the one handling it all. The BDC just sits there. Am I missing something? Here are the smb.conf for each servers: PDC: [global] workgroup = X.X.X

Hi, I have a Samba 3 PDC running with around 20 Windows XP/2K clients. The PDC and the clients are in different subnets. I recently decided to add a Samba 3 BDC in the same subnet as the clients, to give some failover and also to reduce across-switch traffic. After creating the BDC, I restarted one of the clients but don't see it establishing connection with the BDC, instead it connects as

Hi, After lots of struggle and rtfm I finally got most things running, except for 'nmblookup' and 'net getlocalsid' on the BDC. I'm not new to Samba, but plenty more to learn. Here's the setup in summary: system pdc is the PDC on subnet 192.168.0.0, running SuSE10.1, LDAP master, wins server, domain master browser, no iptables; system bdc is the BDC on subnet 192.168.2.0,

hi list&john, i read in the documention about BDCs: The domain SID has to be the same on the PDC and the BDC. In Samba versions pre-2.2.5, the domain SID was stored in the file |private/MACHINE.SID|. For all versions of Samba released since 2.2.5 the domain SID is stored in the file |private/secrets.tdb|. This file is unique to each server and cannot be copied from a PDC to a BDC; the BDC

Hi people. I have finally my PDC+BDC running with LDAP+replicaon different subnets. My doubts are simple, I want to understand a little more about BDC. My network is this: Domaine Name=DOMA Networks:NET-A 192.168.40.0/24 NET-B 192.168.50.0/24 PDC=192.168.40.2 BDC=192.168.50.2 wins server = PDC As u can see, both serves exist on different subnets,I want to

Hi, Does someone know how will all my client machines find the BDC when the PDC is stopped. Both PDC and BDC are running Samba with LDAPSAM backend replicated on both the PDC with master LDAP database and BDC with replicated LDAP database. But when I stop PDC the clients are not detecting the BDC broadcast. The replication on all domain controllers are perfect. I went as far as making BDC

Hi, Maybe this was asked many time (although can't find it on google). Let's assume 2 scenarios: 1) I've got local network where PDC and BDC are set up. PDC is working fine so the BDC is. When it's possible for any XP client to use BDC instead of PDC? I read in samba docs that if PDC is slow client can use BDC - but what does it mean slow for the client? How the client knows

Hi all, I have a BDC which uses the LDAP backend of my PDC. Unfortunately all the users who log-in in the morning and who are processed by this BDC, do not get their logon script executed. The BDC logs this error message: [2013/05/24 07:28:11.946577, 2] auth/auth.c:304(check_ntlm_password) check_ntlm_password: authentication for user [foobar] -> [foobar] -> [foobar] succeeded

I have a question about setting up a samba BDC (with a samba PDC). I am running Samba as the PDC on a small network. Other Unix boxes on the network are running with: security = DOMAIN encrypt passwords = Yes update encrypted = Yes password server = 192.168.1.5 So they make use of the PDC for smbmount and smbsh applications. The W2K box also uses Samba at the PDC. I want to set up a Redhat

Hi all, I have this question, I ve got a master LDAP server on a remote place and i want to install a PDC and a BDC and a slave ldap server in other place. Mi question is... may I force de WorkStations logging (read the information )against the BDC first than PDC, so the READ trafic goes to the Slave Ldap??? The problem is the network avoid READ traffic. In the Samba FAQ recomends that the:

Hello, I plan to update my samba-3.0.22/openldap-2.3.24 to samba-3.0.34/openldap-2.4.15 and I'm currently testing it. This is on FreeBSD. My idea is : 1) slapcat the openldap server and save the various tdb files. 2) deinstall samba and openldap and wipe out the bdb files 3) install the newer versions 4) slapadd to the new openldap server This seems to work in my test lab. During my tests I

If I configure a samba PDC and then a samba BDC, do I need a machine trust account for the BDC? That is, do I have to run "net rpc join" on the BDC? Or manually create the account for the BDC in LDAP? -- Mariano Absatz - "El Baby" el.baby at gmail.com www.clueless.com.ar