[Samba] File permission problems after update from Samba 4 alpha 17 to Samba 4.0.5

[X-Dimension]

We had used Samba alpha 17 (included in Resara Server 1.2) for a long 
time and
has now migrate it to Samba 4.0.5 (Ubuntu + Zentyal 3.0 PPA) with NTVFS 
enabled .


Most things seems to work: DNS with Bind9_DLZ, domain join, user login 
and also GPO are still working fine :)

But we have trouble with file permissions now!
All domain users can't rename or delete their own files which they had 
created with Samba 4 alpha 17 before.

It looks like they only had 'read only' access to their files.
For example when the user peter@mydomain wants to rename/delete a file 
he had created before, then he
gets an error message like "only peter@mydomain can rename this file" or 
"file is locked by peter@mydomain".


Our global section of /etc/samba/smb.conf looks like this:
--
[global]
interfaces = eth0
workgroup = MYDOMAIN
realm = mydomain.lan
netbios name = PDC
server string = PDC
server role = active directory domain controller
passdb backend = samba4
server services = rpc, nbt, wrepl, ldap, cldap, kdc, drepl, 
winbind, ntp_signd, kcc, dnsupdate, smb
dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, 
netlogon, lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, 
eventlog6, backupkey, dnsserver, winreg, srvsvc

--
Because Samba 4 alpha 17 was using NTVFS, i thought it is the best idea 
to stay on NTVFS even on Samba 4.0.5.

But it looks, like i was wrong.

Thanks for any ideas that helps us to fix our permission problem.

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Problems joining Samba4 domain [resolved]

[X-Dimension]

Am 14.10.2013 06:43, schrieb Andrew Bartlett:

On Sun, 2013-10-13 at 14:29 +0100, Rowland Penny wrote:


Just how closely did you follow the webpage you posted in your OP? , it
seems to be using the standard samba4 packages from Ubuntu, which if I
remember correctly are broken. Also there is a howler on the webpage you
posted, you are advised to create a share called [global] , this is the
standard top share that you will find in any smb.conf.

I would advise you to compile samba4 yourself, it is easy, see here:
https://wiki.samba.org/index.php/Build_Samba

I would also suggest that you use the latest tarball (4.1.0)

I totally agree.  We are only now getting current Samba 4.0 packages
into Debian unstable, and Ubuntu's package, particularly on 12.04 is
very, very old.

Start with current code, and then get network traces and log files if
you still have issues.

Andrew Bartlett

I'm using Samba 4.0.5 from Zentyal 3.0 PPA now, and this resolved my 
problem!


But after updating from Samba 4 alpha 17 to  Samba 4.0.5, i have file 
permission problems now.

I will describe my problems in another mail to the samba mailing list.

Thanks so far guys! :)

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Problems joining Samba4 domain

[X-Dimension]

After some minutes the problem exists again! :(
I' can't login anymore as an domain user and i can't join other clients 
to the

Samba4 domain.
After restart the Server it looks like it works again, but some minutes 
later

i ran into the same problems.

What goes wrong?


Am 13.10.2013 14:27, schrieb X-Dimension:
I have fixed this problem by changing the following line in 
/etc/krb5.conf


from

dns_lookup_realm = false

to

dns_lookup_realm = true

Why must i change this line?
When provisioning Samba4 the first time krb5.conf is generated 
automatically with the option "dns_lookup_realm = false".



Am 14.09.2013 23:28, schrieb X-Dimension:

Hi!

I've installed Samba4 like described here on Ubuntu 12.04.3

http://www.matrix44.net/cms/notes/gnulinux/samba-4-ad-domain-with-ubuntu-12-04 



DNS with BIND_DLZ backend seems to work and i can add DNS records 
without a problem with Microsoft RSAT.


When i try kinit on the server i get the following:

root@PDC:~# kinit administrator
Password for administra...@mydomain.lan:

-> Works fine

root@PDC:~# kinit administra...@mydomain.lan
Password for administra...@mydomain.lan:

-> Works fine

root@PDC:~# kinit administra...@mydomain.lan
Password for administra...@mydomain.lan:
kinit: KDC reply did not match expectations while getting initial 
credentials


-> Don't work

When i try to join a Windows 7 Professional client to my domain, i 
get this:


1. Joining as user "administrator" to domain "mydomain" or "MYDOMAIN" 
or "mydomain.lan" or "MYDOMAIN.LAN"

 -> wrong username or password

2.   Joining as user "administrator@mydomain" to domain "mydomain"
 -> works fine
But after a reboot i can't login as "administrator@mydomain" and i 
get wrong username and password


My krb5.conf looks like this:

[libdefaults]
default_realm = MYDOMAIN.LAN
dns_lookup_realm = false
dns_lookup_kdc = true

What goes wrong here?

Thanks for help!






--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Problems joining Samba4 domain

[X-Dimension]

I have fixed this problem by changing the following line in /etc/krb5.conf

from

dns_lookup_realm = false

to

dns_lookup_realm = true

Why must i change this line?
When provisioning Samba4 the first time krb5.conf is generated 
automatically with the option "dns_lookup_realm = false".



Am 14.09.2013 23:28, schrieb X-Dimension:

Hi!

I've installed Samba4 like described here on Ubuntu 12.04.3

http://www.matrix44.net/cms/notes/gnulinux/samba-4-ad-domain-with-ubuntu-12-04 



DNS with BIND_DLZ backend seems to work and i can add DNS records 
without a problem with Microsoft RSAT.


When i try kinit on the server i get the following:

root@PDC:~# kinit administrator
Password for administra...@mydomain.lan:

-> Works fine

root@PDC:~# kinit administra...@mydomain.lan
Password for administra...@mydomain.lan:

-> Works fine

root@PDC:~# kinit administra...@mydomain.lan
Password for administra...@mydomain.lan:
kinit: KDC reply did not match expectations while getting initial 
credentials


-> Don't work

When i try to join a Windows 7 Professional client to my domain, i get 
this:


1. Joining as user "administrator" to domain "mydomain" or "MYDOMAIN" 
or "mydomain.lan" or "MYDOMAIN.LAN"

 -> wrong username or password

2.   Joining as user "administrator@mydomain" to domain "mydomain"
 -> works fine
But after a reboot i can't login as "administrator@mydomain" and i get 
wrong username and password


My krb5.conf looks like this:

[libdefaults]
default_realm = MYDOMAIN.LAN
dns_lookup_realm = false
dns_lookup_kdc = true

What goes wrong here?

Thanks for help!




--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Problems joining Samba4 domain

[X-Dimension]

Hi!

I've installed Samba4 like described here on Ubuntu 12.04.3

http://www.matrix44.net/cms/notes/gnulinux/samba-4-ad-domain-with-ubuntu-12-04

DNS with BIND_DLZ backend seems to work and i can add DNS records 
without a problem with Microsoft RSAT.


When i try kinit on the server i get the following:

root@PDC:~# kinit administrator
Password for administra...@mydomain.lan:

-> Works fine

root@PDC:~# kinit administra...@mydomain.lan
Password for administra...@mydomain.lan:

-> Works fine

root@PDC:~# kinit administra...@mydomain.lan
Password for administra...@mydomain.lan:
kinit: KDC reply did not match expectations while getting initial 
credentials


-> Don't work

When i try to join a Windows 7 Professional client to my domain, i get this:

1. Joining as user "administrator" to domain "mydomain" or "MYDOMAIN" or 
"mydomain.lan" or "MYDOMAIN.LAN"

 -> wrong username or password

2.   Joining as user "administrator@mydomain" to domain "mydomain"
 -> works fine
But after a reboot i can't login as "administrator@mydomain" and i get 
wrong username and password


My krb5.conf looks like this:

[libdefaults]
default_realm = MYDOMAIN.LAN
dns_lookup_realm = false
dns_lookup_kdc = true

What goes wrong here?

Thanks for help!


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Samba 4 Alpha 17 to 4.0.x update - questions concerning S3FS / NTVFS

[X-Dimension]

We had used Samba 4 alpha 17 for a long time and want to update our 
server now to Samba 4.0.x.
The old Samba versions was using NTVFS and Samba 4.0.x is now using S3FS 
by default.


So, what is the best practice now? Should we stay on NTVFS or should we 
switch to S3FS?


The global part of our smb.conf looks like this:

---
[global]
interfaces = eth0
netbios name = PDC
passdb backend = samba4
realm = MYDOMAIN.LAN
# Global parameters
server role = domain controller
server string = PDC
workgroup = MYDOMAIN
---

When we start Samba 4.0.x with this configuration, is it using NTVFS 
like before or is it using S3FS then?


Thx for help!
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Samba 4 - problems with name resolution on Windows 7 clients

[X-Dimension]

Am 10.04.2013 19:15, schrieb Matthieu Patou:

On 04/10/2013 09:48 AM, X-Dimension wrote:
We have a strange name resolution problem on Windows 7 clients. 
(Windows XP clients are working fine!)
If a Windows 7 client is connected more than 7 or 8 hours to our 
Samba 4 active directory server, we can't
do "ping servername" anymore, but "ping servername.domainname" works 
fine.

After logout and login again to the Windows 7 clients everything works!
Can you check what is the ipconfig /all output on windows 7 clients ? 
also you should do a tcpdump/wireshark trace on your client to see 
which DNS request it is doing.
The main problem is, that all Windows clients access the samba shares 
by \\servername\sharename
and not \\servername.domainname\sharename and after 7 or 8 hours our 
users can't access the files

or programs on these shares.
What goes wrong here and what is the best way to fix this? I can 
change some GPOs and set all
shares to \\servername.domainname\sharename, but if there is a better 
solution i would prefer this.

Thx for help! :)


Matthieu.


Here is the output of ipconfig /all:

Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : Client1
   Primäres DNS-Suffix . . . . . . . : mydomain.local
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein
   DNS-Suffixsuchliste . . . . . . . : mydomain.local

Ethernet-Adapter LAN-Verbindung:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : vmxnet3 Ethernet Adapter
   Physikalische Adresse . . . . . . : xx-xx-xx-xx-xx-xx
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : :::::%xx(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 192.168.1.235(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Standardgateway . . . . . . . . . : 192.168.1.5
   DNS-Server  . . . . . . . . . . . : 192.168.1.200
   NetBIOS über TCP/IP . . . . . . . : Aktiviert



--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Samba 4 - problems with name resolution on Windows 7 clients

[X-Dimension]

We have a strange name resolution problem on Windows 7 clients. (Windows 
XP clients are working fine!)
If a Windows 7 client is connected more than 7 or 8 hours to our Samba 4 
active directory server, we can't

do "ping servername" anymore, but "ping servername.domainname" works fine.
After logout and login again to the Windows 7 clients everything works!
The main problem is, that all Windows clients access the samba shares by 
\\servername\sharename
and not \\servername.domainname\sharename and after 7 or 8 hours our 
users can't access the files

or programs on these shares.
What goes wrong here and what is the best way to fix this? I can change 
some GPOs and set all
shares to \\servername.domainname\sharename, but if there is a better 
solution i would prefer this.

Thx for help! :)
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] GPOs don't work after update from Samba4.0 alpha 17 to 4.0.1

[X-Dimension]

Yes, i have used wmi filters before to set some GPOs for our Windows XP clients 
and some for Windows 7 clients only. 

I have removed the wmi filters from Microsofts Group Policy tool, but it seems 
to have no effect, i still get the same errors.


 Original-Nachricht 
> Datum: Sun, 27 Jan 2013 15:37:41 +0100
> Von: "Thomas Manninger" 
> An: samba@lists.samba.org
> Betreff: Re: [Samba] GPOs don\'t work after update from Samba4.0 alpha 17 to 
> 4.0.1

> Do you used wmi filters for your gpos?
> 
>  Original-Nachricht 
> > Datum: Sun, 27 Jan 2013 13:25:22 +0100
> > Von: x-dimens...@gmx.net
> > An: samba@lists.samba.org
> > Betreff: [Samba] GPOs don\'t work after update from Samba4.0 alpha 17 to
> 4.0.1
> 
> > Hi!
> > 
> > I have updated our server from Samba 4 alpha 17 to Samba 4.0.1.
> > Everything seems to work fine after some reconfiguration, but our
> > GPOs are not working anymore.
> > 
> > Samba 4 alpha 17 was using ntvfs and the root partition with the sysvol
> > share was mounted with "user_xattr" only in /etc/fstab.
> > Samba 4.0.1 is now set to use s3fs and the root partition is mouted with
> > "user_xattr,acl,barrier=1".
> > 
> > After updating to the newer Samba release i run "samba-tool ntacl
> > sysvolreset" like it was described in the release notes.
> > 
> > Gpresult /H shows me that only the Default Domain Policy is loaded, but
> > not all the policies in the OU.
> > 
> > Gpupdate /force shows this error on a client:
> > 
> > ---
> > Die Richtlinie wird aktualisiert...
> > 
> > Die Aktualisierung der Benutzerrichtlinie wurde erfolgreich
> abgeschlossen.
> > Die Computerrichtlinie konnte nicht erfolgreich aktualisiert werden.
> > Folgende Probleme sind aufgetreten:
> > 
> > Fehler bei der Verarbeitung der Gruppenrichtlinie. Der WMI-Filter
> (Windows
> > Management Instrumentation) für das Gruppenrichtlinienobjekt
> >
> "cn={97E400EB-EDFD-4024-A9D5-1BB8261ABE01},cn=policies,cn=system,DC=mynetwork,DC=lan"
> > konnte nicht ausgewertet werden. Dies kann darauf zurückzuführen sein,
> > dass RSoP deaktiviert ist, oder dass der WMI-Dienst deaktiviert oder
> > angehalten wurde, bzw. andere WMI-Fehler aufgetreten sind. Stellen Sie
> sicher, dass
> > der WMI-Dienst gestartet ist und dass der Starttyp auf automatischen
> Start
> > festgelegt ist. Neue Gruppenrichtlinienobjekte oder -einstellungen
> werden
> > nicht verarbeitet, bis dieses Ereignis behoben wurde.
> > ---
> > Google Translate:
> > 
> > The policy is updated ...
> > 
> > Updating the user policy has been successfully completed.The computer
> > policy could not be updated successfully. The following problems:
> > 
> > Error processing of Group Policy. The WMI filter (Windows Management
> > Instrumentation) for the GPO "cn =
> {97E400EB-4024-A9D5-EDFD-1BB8261ABE01}, cn =
> > policies, cn = System, DC = mynetwork, DC = lan" could not be evaluated.
> > This may be due to the fact that RSOP is disabled, or that the WMI
> service is
> > disabled or stopped, or other WMI errors. Make sure that the WMI service
> > is started and that the startup type is set to start automatically. New
> > Group Policy objects or settings will not be processed until this event
> is
> > resolved.
> > ---
> > 
> > How can i get my GPOs to work again?
> > 
> > Thanks for help!
> > -- 
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  https://lists.samba.org/mailman/options/samba
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] GPOs don't work after update from Samba4.0 alpha 17 to 4.0.1

[X-Dimension]

Hi!

I have updated our server from Samba 4 alpha 17 to Samba 4.0.1.
Everything seems to work fine after some reconfiguration, but our
GPOs are not working anymore.

Samba 4 alpha 17 was using ntvfs and the root partition with the sysvol share 
was mounted with "user_xattr" only in /etc/fstab.
Samba 4.0.1 is now set to use s3fs and the root partition is mouted with 
"user_xattr,acl,barrier=1".

After updating to the newer Samba release i run "samba-tool ntacl sysvolreset" 
like it was described in the release notes.

Gpresult /H shows me that only the Default Domain Policy is loaded, but not all 
the policies in the OU.

Gpupdate /force shows this error on a client:

---
Die Richtlinie wird aktualisiert...

Die Aktualisierung der Benutzerrichtlinie wurde erfolgreich abgeschlossen.
Die Computerrichtlinie konnte nicht erfolgreich aktualisiert werden. Folgende 
Probleme sind aufgetreten:

Fehler bei der Verarbeitung der Gruppenrichtlinie. Der WMI-Filter (Windows 
Management Instrumentation) für das Gruppenrichtlinienobjekt 
"cn={97E400EB-EDFD-4024-A9D5-1BB8261ABE01},cn=policies,cn=system,DC=mynetwork,DC=lan"
 konnte nicht ausgewertet werden. Dies kann darauf zurückzuführen sein, dass 
RSoP deaktiviert ist, oder dass der WMI-Dienst deaktiviert oder angehalten 
wurde, bzw. andere WMI-Fehler aufgetreten sind. Stellen Sie sicher, dass der 
WMI-Dienst gestartet ist und dass der Starttyp auf automatischen Start 
festgelegt ist. Neue Gruppenrichtlinienobjekte oder -einstellungen werden nicht 
verarbeitet, bis dieses Ereignis behoben wurde.
---
Google Translate:

The policy is updated ...

Updating the user policy has been successfully completed.The computer policy 
could not be updated successfully. The following problems:

Error processing of Group Policy. The WMI filter (Windows Management 
Instrumentation) for the GPO "cn = {97E400EB-4024-A9D5-EDFD-1BB8261ABE01}, cn = 
policies, cn = System, DC = mynetwork, DC = lan" could not be evaluated. This 
may be due to the fact that RSOP is disabled, or that the WMI service is 
disabled or stopped, or other WMI errors. Make sure that the WMI service is 
started and that the startup type is set to start automatically. New Group 
Policy objects or settings will not be processed until this event is resolved.
---

How can i get my GPOs to work again?

Thanks for help!
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Remove dead server from domain.

[X-Dimension]

I have the same problem here.
Would be nice to see a solution for it.

 Original-Nachricht 
> Datum: Mon, 10 Dec 2012 13:49:14 +
> Von: Alex Matthews 
> An: samba@lists.samba.org
> Betreff: Re: [Samba] Remove dead server from domain.

> Hi all,
> 
> Sorry to bump my own thread but are there any suggestions for this issue?
> 
> Thanks,
> 
> Alex
> 
> On 05/12/2012 12:53, Thomas Simmons wrote:
> > Just to note, I have seen the same problem deleting "real" Windows 
> > Server DCs with rc4 and rc5. The first time I try deleting the DC via 
> > ADUC, I get the error:
> >
> > *Windows cannot delete object LDAP://10.1.1.254/CN=ADC2,OU=Domain 
> >  
> > Controllers,DC=internal,DC=testdom,DC=com because:
> > The parameter is incorrect.
> >
> > On subsequent tries, the following error is displayed:
> >
> > Windows cannot delete object LDAP://10.1.1.254/CN=ADC2,OU=Domain 
> >  
> > Controllers,DC=internal,DC=testdom,DC=com because:
> > The specified module could not be found.*
> > *
> > *
> > *My testing has shown that Windows Servers often fail to demote in 
> > various circumstances, so a solution to remove them from AD would be 
> > very useful.*
> >
> >
> > On Wed, Dec 5, 2012 at 7:36 AM, Alex Matthews 
> > mailto:qoole.sa...@lillimoth.com>> wrote:
> >
> > Hiya,
> >
> >
> > I have an S4 domain running that I added another S4 machine to as
> > an extra domain controller. That machine, unfotunately died (quite
> > spectacularly I must say, think magic blue smoke). I would like to
> > remove the dead domain controller from the domain.
> >
> > In ADUC I can see the DC under 'Domain Controllers' but when I try
> > to delete it (having ticked the 'permanently offline' box) I get
> > the following error:
> >
> > "Windows cannot delete object
> > LDAP://tainan.internal.stmaryscollege.co.uk/CN=PEFW01,OU=Domain
> > 
> > Controllers,DC=internal,DC=stmaryscollege,DC=co,DC=uk because:
> >
> > The specified module could not be found."
> >
> > Is there a command line tool that I could try (samba-tool doesn't
> > seem to have an option to remove the machine).
> >
> > Any other suggestions?
> >
> > Thanks,
> >
> > Alex
> > -- 
> > To unsubscribe from this list go to the following URL and read the
> > instructions: https://lists.samba.org/mailman/options/samba
> >
> >
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Wrong menu language on Windows 7 clients after update to Samba4 beta8

[X-Dimension]

 Original-Nachricht 
> Datum: Thu, 4 Oct 2012 19:50:08 +0200
> Von: "Günter Kukkukk" 
> An: x-dimens...@gmx.net
> CC: samba@lists.samba.org
> Betreff: Re: [Samba] Wrong menu language on Windows 7 clients after update to 
> Samba4 beta8

> Am Donnerstag, 4. Oktober 2012, 09:39:49 schrieb x-dimens...@gmx.net:
> >  Original-Nachricht 
> > 
> > > Datum: Thu, 04 Oct 2012 07:17:25 +1000
> > > Von: Andrew Bartlett 
> > > An: x-dimens...@gmx.net
> > > CC: samba@lists.samba.org
> > > Betreff: Re: [Samba] Wrong menu language on Windows 7 clients after
> > > update to Samba4 beta8
> > > 
> > > On Wed, 2012-10-03 at 16:49 +0200, x-dimens...@gmx.net wrote:
> > > > After updating from Samba4 alpha 17 to beta8 most Windows start menu
> > > 
> > > entries on our Windows 7 clients are in english now, instead of
> german.
> > > 
> > > > Also the desktop.ini files are not hidden anymore like it was
> before.
> > > > What goes wrong here?
> > > > Do i need to set a new parameter in smb.conf or mount the filesystem
> > > 
> > > with some attributes?
> > > 
> > > Neither of these are likely to be the cause of a language change on
> the
> > > client.
> > > 
> > > Most likely the issue is due to being unable to load policies or the
> > > profile.
> > > 
> > > Andrew Bartlett
> > 
> > The language of the clients hasn't changed.
> > I think this is a problem with file permissions...
> > 
> > Samba4 alpha 17 was part of the Resara Server we had used before.
> > The partition with the profiles and all user data was mounted by Resara
> > Server with Avahi daemon and now i mount this partition via /etc/fstab
> and
> > this entry:
> > 
> > /dev/sdc1  /volumes/HD1 ext4 user_xattr 0 2
> > 
> > Maybe this is wrong? I don't know what parameters was used before by
> Avahi.
> 
> at least you should also add the "acl" mount option (in addition to the
> already
> used "user_xattr")
> 
> Cheers, Günter

Thank you very much Günter, the acl mount option in fstab seems to fix this 
problem! :)


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Samba-tool dbcheck shows "incorrect GUID" after update from alpha17 to beta8

[X-Dimension]

 Original-Nachricht 
> Datum: Thu, 4 Oct 2012 12:22:54 +0200
> Von: Michael Wood 
> An: Julian Timm 
> CC: samba@lists.samba.org
> Betreff: Re: [Samba] Samba-tool dbcheck shows "incorrect GUID" after update 
> from alpha17 to beta8

> On 4 October 2012 09:46, Julian Timm  wrote:
> >
> >  Original-Nachricht 
> >> Datum: Wed, 3 Oct 2012 16:56:42 +0200
> >> Von: Michael Wood 
> >> An: x-dimens...@gmx.net
> >> CC: samba@lists.samba.org
> >> Betreff: Re: [Samba] Samba-tool dbcheck shows "incorrect GUID" after
> update from alpha17 to beta8
> >
> >> On 3 October 2012 16:26,   wrote:
> >> > After updating our Samba4 server from alpha17 to beta8 "samba-tool
> >> dbcheck" shows 24 "incorrect GUID" errors.
> >> > What does it mean and what should i do to fix this?
> >>
> >> Try samba-tool dbcheck --fix.
> >>
> >> Also, why did you not install rc2 instead of beta8?
> >
> > I don't want to compile every Samba version for myself, so i'm using
> > the Zentyal 2.3 PPA. The latest Samba version here is beta8, but rc2
> packages are in testing and should be available soon.
> >
> > After running samba-tool dbcheck --fix the errors still exists, when
> running dbcheck again.
> 
> Try posting the errors to the list and maybe someone will be able to
> say what causes them.
> 
> -- 
> Michael Wood 

Ok, here is an example:

ERROR: incorrect GUID component for member in object 
CN=Mitarbeiter,OU=Benutzer,DC=test,DC=lan - 
;;CN=Max
 Müller,OU=Benutzer,DC=test,DC=lan
unable to find object for DN CN=Max Müller,OU=Benutzer,DC=test,DC=lan - (No 
such Base DN: CN=Max Müller,OU=Benutzer,DC=test,DC=lan)
Not removing dangling forward link

All of these database errors affecting users who have german umlauts
in their names like Ä,Ö,Ü. 
These users are also not shown within the Microsoft RSAT AD manager.
When i add a new user now like "Horst Müller" with the management tool, i get 
the error that the user could not be verified and can't login, but RSAT still 
creates the user.

Is there a simple way to correct this problem?
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] Wrong menu language on Windows 7 clients after update to Samba4 beta8

[X-Dimension]

 Original-Nachricht 
> Datum: Thu, 04 Oct 2012 07:17:25 +1000
> Von: Andrew Bartlett 
> An: x-dimens...@gmx.net
> CC: samba@lists.samba.org
> Betreff: Re: [Samba] Wrong menu language on Windows 7 clients after update to 
> Samba4 beta8

> On Wed, 2012-10-03 at 16:49 +0200, x-dimens...@gmx.net wrote:
> > After updating from Samba4 alpha 17 to beta8 most Windows start menu
> entries on our Windows 7 clients are in english now, instead of german.
> > Also the desktop.ini files are not hidden anymore like it was before.
> > What goes wrong here?
> > Do i need to set a new parameter in smb.conf or mount the filesystem
> with some attributes? 
> 
> Neither of these are likely to be the cause of a language change on the
> client. 
> 
> Most likely the issue is due to being unable to load policies or the
> profile. 
> 
> Andrew Bartlett
> 
> -- 
> Andrew Bartletthttp://samba.org/~abartlet/
> Authentication Developer, Samba Team   http://samba.org
> 
> 
The language of the clients hasn't changed.
I think this is a problem with file permissions...

Samba4 alpha 17 was part of the Resara Server we had used before.
The partition with the profiles and all user data was mounted by Resara Server 
with Avahi daemon and now i mount this partition via /etc/fstab and this entry:

/dev/sdc1  /volumes/HD1 ext4 user_xattr 0 2

Maybe this is wrong? I don't know what parameters was used before by Avahi.

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Wrong menu language on Windows 7 clients after update to Samba4 beta8

[X-Dimension]

After updating from Samba4 alpha 17 to beta8 most Windows start menu entries on 
our Windows 7 clients are in english now, instead of german.
Also the desktop.ini files are not hidden anymore like it was before.
What goes wrong here?
Do i need to set a new parameter in smb.conf or mount the filesystem with some 
attributes? 

Thanks for help


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Samba-tool dbcheck shows "incorrect GUID" after update from alpha17 to beta8

[X-Dimension]

After updating our Samba4 server from alpha17 to beta8 "samba-tool dbcheck" 
shows 24 "incorrect GUID" errors.
What does it mean and what should i do to fix this?

Thx 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] How to update from Samba4.0.0 alpha17 to beta8 and switch from ntvfs to s3fs

[X-Dimension]

We have a Samba4.0.0 alpha17 based server running with ntvfs in 
/usr/local/samba and want to update it to beta8 but with s3fs support enabled.

Samba4beta8 is installed in /var/lib/samba.

What steps must be done to update our server and switch from ntvfs to s3fs and 
also the samba directory from /usr/local/samba/ to /var/lib/samba?

Thanks for help! :)
 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] How to delete a domain controller from the active directory?

[X-Dimension]

After my migration tests, i have now three domain controllers in my active 
directory, but only one is online.
I've tried to remove the two other domain controllers with the active directory 
tool from MS RSAT, but it doesn't work. 

How can i delete the non used domain controllers completely?

Thx for help!  
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] How to migrate Active Directory from one Samba4 server to another

[X-Dimension]

>  Original-Nachricht 
> > Datum: Mon, 13 Aug 2012 17:47:35 +1000
> > Von: Andrew Bartlett 
> > An: x-dimens...@gmx.net
> > CC: samba@lists.samba.org
> > Betreff: Re: [Samba] How to migrate Active Directory from one Samba4
> server to another
> 
> > On Sat, 2012-08-11 at 22:03 +0200, x-dimens...@gmx.net wrote:
> > > Hello!
> > > 
> > > We are using a Samba4.0.0alpha19 (Resara 1.1.2) based domain
> controller
> > in a small production environment and because the Resara development has
> > ended we want to switch to a plain Samba4 beta based Ubuntu
> 12.04/Zentyal
> > Server.
> > > I have installed and configured the new server with the same
> domain-name
> > and the same hostname like the old server. 
> > > How can i export the Active Directory from the old server and import
> it
> > to the new Samba4 server? 
> > 
> > Something like this (unstested):
> > 
> > Use a different hostname, then run 'samba-tool domain join' to join it
> > to the first domain.  Then you can use the
> > source4/scripting/bin/renamedc script to rename it back to the name of
> > the first DC, after running 'samba-tool domain demote' on it. 
> > 
> > You may need to seize FSMO roles from one DC to the other with
> > 'samba-tool domain fsmo'.
> > 
> > > Do i need to rejoin the clients to the domain, after this?
> > 
> > No.
> > 
> > Additional complications may include DNS configuration.  You may need to
> > use --dns-backend=none on the join command. 
> > 
> > This is just a series of hints to get you started.  Hopefully you can
> > work it out from here. 
> > 
> > Andrew Bartlett
> > 
> > -- 
> > Andrew Bartlett   
> http://samba.org/~abartlet/
> > Authentication Developer, Samba Team   http://samba.org
> > 
> > 
> Thank you Andrew, this was very helpful!
> Joining the new Samba4 Server to the old one replicates the Active
> Directory without a problem! After shutting down the old server, renaming the 
> new
> server and restore smb.conf and krb5.conf i can access the new server with
> RSAT now. :-)
> 
> What does not work is the dns-backend! :-(
> After the AD replication the DNS snap-in from RSAT does not work anymore.
> The join option "--dns-backend=none" is not available here
> (Samba4.0.0beta2 Zentyal package) 
> Is there another way to get DNS working after the replication from the old
> server? 
> 
> I have also another question: What does the "renamedc" script do? 
> When i start it, it always tells me that there are opened transactions and
> so it can't run.
> Because of this i simple change the hostname in /etc/hostname/ and
> /etc/hosts and run hostname -F /etc/hostname. After a restart all looks good 
> so
> far. (but i haven't tested it very much)
> 
> THX
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

I've tried now also Samba4.0.0beta6 and when i join this server with the 
--dns-backend=NONE option to the old samba4alpha PDC i have no working DNS 
service on the new Samba server. Bind9 won't start because it can't find 
sam.ldb. This file is created on provisioning the Samba server the first time, 
but while our old Resara Server uses plain Bind without the Samba-LDAP-backend 
sam.ldb is not created when joining the new server to the existing domain.
Is there a way setup the DNS-part after the replication, so that it uses the 
internal LDAP of Samba4? I don't need to get the DNS entries of the old server 
to the new server, but i need a working DNS-Samba/LDAP Backend to create Zones 
and entries with RSAT.

Thx for help!

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Re: [Samba] How to migrate Active Directory from one Samba4 server to another

[X-Dimension]

 Original-Nachricht 
> Datum: Mon, 13 Aug 2012 17:47:35 +1000
> Von: Andrew Bartlett 
> An: x-dimens...@gmx.net
> CC: samba@lists.samba.org
> Betreff: Re: [Samba] How to migrate Active Directory from one Samba4 server 
> to another

> On Sat, 2012-08-11 at 22:03 +0200, x-dimens...@gmx.net wrote:
> > Hello!
> > 
> > We are using a Samba4.0.0alpha19 (Resara 1.1.2) based domain controller
> in a small production environment and because the Resara development has
> ended we want to switch to a plain Samba4 beta based Ubuntu 12.04/Zentyal
> Server.
> > I have installed and configured the new server with the same domain-name
> and the same hostname like the old server. 
> > How can i export the Active Directory from the old server and import it
> to the new Samba4 server? 
> 
> Something like this (unstested):
> 
> Use a different hostname, then run 'samba-tool domain join' to join it
> to the first domain.  Then you can use the
> source4/scripting/bin/renamedc script to rename it back to the name of
> the first DC, after running 'samba-tool domain demote' on it. 
> 
> You may need to seize FSMO roles from one DC to the other with
> 'samba-tool domain fsmo'.
> 
> > Do i need to rejoin the clients to the domain, after this?
> 
> No.
> 
> Additional complications may include DNS configuration.  You may need to
> use --dns-backend=none on the join command. 
> 
> This is just a series of hints to get you started.  Hopefully you can
> work it out from here. 
> 
> Andrew Bartlett
> 
> -- 
> Andrew Bartletthttp://samba.org/~abartlet/
> Authentication Developer, Samba Team   http://samba.org
> 
> 
Thank you Andrew, this was very helpful!
Joining the new Samba4 Server to the old one replicates the Active Directory 
without a problem! After shutting down the old server, renaming the new server 
and restore smb.conf and krb5.conf i can access the new server with RSAT now. 
:-)

What does not work is the dns-backend! :-(
After the AD replication the DNS snap-in from RSAT does not work anymore.
The join option "--dns-backend=none" is not available here (Samba4.0.0beta2 
Zentyal package) 
Is there another way to get DNS working after the replication from the old 
server? 

I have also another question: What does the "renamedc" script do? 
When i start it, it always tells me that there are opened transactions and so 
it can't run.
Because of this i simple change the hostname in /etc/hostname/ and /etc/hosts 
and run hostname -F /etc/hostname. After a restart all looks good so far. (but 
i haven't tested it very much)

THX
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] How to migrate Active Directory from one Samba4 server to another

[X-Dimension]

Hello!

We are using a Samba4.0.0alpha19 (Resara 1.1.2) based domain controller in a 
small production environment and because the Resara development has ended we 
want to switch to a plain Samba4 beta based Ubuntu 12.04/Zentyal Server.
I have installed and configured the new server with the same domain-name and 
the same hostname like the old server. 
How can i export the Active Directory from the old server and import it to the 
new Samba4 server? 
Do i need to rejoin the clients to the domain, after this?

Thx for help! :)

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

[Samba] Samba PDC and Windows XP clients - login timeout after 15 minutes

[X-Dimension]

Hi!

We are using a Samba PDC with 40 Windows XP clients and have some strange  
problems.
When a user starts his Windows computer and don't login within the next 15  
minutes
(because he drinks a cup of coffee) and tried to login after that time he  
get the message,
that the server-profile could not be loaded and a temporary profile is  
used instead.


There are absolutely no problems when a user starts his computer and log  
in within the next 15 minutes,

but after this time period he always get the error described above.

Any ideas what goes wrong?

THX

--
Powered by Mandriva Linux & Opera M2
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba