Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - krainbolt

Pages: [1]
1
Bump.   :(

Does anyone have any ideas?

2
Installation and Upgrades / Re: resolv.conf
« on: July 18, 2014, 03:53:44 am »
I have noticed the same behavior.  When I install Users and Computers, the DNS component is installed along with it.  However, instead of the Zentyal DNS component performing zone transfers for records on the master DNS server to itself, it completely ignores the other DNS servers and sets itself to be the master with only one DNS record for itself, then changes the resolv.conf file to resolve to itself (127.0.0.1). The other DNS servers have been configured to allow zone transfers to Zentyal, but Zentyal doesn't want anything to do with them.

There is a chance my bad experience with the Zentyal DNS component might be caused by an unrelated bug in Samba4.  I won't know until I've had a chance to test the Samba patch located here: https://github.com/Zentyal/samba/commit/d747372d28273542298f86530e715e8faaf907f2


3
Installation and Upgrades / Where are the Daily Builds of Zentyal?
« on: July 18, 2014, 03:13:59 am »
According to this page, I can download the latest daily builds from SourceForge: https://wiki.zentyal.org/index.php/Daily_Builds

However, only Zentyal 3.5 and older are available there: http://sourceforge.net/projects/zentyal/files/

There is a big bug in ZentYal 3.5 which prohibits me from testing\using it, but it has been patched in the GitHub repository here: https://github.com/Zentyal/zentyal/ and here: https://github.com/Zentyal/samba

Where is current location of Daily Builds from GitHub?

4
This problem is not with the Windows 2012 domain functional level.  I am currently operating my Windows 2012 R2 servers in a Windows 2003 domain functional level which should work, but it doesn't due to this bug.  The bug is related to the operating system itself and the fact it returns a blob of 52 bytes instead of 48 as with Windows 2008 server.

Here is a quote from the patch:

Quote
Digging into the problem it seems to be in the drsuapi IDL. The
DsBindInfo blob returned by the server is decoded in the IDL, based on
the blob length. For some reason, some servers are returning a 32 bytes
length blob, which is not decoded, so it falls into the default case and
python bindings crash.

Reviewing the documentation [MS-DRSR], it is possible the server not to
push the object GUID of the configuration NC, so I have added that case
and also the one to decode the blob returned by W2K12 R2 which is 52 bytes.

So regardless of the domain functional level, Windows 2012 R2 cannot be used unless this patch is applied.


5
It appears there are a few people reporting this error when running Windows 2012 Server and attempting to join Zentyal to a domain as DC.  I am also experiencing this error.

A few references here:

Server 2012/Zentyal issues
https://forum.zentyal.org/index.php/topic,21652.msg83486.html#msg83486

Joining Samba to Windows Server 2012 DC failed
https://forum.zentyal.org/index.php/topic,19988.msg76525.html#msg76525

Zentyal como controlador de dominio adicional
https://forum.zentyal.org/index.php/topic,22347.msg86123.html#msg86123


It also appears Zentyal has found a solution and has even submitted a patch to Samba - which they have implemented.

References here:

Bug #689: samba-tool join error ( 'drsuapi.DsBindInfoFallBack' object has no attribute 'supported_extensions')
https://tracker.zentyal.org/issues/689

[PATCH] drsuapi.idl: Manage all possible lengths of DsBindInfo
https://lists.samba.org/archive/samba-technical/2014-July/100951.html

idl:drsuapi: Manage all possible lengths of drsuapi_DsBindInfo
https://git.samba.org/?p=samba.git;a=commitdiff;h=d747372d28273542298f86530e715e8faaf907f2


My question is, will Zentyal be releasing a patch for this bug for Zentyal 3.5?  It may be awhile before a new version of Samba is released which contains this patch and in the meantime Zentyal will remain unusable as an Exchange replacement for those running Windows 2012 R2 (regardless of the domain functional level used).


6
I agree.  Maybe those changes will make their way into the next release.

In the end I used Microsoft ADSI Edit Tool to locate and delete the ghost trust.  This seems to have fixed this problem.

For others with this problem, you can follow the directions here to locate and delete the ghost trust:
http://support.microsoft.com/kb/228477


Now I have a new error related to the Samba4 bug and Windows 2012 R2.  Seems Zentyal has submitted a patch to the Samba community - hopefully Zentyal will release a point update soon with this patch included.
https://tracker.zentyal.org/issues/689

7
Thanks for the reply and suggestions!  I have quadruple-checked and there are no trusts visible in the Active Directory Domains and Trusts MMC Snap-in.  I discovered the "nltest" command line tool and ran it - sure enough, there is a hidden domain trust which isn't viewable in the GUI.

Code: [Select]
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\administrator.MYDOMAIN>nltest /server:dc-01 /trusted_domains
List of domain trusts:
    0: MYDOMAIN mydomain.net (NT 5) (Forest Tree Root) (Primary Domain) (Native)
The command completed successfully

C:\Users\administrator.MYDOMAIN>

More information here: http://support.microsoft.com/kb/228477
(The article was written for Windows 2000 Server, but is still valid for Windows Server 2012 R2.)

The trust is to itself, which doesn't make much sense to me.  It was created in 2005 (probably by mistake) and apparently quietly sneaked through all of our domain controller migrations over the years.  I will remove it tomorrow and report my findings.


8
I should mention that I have exhaustively searched for this topic and the only (slightly) similar post I have found was the following, which does not apply in my case: 

https://forum.zentyal.org/index.php/topic,16576.msg66270.html#msg66270

No trust relationships exist in my case.

I tried to install and configure Zentyal 3.4 a month ago and exhausted efforts trying to find a resolution to the same error, so I dropped the project.  I have recently picked it up again since Zentyal 3.5 was released, only to receive the same error.

If there is a command I can run to verify trust relationship status, or a log file I can look at to locate the exactly reason the error was thrown, please point me in the right direction.  Thanks for any ideas.

9
I am running two Windows 2012 domain controllers in Windows Server 2003 domain functional level.  There is only one domain in the forest and no trust relationships exist.

After a fresh install of Zentyal 3.5 and adding OpenChange, I am getting the following error when I attempt to set the Zentyal Domain Server Role to "Additional domain controller" under Domain settings:

The domain you are trying to join has trust relationships defined. At the moment this is not supported by samba.

Error from log file:
Code: [Select]
2014/07/11 12:00:49 INFO> Provision.pm:930 EBox::Samba::Provision::checkTrustDomainObjects - Checking for domain trust relationships...
2014/07/11 12:00:49 DEBUG> Provision.pm:939 EBox::Samba::Provision::checkTrustDomainObjects - The domain you are trying to join has trust relationships defined. At the moment this is not supported by samba. at The domain you are trying to join has trust relationships defined. At the moment this is not supported by samba. at /usr/share/perl5/EBox/Samba/Provision.pm line 939

Again, no trust relationships exist according to the Active Directory Domains and Trusts GUI for the domain or forest.  What could be causing this error when no forest or domain trust relationships exist?

Pages: [1]