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

Pages: [1]
Good-day Folks,

I've been running Zentyal v7.0.5 on a small church network for a few months now without any issues, then all of a sudden this past weekend, I got an error while attempting to make an edit to a Group Policy Object via the RSAT Group Policy Management Console from a Windows 10 workstation.  The error message simply said "There is Not Enough Disk Space".

I am unable to create any new GPOs as well, but strangely I can delete them.  When I access the SYSVOL folder from Windows Explorer, I am unable to create any files in the folder (as a quick test, so I'm suspecting perhaps some permissions have changed but can't figure out where).

This is what I see in "/var/log/samba/samba.log" -

I see one other post on here with a similar issue - - but their solution doesn't seem to work for me.  Any help is very much appreciated, thank you.

Thanks for sharing your solution.  I, too, ran into this very problem and running "samba-tool ntacl sysvolreset" resolved it for me.  It would be helpful, if the developers would see this and try to determine what the root cause is and find a way to mitigate it.

Email and Groupware / Zentyal 7.0 Fetchmail Not Working Anymore
« on: October 11, 2021, 09:00:44 pm »
Good-day folks,

Hope you're all doing well.  So, I'm testing a Zentyal 7.0 installation as a Proof of Concept for my company; to have Zentyal serve as our Primary Domain Controller, DNS, and Groupware Server.  I managed to create an account for myself and was testing the Groupware functionality.  I successfully enabled the "Retrieve External Emails" functionality and was able to fetch emails from our external mail provider.  However, due to a minor configuration mistake I made with the stub file for fetchmail, I ended up getting lots of duplicate mails.

So I reverted the change I made, leaving the original config file and rebooted the server.  Now, fetchmail refuses to retrieve external mails and is throwing the following error message:

Code: [Select]
Oct 11 14:21:27 dc01 fetchmail[3605]: socket error while fetching from
Oct 11 14:21:27 dc01 fetchmail[3605]: Query status=2 (SOCKET)

I've restarted the mail module from the admin interface, and rebooted the server; still it's not working.  Has anybody see this happen with their Zentyal 7.0 instance?

Hello guys,

I just deployed a Zentyal 2.0 box in testing mode and I want to know if it's possible to join computers from a remote office - on a different subnet - to the domain.

I have two networks connected via VPN Tunnel through a Cisco 2901 router on both ends:

  • Site A ( (Main Site where DC resides)
  • Site B ( (Remote site)

  • I can ping the DC using both the FQDN and IP from within Site A.
  • I can ping the DC using IP from Site B but not FQDN
  • After modifying the hosts file on a pc in Site B, I can ping the DC using the FQDN

Thus far I have had no problem connecting PCs within the same subnet to the domain.  I just can't get the PCs from the remote office (Site B) to connect to the domain.  Would love any assistance that can be given, thanks.


This possible if you're subscribed to a support services...

I get your point, but I want to know if this will work before committing the money to purchasing the server(s).  I need to know if I will need only one server located at the main office, or one each in each building with different domain names.  I already have approval for the project and funds have been committed, but I want to make sure this will work first.

Please take into consideration that other people who contributed to answer (for free) posts in the forum have jobs too. Do your homework and provide as much information you can to the community. This way people will be more interested in answering them.

I understand that everybody here has a job, as I said I didn't mean to be hasty.  Now can you offer me some real help, as opposed to pointing me to purchasing a support subscription?

Thanks guys................

Installation and Upgrades / Re: Can't Connect to LDAP
« on: August 24, 2011, 10:38:15 pm »

Good  ;D

So, I read the documentation for the DNS component which instructed me to edit the /etc/ebox/80dns.conf.  I used nano to edit the file and added the following line (which is the subnet of our remote office connected to us via vpn tunnel):

Code: [Select]
intnets =
  could you please explain:
- purpose of this
- Why edit of config file was required (do you mean this change was not available using Zentyal GUI?┬░

I read the documentation (URL and it was saying something about how it might be necessary to use DNS cache in order for networks not defined to be able to access the server.  So I took that to be a solution to why I can't connect to the server from our remote office using FQDN instead of the IP (which I don't have a problem with).

Unfortunately there isn't a feature to do this via the admin interface, so I had to edit the file as per the instructions in the documentation.  - still no success, I can't connect to the LDAP database from the remote office.

Then I added an ALLOW entry in FIREWALL>PACKET FILTER for the ldap service.

I don't know if this is a typo in your previous mail but LDAP uses ports 389 and 636 not 631

This - indeed - was a typo.

I don't have any Outlook client here  :-[  or  8)....  ;D
Once you have found where to define addressbook, settings to be reported here are those you will find in Zentyal's LDAP section in term of baseDN.

I am able to connect to the LDAP database from within the same subnet that the server's on and It seems I am able to configure an LDAP Address Book in Outlook, however, when I run a query it gives me an error message which says:

"The search cannot be completed.  MAPI_E_CALL_FAILED"

Here's the LDAP settings as displayed in the admin interface:

Code: [Select]
Base DN: dc=server1,dc=centraltruck,dc=com
Root DN: cn=ebox,dc=server1,dc=centraltruck,dc=com
Password: yz6uzO51RMUtilWV
Users DN: ou=Users,dc=server1,dc=centraltruck,dc=com
Groups DN: ou=Groups,dc=server1,dc=centraltruck,dc=com

NOTE: PAM is disabled.  I'm not sure if I need it (reading the description of what it is, I'm not sure I want my users to be able to open sessions on the server).  I assume by sessions, they mean an actual connection to the CLI right?

One final note - is a domain name I made up during the installation.  It doesn't actually exist (at least with my understanding of what a domain name is - as in a web address pointing to an ip address).

Installation and Upgrades / Re: Can't Connect to LDAP
« on: August 24, 2011, 04:44:12 am »

So, I read the documentation for the DNS component which instructed me to edit the /etc/ebox/80dns.conf.  I used nano to edit the file and added the following line (which is the subnet of our remote office connected to us via vpn tunnel):

Code: [Select]
intnets =

I restarted the DNS service.

Then I added an ALLOW entry in FIREWALL>PACKET FILTER for the ldap service.

After doing that I opened the command prompt on a workstation in the local office and one in the remote office and ran the following:

Code: [Select]
telnet 389

I got a blank screen with the cursor blinking - so I assume that the ldap server is responding.

Now I don't know how to actually enter the database information into an address book such as Outlook to query the database.  Can somebody please help.

Robb and Marcus,

Sorry for seeming "hasty" 

I guess as a newbie to Linux I was expecting that there would be people online who were always ready to spit back and answer - guess that's not quite true.  I'm not upset or anything, so please don't take it that way.

I did manage to reinstall from the CD and everything's working fine now - except that everytime I try to start the DHCP module it fails telling me about some uninitialized value.  I manage a network with two subnets connected via site-to-site VPN and I'm having a hard time getting the PCs on the other subnet to find the Primary Domain Controller.

Anyway, so I'm working on that at the moment.


Installation and Upgrades / Re: Can't Connect to LDAP
« on: August 24, 2011, 02:36:57 am »
Thanks Christian and Sam.

I'm going to remote into the server right now and turn on the DNS module.  Once it's up and running, I'll check the firewall rules from the admin interface to make sure that either the LDAP service or port 389 and 631 are open.

I will report back........................

Installation and Upgrades / Re: Can't Connect to LDAP
« on: August 23, 2011, 12:54:42 pm »

Thanks for your quick response.  I will elaborate as requested.

The Zentyal box is sitting behind a firewall on our lan - that's not a problem since I don't intend on allowing traffic from the internet to access the box.

What I mean by NO ACCESS is that I can't get a mail client such as Outlook or Outlook Express to connect to the LDAP using the address book.  Now, I don't know if I'm entering the LDAP database info wrong or I didn't set it up right.  I don't know how to check for it on the server.

I've googled to find instructions but all I keep finding is pointing me to a config file that should be residing in /etc/ldap/ldap.conf - but mine doesn't live there.  It's actually in /etc/ldap.conf - the file that's at /etc/ldap/ldap.conf is different and doesn't have the configuration info that's in the /etc/ldap.conf file.

Now when I check the LDAP settings from the Admin Interface, the settings are showing as I listed above.

One thing though, does the DNS need to be running in order to resolve the address?  At the moment, the DNS module is disabled.

Installation and Upgrades / Can't Connect to LDAP
« on: August 23, 2011, 04:44:38 am »
Hello guys,

I'm new to Zentyal 2.0 and Linux - alltogether.  I've done all I can - google searches and other things to figure out how to get my users to be able to connect to the LDAP server from their mail clients such as Outlook.  However, NO SUCCESS.

When I check the Ldap settings under the Users and Groups, here's what I find:

Code: [Select]
Base DN: dc=server1,dc=centraltruck,dc=com
Root DN: cn=ebox,dc=server1,dc=centraltruck,dc=com
Password: XXXX
Users DN: ou=users,dc=server1,dc=centraltruck,dc=com
Groups DN: ou=Groups,dc=server1,dc=centraltruck,dc=com

Now, it's important to note that the domain name I'm using was made up.  I followed the instructions in the installation - to make up one.  I'm new to databases so I'm not sure if this is right.  However, it must be - because the PDC is working fine and I've been able to connect two Windows XP workstations to the domain without a problem.

I should also point out that all my research about slapd shows that the conf file should be in /etc/ldap/ldap.conf  - however, it's not.  It's actually located at /etc/ldap.conf.  So I don't know if something is causing this to be off - or perhaps there's nothing wrong.

There is an ldap.conf file located in /etc/ldap/ however, it's different from the one located in /etc/.

I might be doing something wrong, but would really love it if somebody could help me.  I'm really looking forward to testing this as a solution for my company (as opposed to getting a Windows Server with all the ACL expenses that comes with it).

So far everything is working perfectly - EXCEPT FOR LDAP.

Sincerely Yours,


Installation and Upgrades / Re: Cannot Reach Admin Interface
« on: August 19, 2011, 04:56:15 pm »
I guess nobody on here wanted to touch this topic.  Anyway, I ended up reinstalling Ubuntu 10.04 Server and reinstalling Zentyal 2.0.

Installation and Upgrades / [SOLVED]: Cannot Reach Admin Interface
« on: August 19, 2011, 03:19:50 am »
Hello Guys,

I'm totally new to the Ubuntu/Linux environment and I just installed Zentyal 2.0 today.  I'm working on a HP/Compaq ProLiant ML310 G1 Server with Ubuntu Server 10.04 installed.

This is what I was doing:
I had just managed to finish the installation and configuration process.  Zentyal saved its settings then I rebooted the machine.  After reboot, I entered the interfaces section and changed eth1 from dynamic to static and assigned an ip address.  I then hit the "Save Changes" button in the top-right corner, and that's where I believe the problem started.

The saving process stalled on the 11th or 12 processes which I believe was the "Firewall" settings.  I think Zentyal was trying to save the new IP for the second interface to the firewall settings when the system hung.  So I was forced hit F5 to refresh the browser - and that's when I lost connection to the server.  From this point on all pings to both interfaces are unsuccessful.


sudo /etc/int.d/ebox firewall stop

I've tried using that command to stop the firewall - thinking that's what's blocking all connections to the server

Beyond this, I don't what else to do.  I've tried searching the forum but can't find any solutions.  I saw one post here,7082.0.html and it's marked as solved, but I don't see anything information in there that'll help my situation.

Your help would be greatly appreciated.


Pages: [1]