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.
1
Installation and Upgrades / Re: Raspberry Pi 2 and zentyal??
« on: June 24, 2019, 03:46:58 pm »
Today the Raspberry Pi 4 with 4 gig of memory was announced, so it might be a better platform to try again to get Zential working?
2
Installation and Upgrades / Serious 3.5 problem!
« on: August 15, 2014, 03:42:44 pm »
I found a serious flaw in 3.5 and I think this is causing all my current 3.5 challenges.
They removed something with 3.5 to clean things ups regarding LDAP, but in my opinion something was forgotten. Let me try to explain.
I had a 24x7 server running, which cost me a fortune on electricity, so I decided to buy a Zotac ID42 and use Zentyal as my home BDC, Internet gateway, proxy server, ad blocker etc.
I have my PDC running in a virtual 2008 R2 system and I finally managed with many reinstalls to get a working Zentyal 3.3. An upgrade to 3.4 worked just fine, but problems started happening again as soon as I executed the 3.5 upgrade. I managed to overcome this by a clean install, but the upgrade or me (?) corrupted my pdc. Because my PDC now thought it was a BDC. After several dcdiag and ntdsutil actions, I recovered my original PDC and making Zentyal the BDC finally worked again!
This is not a Corperate environment, just my Home setup, but something could happen in a Corperate environment too.
With 3.3 and 3.4, I was able to shutdown my 230 watt consuming server, during the times that there was no electricity coming from my solar panels. With 3.5, when my PDC is down, lots of services, like http proxy and web server fail as soon as I make a change and save changes or after an update and reboot.
The zentyal log now (!) shows that these services are unable to reach my PDC, this while Zentyal itself is a BDC!!! As I said with 3.3 and 3.4 THIS WAS NOT A PROBLEM!!! Now it suddenly is!
My geuss is somebody hardcoded a PDC address somewhere, while in my opinion any LDAP related query should be handled by the BDC, if the PDC is not available!!! With 3.5 this is not happening, with 3.3 and 3.4 it was!
This can simply be replicated, if you have just 1 PDC and Zentyal is your BDC, remove the network cable from your PDC and reboot 3.5. HTTP proxy will fail to start, at least it does at my end ;-)
They removed something with 3.5 to clean things ups regarding LDAP, but in my opinion something was forgotten. Let me try to explain.
I had a 24x7 server running, which cost me a fortune on electricity, so I decided to buy a Zotac ID42 and use Zentyal as my home BDC, Internet gateway, proxy server, ad blocker etc.
I have my PDC running in a virtual 2008 R2 system and I finally managed with many reinstalls to get a working Zentyal 3.3. An upgrade to 3.4 worked just fine, but problems started happening again as soon as I executed the 3.5 upgrade. I managed to overcome this by a clean install, but the upgrade or me (?) corrupted my pdc. Because my PDC now thought it was a BDC. After several dcdiag and ntdsutil actions, I recovered my original PDC and making Zentyal the BDC finally worked again!
This is not a Corperate environment, just my Home setup, but something could happen in a Corperate environment too.
With 3.3 and 3.4, I was able to shutdown my 230 watt consuming server, during the times that there was no electricity coming from my solar panels. With 3.5, when my PDC is down, lots of services, like http proxy and web server fail as soon as I make a change and save changes or after an update and reboot.
The zentyal log now (!) shows that these services are unable to reach my PDC, this while Zentyal itself is a BDC!!! As I said with 3.3 and 3.4 THIS WAS NOT A PROBLEM!!! Now it suddenly is!
My geuss is somebody hardcoded a PDC address somewhere, while in my opinion any LDAP related query should be handled by the BDC, if the PDC is not available!!! With 3.5 this is not happening, with 3.3 and 3.4 it was!
This can simply be replicated, if you have just 1 PDC and Zentyal is your BDC, remove the network cable from your PDC and reboot 3.5. HTTP proxy will fail to start, at least it does at my end ;-)
3
Installation and Upgrades / Re: upgrade 3.4 to 3.5 failed
« on: August 15, 2014, 03:09:18 pm »
Not that I noticed and I did not check the zentyal log, because that's impossible to interpret.
I did a clean install of 3.5 and now almost everything is fine again.
I'll open a seperate issue because there is a serious 3.5 problem!
I did a clean install of 3.5 and now almost everything is fine again.
I'll open a seperate issue because there is a serious 3.5 problem!
4
Installation and Upgrades / Re: HTTP Proxy module won't start after update to 3.5
« on: August 06, 2014, 02:27:27 pm »
I had the same problem and my zentyal.log complained something about ldap, so I made the decision to remove the user and computer module and reinstall it, which made me lose all my domain information though. It gave me the standard Zentyal domain, but proxy filtering and caching worked again.
Up until now I am unable to rejoin my original 2008 R2 domain on a samba provisioning error, what ever that means. Up until no support or hints. I suggest you upload your zentyal.log en cross your fingers and hope somebody has time and is interested in looking at it.
Up until now they seem to be more busy with 3.6 instead of resolving this 3.4 upgrade to 3.5 challenge.
Up until now I am unable to rejoin my original 2008 R2 domain on a samba provisioning error, what ever that means. Up until no support or hints. I suggest you upload your zentyal.log en cross your fingers and hope somebody has time and is interested in looking at it.
Up until now they seem to be more busy with 3.6 instead of resolving this 3.4 upgrade to 3.5 challenge.
5
Installation and Upgrades / Re: upgrade 3.4 to 3.5 failed
« on: August 04, 2014, 11:39:39 am »
added log from todays attemp.
6
Installation and Upgrades / upgrade 3.4 to 3.5 failed
« on: August 01, 2014, 10:33:33 pm »
After finally managed to install 3.4 and running it for months successfully, i made the error to upgrade to 3.5 to soon. The upgrade seemed to run fine, but after a reboot a transparent proxy would not start. I had to uncheck it, for users to gain access to the internet without caching and rules.
The zentyal log complained about ldap, so I tried to recreate zentyal as a basic domain controller.
users and computers showed all users and computers in my domain before I started and in the end I got the basic Zential domain controller setup.
Like with 3.3 and 3.4 I now have again problems with making Zentyal an additional DC.
On my PDC I see my zentyal machine being added, but zentyal showes and error in the zentyal log with a text "Samba is not yet provisioned " and module users and computer is stopped and is not startable at all. Setting domain back to domain controller fixes everything except still the empty domain.
The 3.5 docs do not yet show how to rejoin a domain and what to remove on the Zentyal machine before attempting, like maybe removing all users from /home???
Does anybody already successfully rejoined a 3.5 with a Server 2008 R2 domain and wrote the steps down?
Thanks
Ron
The zentyal log complained about ldap, so I tried to recreate zentyal as a basic domain controller.
users and computers showed all users and computers in my domain before I started and in the end I got the basic Zential domain controller setup.
Like with 3.3 and 3.4 I now have again problems with making Zentyal an additional DC.
On my PDC I see my zentyal machine being added, but zentyal showes and error in the zentyal log with a text "Samba is not yet provisioned " and module users and computer is stopped and is not startable at all. Setting domain back to domain controller fixes everything except still the empty domain.
The 3.5 docs do not yet show how to rejoin a domain and what to remove on the Zentyal machine before attempting, like maybe removing all users from /home???
Does anybody already successfully rejoined a 3.5 with a Server 2008 R2 domain and wrote the steps down?
Thanks
Ron
7
Installation and Upgrades / Re: Reopen: Zentyal 3.4 create bdc failing on?
« on: July 11, 2014, 11:56:43 am »
Thanks, after almost 3 months, still a solution, great. Will there also be a 3.4 fix?
As i said with 3.3 i did not have this problem, did somebody change a samba module when moving from 3.3 to 3.4?
As i said with 3.3 i did not have this problem, did somebody change a samba module when moving from 3.3 to 3.4?
8
Installation and Upgrades / Re: Reopen: Zentyal 3.4 create bdc failing on?
« on: April 14, 2014, 02:04:55 pm »
With 3.3 my providers 150/10 down/up is not completely used, so I waste bandwidth.
With 3.3 only 90/10 was used and since NOBODY reacted on my post about that, I decided to retry 3.4 and although my bandwidth is now fully used, I still get this problem as soon as I make this machine an additional domain controller.
Within Windows domain, Kerberos and dns-user records are created and I see all my users and computers within the Zentyal users and Computers, but save changes fails with the above error and Zentyal's dns will not start anymore, making internet/Dns unavailable for me.n
When I disable the users and computers module, all packages are removed and after a reenable and install, I pick again the Domain Controller install option and I have again an initial Zentyal users and computers with 1 machine, 1 group and one guest user. This is much better then that 3.x "sudo /usr/share/zentyal/unconfigure-module users" command, after that I only had a complete empty Zentyal domain and a rejoin failed after that every time!
Did anybody have this problom too with 3.4 after joining a Windows 2008 R2 domain?
What can be wrong with my PDC/dns esspecially since joining under Zentyal 3.3 does not give any problem (besides the speed) with that same PDC/dns.
With 3.3 only 90/10 was used and since NOBODY reacted on my post about that, I decided to retry 3.4 and although my bandwidth is now fully used, I still get this problem as soon as I make this machine an additional domain controller.
Within Windows domain, Kerberos and dns-user records are created and I see all my users and computers within the Zentyal users and Computers, but save changes fails with the above error and Zentyal's dns will not start anymore, making internet/Dns unavailable for me.n
When I disable the users and computers module, all packages are removed and after a reenable and install, I pick again the Domain Controller install option and I have again an initial Zentyal users and computers with 1 machine, 1 group and one guest user. This is much better then that 3.x "sudo /usr/share/zentyal/unconfigure-module users" command, after that I only had a complete empty Zentyal domain and a rejoin failed after that every time!
Did anybody have this problom too with 3.4 after joining a Windows 2008 R2 domain?
What can be wrong with my PDC/dns esspecially since joining under Zentyal 3.3 does not give any problem (besides the speed) with that same PDC/dns.
9
Installation and Upgrades / Wrong domain when registering.
« on: April 07, 2014, 11:29:21 am »
Today I tried to register my Zentyal machine and although the correct name and domain are within System settings, the fqd is made up as nlamrt00.zentyal.me.
Within Users and Computers, ldap settings, I see root DN cn=zentyal,dc=nl1106,dc=eu ,
Read-only root DN cn=zentyalro,dc=nl1106,dc=eu
Why are these not cn=nlamrt00
And how can I correct it, although System, General, Hostname=nlamrt00 and domain=nl1106.eu
Within Users and Computers, ldap settings, I see root DN cn=zentyal,dc=nl1106,dc=eu ,
Read-only root DN cn=zentyalro,dc=nl1106,dc=eu
Why are these not cn=nlamrt00
And how can I correct it, although System, General, Hostname=nlamrt00 and domain=nl1106.eu
10
Installation and Upgrades / Re: Bypass proxy
« on: April 07, 2014, 10:55:14 am »
With Http Proxy general settings, I only see 3 choices, if Auth and Cache Exemptions is not the answer then I don't know.
11
Installation and Upgrades / Re: Problem fresh install
« on: April 07, 2014, 10:50:08 am »
Why didn't you just download the install CD, burn it and use that as install?
12
Installation and Upgrades / Re: zentya 3.4 issue with AD 2003R2
« on: March 28, 2014, 10:52:34 pm »
By now I must have already installed Zentyal about 20 times in 2 months time.
Each reinstall was because DNS stopped working and the only solution I could come up with, was a complete reinstall, because just uninstalling Zentyal-dns completely messes up my Zentyal domain and PDC.
As starters, ALWAYS first create a proven backup of your PDC, I need to restore my PDC before every Zentyal reinstall, because something within my PDC is changed after a join and a reinstall and rejoin of the domain, fails with unknown error. Probably the same as yours, so the questions is, is this really your first attemp to join a Zentyal machine to your domain, because if it isn't then...........
If it is your very first attemp, ensure date/time is exactly the same on all involved machines!
Run dcdiag on your PDC and correct any errors this might give.
Check that all your machines and users id's so they don't contain special characters , like mssql#2005#administrator.
Check within your PDC AD that no additional domain controller exist with the name of your Zentyal machine.
During the install, select the correct domain name and use a root account that is UNKNOWN on your PDC!
Finish the install as a standalone domain controller and at the end you should have a Zentyal domain with one machine and a geust account as soon as you enable
users and computers.
Test Internet and other stuff.
Create Proxy rules to filter unwanted web stuff as google-analytics.
Within Zentyal DNS menu, add your PDC machine/ipaddress to Zentyal's domain dns as a secondary dns server and add your PDC/DNS machine to hostnames.
Within DNS add external forwarders.
Within DHCP have Zentyal/DNS as primary and PDC/DNS as secondary.
If all is fine and working, make the machine an Additional Domain Controller and voila.
For me, this works flawlessly everytime, but as said, I HAVE TO RESTORE MY PDC for EVERY install. if I don't, then I am unable to join!
I already have an issue requesting information what exactly is changed or added to a PDC after a succesful or started and failing join!
This could fix your problem and saves me a restore!
Each reinstall was because DNS stopped working and the only solution I could come up with, was a complete reinstall, because just uninstalling Zentyal-dns completely messes up my Zentyal domain and PDC.
As starters, ALWAYS first create a proven backup of your PDC, I need to restore my PDC before every Zentyal reinstall, because something within my PDC is changed after a join and a reinstall and rejoin of the domain, fails with unknown error. Probably the same as yours, so the questions is, is this really your first attemp to join a Zentyal machine to your domain, because if it isn't then...........
If it is your very first attemp, ensure date/time is exactly the same on all involved machines!
Run dcdiag on your PDC and correct any errors this might give.
Check that all your machines and users id's so they don't contain special characters , like mssql#2005#administrator.
Check within your PDC AD that no additional domain controller exist with the name of your Zentyal machine.
During the install, select the correct domain name and use a root account that is UNKNOWN on your PDC!
Finish the install as a standalone domain controller and at the end you should have a Zentyal domain with one machine and a geust account as soon as you enable
users and computers.
Test Internet and other stuff.
Create Proxy rules to filter unwanted web stuff as google-analytics.
Within Zentyal DNS menu, add your PDC machine/ipaddress to Zentyal's domain dns as a secondary dns server and add your PDC/DNS machine to hostnames.
Within DNS add external forwarders.
Within DHCP have Zentyal/DNS as primary and PDC/DNS as secondary.
If all is fine and working, make the machine an Additional Domain Controller and voila.
For me, this works flawlessly everytime, but as said, I HAVE TO RESTORE MY PDC for EVERY install. if I don't, then I am unable to join!
I already have an issue requesting information what exactly is changed or added to a PDC after a succesful or started and failing join!
This could fix your problem and saves me a restore!
13
Installation and Upgrades / Re: zentya 3.4 issue with AD 2003R2
« on: March 27, 2014, 11:30:20 pm »14
Installation and Upgrades / Re: After ad-migrate and switch off orginal PDC no transparent proxy!
« on: March 26, 2014, 10:38:41 pm »
Just now I switched of only my pdc virtual machine and again internet access dropped.
My virtual Tribler machine was uploading at 1MBs, this dropped to 10Kbs as soon as the PDC/BDC machine stopped. After a restart of the PDC/BDC everything worked again!
I assume after the ad-migrate my orginal PDCis now a BDC, why can't I switch it off, why does Zentyal react as it does?
Thanks
My virtual Tribler machine was uploading at 1MBs, this dropped to 10Kbs as soon as the PDC/BDC machine stopped. After a restart of the PDC/BDC everything worked again!
I assume after the ad-migrate my orginal PDCis now a BDC, why can't I switch it off, why does Zentyal react as it does?
Thanks
15
Installation and Upgrades / After ad-migrate and switch off orginal PDC no transparent proxy!
« on: March 26, 2014, 10:22:35 pm »
After a succesfull ad-migrate my Zentyal machine works perfect and users are able to access the internet and the filter profile works great. No more dirty pictures and unwanted popups.
All fishing stuff like doubleclick are denied, all is fine until I powerdown my orginal server with my previous PDC, IIS and database server. None of these machines are used by my Zentyal setup, except as hostnames.
The dns reference of my old PDC are also removed from my zentyal machine within dhcp and DNS, so???
As soon as I switch the server off, all internet access is gone or very very slow, until I disable transparent proxy, then all internet access works, but of course no filtering!
This morning I switched on the old server reenabled transparent proxy and all is fine again, leaving me clueless.
Regards
All fishing stuff like doubleclick are denied, all is fine until I powerdown my orginal server with my previous PDC, IIS and database server. None of these machines are used by my Zentyal setup, except as hostnames.
The dns reference of my old PDC are also removed from my zentyal machine within dhcp and DNS, so???
As soon as I switch the server off, all internet access is gone or very very slow, until I disable transparent proxy, then all internet access works, but of course no filtering!
This morning I switched on the old server reenabled transparent proxy and all is fine again, leaving me clueless.
Regards