similar to: Moving SAMBA PDC to another machine.

hello list, I had to move a samba pdc server to a new hardware plattform. So I copied the whole files of the samba shares. And additionally the following config files: /etc/passwd /etc/group /etc/smb.conf /etc/smbpasswd /etc/secrets.tdb The new server has the same name and ip address like the old one. But now, the w2k users can no more download their profiles. (w2k says something like access

> -----Original Message----- > From: Andrew Bartlett [mailto:abartlet@samba.org] > > passdb backend = ldapsam:"ldaps://ldap1 ldaps://ldap2" > is what you want. This helped me a little bit forward. I suggest to add this line also to samba-pdc help. But still I ran into problems. I fixed the passdb lines on PDC and BDC. If the second server (on PDC slave-ldap and on BDC

Hi all, I am trying to install samba 3.0 pdc alongwith winbind on the same machine, the objective is to allow Squid to use ntlm_auth for samba users existing on the same machine. If I move squid to another machine, join this machine to samba3.0 domain and then use wbinfo, everything works fine. But when I install squid on the same machine as samba and then try to use wbinfo it fails. I get the

I read in the Samba HOWTO Collection that every machine in the domain needs to have a corresponding UNIX account. Does this mean whenever I add a machine to the network, I must create a UNIX account for each one?? Am I supposed to create Unix accounts for my users as well? Doesn't this defeat the purpose of using a centralized authentication backend such as LDAP or MySQL?

Howdy :) I just have a little question regarding PDC and domain logons... my setup is working nicely with roaming profiles, logging onto the Samba 2.2.3 PDC, but I find that I am still able to find the server from a new machine, supply a user/password and access the shares on the server. Is this correct operation? Surely allowing this completely defeats the object of machine accounts and a

Hello everyone. As far I know, all Microsoft domain are identified with a SID. It is used for authorization, for example in the file ACLs of the users' files. Before using it, this SID is generated at random. This SID resides in the PDC, When Samba is acting as PDC, where lives this SID? (I suppose that in a file). I'm asking this because I'm thinking in a backup procedure for my

According to the documentation on setting up Samba to be a PDC. It says that you have to enable encrypted passwords for it to work! Now for Samba with PAM to work the documentation says that you can't have encrypted passwords enabled! So does that mean that I can't set up Samba has a PDC and use PAM to authenticate the users! Reason I ask is I did have Samba set up as a PDC with 3

Ver smb 2.2.7a Managers, I am having trouble configuring samba as a domain member authenticating to a win2k domain controller. All other aspects seem to be functioning but samba is generating a log event when attempting to connect to the password server as follows. Machine NDEVDC1 rejected the tconX on the IPC$ share. Error as follows: NT_STATUS_ACCESS_DENIED Any help is appreciated. Aaron

I've got two sites that I am planning a Samba3/LDAP implementation on, each will have its own local server. The problem is that I want to implement in my local office first, which is not the site that eventually will be the 'master' site. Sometime later when the proper master site comes online, I'd like to demote for lack of a better term, my local machine to a BDC and then

Hi, The 'add machine script' and 'add user script' is very handy in creating samba user accounts and joining machines to domain. However, the 'add machine script' needs to first create a 'unix account' in order for samba to proceed and create the necessary SID entry. This unix account is no longer used after this process(at least I have deleted it and not seeing

I have 3.0.2a (with about 75 machines/users) installed as a PDC for my Win2k users and found an oddity. (waiting for a bin version of 3.0.3 for RH8.0) All was fine before I left 2.2.8.... But now when users hit <CTL>-<ALT>-<DEL> and change the password, they get "domain not available". When they log in, they get the logon scripts to execute, and anything else I do to

Hello, I have inherited a samba-tng PDC (without ldap) that I am to upgrade to samba 3. My first attempt failed miserably. I copied over the smbpasswd and the domain SID, users were able to log in, but most were not able to load their profiles. I think I have to copy over machine IDs, but I'm not sure how to proceed. The migration section of the the howto doesn't seem to apply to

Hi, I've finally gotten my LDAP password backend up and running, and finally figured out the SID 1000/1001 thing for Samba admin. However I'm unable to join the workstation to my domain. Using any random user in the WXP dialogue, I get the "Access is Denied" error. Fair enough. Using the user with sambasid and sambagroupsid s-*-1000/s-*-1001, I get the error "The Username

Finally figured out why I couldn't login to my samba 3.0.2a PDC, I had a mismatch in one of the SID's. Now that I have that figured out my workstations crash when logging in after applying the personal settings. The error is in a window titled SAS window:winlogon.exe - Application Error with the message being instruction at 0x00450056 referenced memory at 0x00000000 the memory could not

Hi all, looking for a wee bit of help here. I've inherited 2 samba servers both running 2.2.7 Server 1, due to be pensioned off os the PDC and currently supports roaming profiles printing, home directories and an ldap service. Server 2 is the all singing all dancing new server that houses all the other directories used by our users. once we're down to 1 server the plan is to move to

Samba folks: The title maybe indulgent, but I wanted to get everyone's attention. I currently run mandrake 9.0 (FILESERVER) with samba 2.2.8 running as a PDC and file server for 20 WinXP workstations. We bought a new server to replace (FILESERVER). However, I want to install mandrake 9.2 and samba 3.0 on the new server -then I want the new server also to replace the PDC of the old

I've seen several references on the web to setting up the LDAP SAM to communicate with the LDAP server via ldapi (IPC) verses ldap (IP). This should theoretically much faster. My LDAP master is on the same host as the Samba PDC. With nss_ldap using "uri ldap://localhost" and Samba using "ldapsam:ldap://localhost/" everything works. But changing nss_ldap to use

I keep hoping for better wasy to remotely manage windows machines through samba. In the very old samba-tng there was an rpcclient that could connect to a remote machine and do various things like read/write the registry, grab event logs, etc. I could never get it to work very well and waited for a better one. The trouble is the rpcclient program in samba-current doesn't have these features.

After googling a bit, it seems that only way samba playes with active directory is with samba 3.x I'f been use samba 2.x with 'pass through' authentication and would like to get rid of the pass through auth cause it seems to cause problems. Yet, I don't know if I can trust samba 3 -- Has anyone been able to get a samba 2.x server to join a an Active Directory domain? My

I have one problem with the mapping Unix group with NT group I have 3 unix group and I want that two group are mapped with nt group "Domain Users" and one with "domain Admins" For the domain admins there aren't problem but for mapping two unix group with the same nt group. I have the necessity that 2 or plus group unix is mapped with the nt group domain user. Ciao