similar to: Please adwise on classicupgrade process

Hi Andrey > Greetings, All! > > I'm still on the topic, but probably I read too much stuff lately and can't > have my head set straight. > > Situation: NT4 domain, LDAP+Samba 3.6, running under Ubuntu 12.04. > The machine is also a network gateway and access (VPN/ssh) server. > > Target goals: > 1. Upgrade to Samba4 (4.1 seems possible). > 2. Convert to

Hi, someone know how to install/configure a domain for starting Windows? I have a server Dell, arrived just now, and I would like to try Windows in a Xen domain. -- Marco Natali <marco@natali.com> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

On 03/04/15 19:33, Andrey Repin wrote: > Greetings, Rowland Penny! > >>>>>> I'm trying to get the former PDC back into domain after performing a >>>>> classic >>>>>> migration. >>>>>> AD DC is running fine... if you can call it that. >>>>>> I've edited the smb.conf and nsswitch.conf as suggested in

On 04/04/15 03:29, Andrey Repin wrote: > Greetings, Rowland Penny! > >>>>>>>>>> I'm trying to get the former PDC back into domain after performing a >>>>>>>>> classic >>>>>>>>>> migration. >>>>>>>>>> AD DC is running fine... if you can call it that.

On 03/04/15 21:29, Andrey Repin wrote: > Greetings, Rowland Penny! > >>>>>>>> I'm trying to get the former PDC back into domain after performing a >>>>>>> classic >>>>>>>> migration. >>>>>>>> AD DC is running fine... if you can call it that. >>>>>>>> I've edited the

Greetings, All! I'm planning a migration to Samba 4 (for a long time, I admit, but I only recently got a promise of funds for a new server... whew...), but I'm a little in the dark on how to arrange whole process. Right now, the situation is imagined as follows: Server A: LDAP/PDC/Samba3/NAT/DHCP/BIND/everything else. Server B: New installation, x86_64, Samba4, would-be-replacement for

Hello, I'm talking about re-writing the classicupgrade HowTo since over a year now. :-) Now, after three rainy vacation days, it's finaly done: A complete and comprehensive re-write of the classicupgrade HowTo: https://wiki.samba.org/index.php/Samba_Classic_Upgrade_%28NT4-style_domain_to_AD%29 Some other mentionable documentation changes, I had done during the last week: *

I copied all the database files of samba3 as is mentioned in the wiki - The classicupgrade process <https://wiki.samba.org/index.php/Samba_Classic_Upgrade_(NT4-style_domain_to_AD)#The_classicupgrade_process> But if the winbindd_idmap.tdb file is in the folder, the errors occur. See below: Importing idmap database > ERROR(assert): uncaught exception > File

You're right, man! Sorry! My mistake! I put that file because I read in somewhere about the persistent and temporary files regarding .tdb files. The winbindd_idamp.tbm was on that list, and I think that's why I left it in the folder. :D Another doubt. For the provisioning starts, I had to comment out the line referring to the ldap backend in the smb.conf of samba3. # passdb backend =

On 03/04/15 13:05, Andrey Repin wrote: > Greetings, Ashish Yadav! > >>>> I'm trying to get the former PDC back into domain after performing a >>> classic >>>> migration. >>>> AD DC is running fine... if you can call it that. >>>> I've edited the smb.conf and nsswitch.conf as suggested in Wiki article, >>> and

Hey, man, the error: Provisioning smbldap_search_domain_info: Searching for:[(&(objectClass= sambaDomain)(sambaDomainName=EMPRESA))] smbldap_open_connection: connection opened failed to bind to server ldap://127.0.0.1 with dn="cn=Manager,dc=empresa,dc=com" Error: Invalid credentials (unknown) has been fixed. :D I modified the master password of ldap (vm) for the same that was

Greetings, Rowland Penny! >>>>> I'm trying to get the former PDC back into domain after performing a >>>> classic >>>>> migration. >>>>> AD DC is running fine... if you can call it that. >>>>> I've edited the smb.conf and nsswitch.conf as suggested in Wiki article, >>>> and >>>>> rejoined

Ok. I uncomment that line and put: passdb backend = ldapsam:ldap://127.0.0.1 Error message: Provisioning > smbldap_search_domain_info: Searching > for:[(&(objectClass=sambaDomain)(sambaDomainName=EMPRESA))] > smbldap_open_connection: connection opened > failed to bind to server ldap://127.0.0.1 with > dn="cn=Manager,dc=empresa,dc=com" Error: Invalid credentials

Greetings, Rowland Penny! >>>>>>>>> I'm trying to get the former PDC back into domain after performing a >>>>>>>> classic >>>>>>>>> migration. >>>>>>>>> AD DC is running fine... if you can call it that. >>>>>>>>> I've edited the smb.conf and nsswitch.conf as

> > Then why can the upgrade not contact the ldap server ? I dont know! :( Was ldap running on another computer before ? I installed a temporary openLDAP backend on the new host. Can you post the smb.conf from the old PDC ? the one you are trying to > upgrade from. I sent my smb.conf to your private e-mail. On Thu, May 21, 2015 at 3:08 PM, Rowland Penny <rowlandpenny at

> > Is ldap running on the computer you are trying to run the classicupgrade > on? Yes. I need to modify other files too? On Thu, May 21, 2015 at 2:39 PM, Rowland Penny <rowlandpenny at googlemail.com> wrote: > On 21/05/15 18:22, Elias Pereira wrote: > >> Ok. I uncomment that line and put: >> >> passdb backend = ldapsam:ldap://127.0.0.1 >> >

Greetings, Rowland Penny! >>>>>>> I'm trying to get the former PDC back into domain after performing a >>>>>> classic >>>>>>> migration. >>>>>>> AD DC is running fine... if you can call it that. >>>>>>> I've edited the smb.conf and nsswitch.conf as suggested in Wiki article,

On 21/05/15 16:31, Elias Pereira wrote: > I copied all the database files of samba3 as is mentioned in the wiki - The > classicupgrade process > <https://wiki.samba.org/index.php/Samba_Classic_Upgrade_(NT4-style_domain_to_AD)#The_classicupgrade_process> > > But if the winbindd_idmap.tdb file is in the folder, the errors occur. See > below: > > Importing idmap database

On 21/05/15 17:28, Elias Pereira wrote: > You're right, man! Sorry! My mistake! > > I put that file because I read in somewhere about the persistent and > temporary files regarding .tdb files. The winbindd_idamp.tbm was on that > list, and I think that's why I left it in the folder. :D > > Another doubt. For the provisioning starts, I had to comment out the line >

Greetings, Rowland Penny! >> # cat /etc/resolv.conf >> nameserver 192.168.17.4 >> search ads.ccenter.lan >> >> # host -t SRV _ldap._tcp.ads.ccenter.lan. >> _ldap._tcp.ads.ccenter.lan has SRV record 0 100 389 dc1.ads.ccenter.lan. >> >> # nslookup dc1 >> Server: 192.168.17.4 >> Address: 192.168.17.4#53 >> >>