search for: wheezytest

Note: I could simply direct boot the appropriate kernel/initrd to get the alpha1 installation going as always done in the past, but I think this should work. The Debian alpha 1 installer page says it should. Details $ sudo xm create -c wheezytest.cfg Using config file "./wheezytest.cfg". Error: Boot loader didn''t return any data! direct pygrub test run: # pygrub --kernel=/install.amd/vmlinuz --ramdisk=/install.amd/initrd.gz /BACKUP/dumpz/wheezytest/debian-wheezy-DI-a1-amd64-netinst.iso linux (kernel /var/run/xend/boot...

I did not run that command at all. I did run samba-tool classicupgrade on the DC after setting up ldap with my data. As far as I understand the provisioning of the domain is done during that process. And on the other machines provisioning must not be done, right? On 20 Mar 2015 19:35, "Rowland Penny" <rowlandpenny at googlemail.com> wrote: > On 20/03/15 18:28, Timo Altun wrote:

...ory authentication as possible auth methods. - windows machines can join the domain and communicate fine with the ad dc. Samba Version 3.6.6. Following the configs of the domain member to be (wheezy), they worked for a fresh wheezy install for the same domain: *smb.conf:* [global] netbios name = WheezyTest workgroup = MAYWEG.NET security = ADS realm = INTRANET.MAYWEG.NET dedicated keytab file = /etc/krb5.keytab kerberos method = secrets and keytab idmap config *:backend = tdb idmap config *:range = 2000-9999 idmap config MAYWEG.NET:backend = ad idmap config MAYWEG.NET:schema_mode = rfc2307 idmap con...

...sers can't access the shares (password dialog is shown, but credentials do not work). The DNS failure I get on the wheezy VM says a bit more than on the squeeze with Samba 3.5.6.: net ads join -Uadministrator Enter administrator's password: Using short domain name -- MAYWEG.NET Joined 'WHEEZYTEST' to realm 'intranet.mayweg.net' DNS Update for wheezytest.intranet.mayweg.net failed: ERROR_DNS_INVALID_MESSAGE DNS update failed! I also can't logon onto the wheezy machine with domain users...says authentication error for administrator and "Could not update ICEAuthority file...

...t; - windows machines can join the domain and communicate fine with the ad dc. > Samba Version 3.6.6. > Following the configs of the domain member to be (wheezy), they worked for > a fresh wheezy install for the same domain: > > > *smb.conf:* > [global] > > netbios name = WheezyTest > workgroup = MAYWEG.NET > security = ADS > realm = INTRANET.MAYWEG.NET > dedicated keytab file = /etc/krb5.keytab > kerberos method = secrets and keytab > > idmap config *:backend = tdb > idmap config *:range = 2000-9999 > idmap config MAYWEG.NET:backend = ad > idmap...

...communicate fine with the ad >> dc. >> Samba Version 3.6.6. >> Following the configs of the domain member to be (wheezy), they worked for >> a fresh wheezy install for the same domain: >> >> >> *smb.conf:* >> [global] >> >> netbios name = WheezyTest >> workgroup = MAYWEG.NET >> security = ADS >> realm = INTRANET.MAYWEG.NET >> dedicated keytab file = /etc/krb5.keytab >> kerberos method = secrets and keytab >> >> idmap config *:backend = tdb >> idmap config *:range = 2000-9999 >> idmap config...

...t;> Samba Version 3.6.6. >>> Following the configs of the domain member to be (wheezy), they worked >>> for >>> a fresh wheezy install for the same domain: >>> >>> >>> *smb.conf:* >>> [global] >>> >>> netbios name = WheezyTest >>> workgroup = MAYWEG.NET >>> security = ADS >>> realm = INTRANET.MAYWEG.NET >>> dedicated keytab file = /etc/krb5.keytab >>> kerberos method = secrets and keytab >>> >>> idmap config *:backend = tdb >>> idmap config *:range =...