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 - nubro01

Pages: 1 [2] 3
16
Could somebody explain what exactly is updated within your PDC as soon as you join your Zentyal machine as an additional domain controller?
Within ADUC I see the Zentyal machine being added as domain controller,
I see a kerberos http-zentyal and mail-zentyal entry created and dns entries.
When I reinstall Zentyal 3.4 or 3.3, without restoring my PDC, I am unable to join.
If I delete the Zentyal dc within UDUC, it is created again as soon as I try to join, but no machines and users are created within the Zentyal machine and the join fails.
After a restore of the PDC and retrying the join, all goes fine, so???
Why does a rejoin fail without a restore and why is a second initial Zentyal Domain controller not setup as like as with a complete reinstall?
Using the command: sudo /usr/share/zentyal/unconfigure-module users gives me the install choice, but then also just an empty domain is created. No Zentyal machine is added to the new domain and also no guest account is created!

Thanks

17
Installation and Upgrades / Zentyal 3.3 network performance
« on: March 25, 2014, 11:07:05 am »
Hi, some of you probably already read my 3.4 remarks and my final return to 3.3, but I forgot why I even tried 3.4. A few days after my successfull return to 3.3 I realised why.
I have a 150 MBs download and 10 MBs uploaded internet subscription and when I test the speed with speedtest.net or upc.nl/speedtest, I only get 67 MBs down and 10 MBs up, so <half of my download.
My traffic interface rules are, up 16384 Kb/s and down 163840 Kb/s the same as with 3.4.
With 3.4 I had full speed.
I could try Ubuntu  network performance tips, because I found no Zentyal network tuning tips.
Any suggestions?

Thanks

Ron

18
Thanks, the section about the free command would suggest that indeed programs are loaded into memory directly and when memory fills up, unused program pages are swapped out.
For windows I think, that a program is loaded first into virtual memory and then the first pages with the startup and initialisation parts are loaded within real memory and the rest is loaded from virtual memory when needed. I must admit this knowledge is from the beginning of virtual memory, which is for me IBM dos/vse, back in the 70ths. I always thought that MS acted the same way, but I can be wrong of course, because memory is now cheap and newer windows os, might do it now differently.
Still having a second disk under windows and allocating virtual memory on it, gives me the impressing of twice as fast loading. ;-)

19
Installation and Upgrades / Re: Problem dns and Android 4.1
« on: March 25, 2014, 10:24:50 am »
I tried splitting my local and external domain by using .lan and .eu too, but i ran into problems, which i forgot. So i can't suggest anything more, besides abandon the .lan for your intranet and just use the intranet domain.
good luck.

20
If two disks, I would alway create a swap and home partition on the second disk.
With windows i know a program load twice as fast, because reading a program, always puts it first within virtual memory and then the starting code is loaded in real memory. I geuss Linux works the same? Having one disk reading the program and one disk writing virtual memory....
Then again naming it swap, could mean, the program is loaded first in memory and then not used code, is swapped out, if memory usage gets to high, hence  the vm.swappiness and vm.vfs_cache_pressure settings regarding SSD disks. Who knows an url which explains this better?

21
Installation and Upgrades / Re: Problem dns and Android 4.1
« on: March 23, 2014, 11:55:55 am »
I have installed ping& dns on my android tablet, so I can always check if I have the correct settings.
Are you sure you have the correct dns ip address within your android device?
And also important, did you define forwarders within Zentyal?
You also need a WINS server defined, because someting needs to gather intranet machine names and add them to dns.

22
Dutch / Re: Uitwiseling ervaringen
« on: March 20, 2014, 10:29:19 am »
Nou, vanmorgen terug gegaan naar 3.3. Bij de partitionering wordt de SD Mybook 3tb SWAP partitie van 1.2 gig gezien als een 149 mb partitie en de /Home van 3TB als 379.9 mb.
Deze gelaten voor wat ze waren, want alles was goed na de installatie.
Binnen 1 uur had ik weer een werkende bdc en zelfs webmail doet het ook weer.
Wat mij betreft blijf ik de komende jaren op Zentyal 3.3 en laat ik 3.4 met Ubuntu 13.10 links liggen.

Bedankt voor het meedenken! Na 38 jaar in de ICT, nu al weer 4 jaar thuis. Mis collega's om mee te brain stormen, zeker nu ik geen MSDN licentie meer heb en ik over moet op open source.
Men kan zeggen wat men wil over Microsoft, maar zij bepalen wat er gebeurd, daar waar men met Linux, als het niet bevalt een eigen versie kan beginnen, waardoor e.a. een hele grote puinhoop wordt.
Verschillende dns, proxies, xwindows en ga maar door. Voor mij is het erg moeilijk, om door al die verschillende bomen het bos te zien. Dan valt die ene grote boom van Microsoft, alleen in het landschap veel duidelijker op!
Maar het moet ook gezegd worden dat Zentyal 3.3 met Ubuntu 12.04 een uitstekende vervanging is voor SBS2003 en mijn PDC op mijn Windows 2008 R2 domein.
Mijn server kan nu uit en ik bespaar 200 watt 24x7.

23
I went back to Zentyal 3.3 and all is working fine.
Even webmail is functioning again!

I got the same error of 0 SOA records found within my 3.3 syslog, when I activated the BDC functionality, so that was not the cause. What it was, I have no clue, but for one, I would not recomment people tot move to Zentyal 3.4. probably the underlying Ubuntu 13.10 is the problem, because the 3.3 and 3.4 install differ a lot!
As I said I use a Zotac ID42 with two nics, the top nic is my intranet, the lower my internet connection.
3.3 comes up with eth0, eth1, wlan0.
3.4 comes up with p1p1, p4p1, wlan0.
For 3.3 I have to pick the second choice (eth1) and for 3.4 the first p1p1. Later on they are renamed to eth0 and eth1.
Because of the different order, I am unable to initially set the correct DHCP setting for eth1 in 3.4.
Because only the first choice gives you dhcp, static, second and third only give no configure and static.
With 3.3 I am able to set mount options for my ssd to noatime, with 3.4, I can not!

3.4 is a nogo for me! Geuss people advising against Ubuntu 13.10 are correct!

24
Installation and Upgrades / Re: Zentyal 3.4 create bdc failing on?
« on: March 19, 2014, 09:23:23 pm »
I saw that, but what zone is invalid?
This same PDC worked fine when I created a Zentyal 3.3 BDC.
I'll run a dcdiag and investigate what soa means.

25
Dutch / Re: Uitwiseling ervaringen
« on: March 19, 2014, 09:16:58 pm »
Met 3.3 kon ik niet echt de 3TB partitioneren, hij zag geen 3TB maar een stuk minder. Dit zelfde heb ik ook wel eens met windows gehad, toen 3TB schijven net uit waren.
Ik heb eerst Ubuntu 13.10 server geïnstalleerd en die gaf geen problemen met partitionering.
Met Zentyal 3.3 zag ik toen, wat er gemaakt was en kon toen gewoon de partities hergebruiken, ook al klopte de informatie qua grote niet.
Dit zou ook kunnen komen omdat de WD Mybook essential een 4kb cluster heeft!

26
Installation and Upgrades / Re: Zentyal 3.4 create bdc failing on?
« on: March 19, 2014, 09:11:34 pm »
Syslog attached. I used a Dell D610 with two nics with server 2003 and isa 2006 before, I replaced that with this Zotac ID42.
Within my home intranet I have a 2008 R2 server with Hyper-v and one virtual machine acting as a PDC with Server 2008 r2. This domain was created from a previous SBS2003 domain and worked perfectly for the last 4 years. So just one single domain, nothing fancy, only about 30 user accounts for local access and remote ftp.

I hope you see something that I am missing, else I have to go back to Zentyal 3.3.

thanks

Ron

27
With 3.3 i encountered usernames containing #, so I fixed these and I was able to reinstall 3.3 and make it a windows 2008 r2 BDC.
All 3.4 betas up until the last two daily builds and the GA (General Available) went fine at install time, but after a day they gave dns problems every time one day after successfull install or when I activated mail modules.
This morning I reinstalled again the 3.4 GA build and after 45 minutes I had a successfull running machine and people could browse the internet through this machine. All was fine and working until I tried to make it a BDC.
I got;

The following modules failed while saving their changes, their state is unknown: samba The following modules failed while saving their changes, their state is unknown: samba at Trace begun at /usr/share/perl5/EBox/GlobalImpl.pm line 735 EBox::GlobalImpl::saveAllModules('EBox::GlobalImpl=HASH(0x3d62678)', 'progress', 'EBox::ProgressIndicator=HASH(0x29f8168)') called at /usr/share/perl5/EBox/Global.pm line 95 EBox::Global::AUTOLOAD('EBox::Global=HASH(0x3d664b0)', 'progress', 'EBox::ProgressIndicator=HASH(0x29f8168)') called at /usr/share/zentyal/global-action line 32 eval {...} at /usr/share/zentyal/global-action line 30

Within my pdc I saw the machine being created as domain controller and also within my domain dns a dns-account was created. (see attached zentyal.log)
The attached log was created after I did a sudo apt-get remove zentyal-samba and reinstall.
Before this final try, I already reinstalled 3 times today, everytime with the same result.

Although IBM and microsoft certified, I am unable to understand why things are failing.
I bet, if I try 3.3 all will go just fine, as before, so???
Who can hint me on how to determine and repait this?

Thanks

Ron

28
Dutch / Re: Uitwiseling ervaringen
« on: March 19, 2014, 07:46:49 pm »
Daar kwam ik al in 3.3 achter en ik heb toen alle oude en foute gebruikers namen verwijderd.
Daarna ging na een reinstall alles goed. De twee laatste betas en GA (general Available) van 3.4 gaan opeens weer fout zodra ik e.a. als additional domain controller maak.
Ik zie in mijn pdc dns de nieuwe machine verschijnen, in AD zie de machine naam ook als domain controller verschijnen, maar de machine en gebruikers worden niet over genomen.
ik krijg;
The following modules failed while saving their changes, their state is unknown: samba The following modules failed while saving their changes, their state is unknown: samba at Trace begun at /usr/share/perl5/EBox/GlobalImpl.pm line 735 EBox::GlobalImpl::saveAllModules('EBox::GlobalImpl=HASH(0x3d62678)', 'progress', 'EBox::ProgressIndicator=HASH(0x29f8168)') called at /usr/share/perl5/EBox/Global.pm line 95 EBox::Global::AUTOLOAD('EBox::Global=HASH(0x3d664b0)', 'progress', 'EBox::ProgressIndicator=HASH(0x29f8168)') called at /usr/share/zentyal/global-action line 32 eval {...} at /usr/share/zentyal/global-action line 30

Het ziet er naar uit dat ik maar weer terug moet naar 3.3, maar die doet moeilijk met 3TB 4kb clusters.

Bedankt

Ron

29
Installation and Upgrades / Re: Migrating from SBS2003
« on: March 19, 2014, 02:49:22 pm »
I am trying to get rid of my old 2008 R2 PDC too and have been strugling for weeks now.
One thing! Be sure to have a backup of your PDC, if things get corrupted you can restore it.
I installed Zentyal 3.4 beta a couple of times to a Zotac ID 42, with a 240 GIG SSD and 3TB WD mybook essential, using a image on CD.
The install with Ubuntu 13.10 has some flaws, like no mount options, for SSD noatime, nodiratime, when partioning the disks.
With 3.3 this did work!
Next the initial configuration wizard doesn't give you a choice in configuring eth1 and wlan0 (only no config and static option, there is no dhcp choice) , but later when the Dashboard comes up, you can configure your network properly.
When user and groups comes up, enter the your present domain name and go for domain controller, because in the end we want to disable the windows PDC!
The next steps did go ok the previous times, but the GA 3.4 version gives me problems with Samba.
Normally within the domain setup, I changed from domain controller to additional domain controller and after applying changes, the windows domain was replicated and Zentyal became my BDC.
I hope your effort goes as smoothly as my 3.4 beta did, it only took 45 minutes for me to get a working system, where people access the internet through my Zentyal 3.4.

30
Dutch / Re: Uitwiseling ervaringen
« on: March 18, 2014, 08:14:57 pm »
Nou, ik heb vandaag dus Zentyal 3.4 geïnstalleerd en e.a. zag er in het begin erg goed uit. Geen problemen, maar net als met de 3.4 beta feb 25 build, begonnen de problemen, nadat ik mail modules geïnstalleerd en geactiveerd had.
Ik heb thuis een Microsoft 2008 R2 domein en dat wordt initieel goed door Zentyal 3.4 overgenomen, maar ik heb de indruk dat door mijn geklooi in het verleden, ik bepaalde gebruikersnamen had die niet helemaal lekker waren en die ook als fouten in de zentyal.log kwamen. Het waren oude namen voor sqlserver 2005 met hashes (#) tussen de naam delen. Ik vermoed dat iets de dns database verknald heeft, maar wat ik ook probeer ik krijg dns niet meer gestart.
In de zentyal.log staat alleen maar, start bind9 failed, nou daar heb ik dus helemaal niets aan.
Bij de beta dacht ik, nou ik verwijder dns en herinstalleer, nou dat werkte wel, wat dns betreft, maar mijn hele Zentyal bdc werkte niet meer omdat bij de dns verwijdering ook alle afhankelijke modules zoals users & groups en file en domain services verwijderd werden. Na herinstallatie vertikte een bdc (backup domain controller) activatie van ZENTYAL het.
Na de herinstallatie van de officiële Zentyal 3.4 liep e.a. weer goed, tot de mail service activatie, dus .....
Iemand enig idee hoe ik dit dns probleem kan onderzoeken? Ik ben IBM mainframe en Microsoft  gecertificeerd, maar na 40 jaar ontslagen en kan me nu geen dure legale Microsoft licenties voor thuis meer veroorloven, dus is Zentyal een redelijk alternatief.

Bedankt

Ron

Pages: 1 [2] 3