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

Pages: 1 2 3 [4]
Installation and Upgrades / Ebox 1.3.6 bug with virtual hosts
« on: October 21, 2009, 06:10:31 am »
I setup 5 different virtual hosts using 1.3.3 and this past weekend updated to 1.3.6 and tried to create a virtual host today under the web server module only to receive the following error:

          Invalid value for Virtual host's name: vhost. The virtual host name supplied is a top domain name

However, the vhost name that I used is not in the DNS at all so I don't understand the conflict.  I'm assuming this is a bug and wanted to let people know about it if it wasn't found already.

After poking around the new ldap config files I finally understand a little about how they work.  I figured out that I was wrong on the base dn and admin.

base dn: dc=nodomain
admin dn: cn=admin,dc=nodomain

Ebox 1.3.3 no longer overwrites the password you create when installing the usersandgroups module so whatever you typed in the prompt for libnss-ldap will be the password for the client when you install the ldap packages.  Just follow the original howto (linked above) but replace the new base and admin dn.

Installation and Upgrades / Ubuntu LDAP client with Ebox 1.3.3 on Jaunty
« on: September 24, 2009, 07:18:38 am »
I decided to upgrade my server to Jaunty and therefore had to go with Ebox 1.3.3 so the instructions I followed from no longer work.  Just wondering if anybody could point me in the right direction for getting a client connected to the LDAP server database since so much has changed since Intrepid with LDAP configuration.  I think these are the main differences in configuration between the howto listed above and what needs to be done now but wonder if somebody could confirm.

      Base dn:  cn=ebox,dc=nodomain
      Admin dn: cn=admin,dc=config
      Admin Pass: e2NyeXB0fUZrV3k1RzNlQURqaEU=  (This may vary...verify in /etc/ldap/slapd.d/olcDatabase={0}config.ldif)
      Domain Name:  EBOX (Whatever you set it  to when you setup Samba as PDC)
      Ebox Server IP/hostname:  (If you setup dns a hostname.domain would be better but an IP will work)

I have tried the above settings and it still fails to list the LDAP users when typing "getent passwd" and I'm not sure if ebox-desktop is update for 1.3.3 on Jaunty so I haven't pursued that route.  Thanks in advance for any insights offered.

Installation and Upgrades / Re: eGroupware sync
« on: June 08, 2009, 08:56:56 pm »
Thank you cheesyking.  I was only making appointments not meetings so Evolution doesn't let you add participants to appointments.  I never thought to look at meetings cause we don't do those.  :)  Now I feel stupid that is was something so simple.

Installation and Upgrades / Re: Squid + windows update
« on: April 23, 2009, 03:51:17 am »
I know this used to work back in November when I configured those lines on an Ebox machine and then downloaded updates on one machine then the other 2 downloaded extremely quick from the Squid server.  However, it appears this no longer works as it now takes just as long on each machine to get new updates.  Does anybody know if M$ did something and if there is an easy alternative to cache updates again?

Installation and Upgrades / Re: eGroupware sync
« on: April 17, 2009, 09:44:48 pm »
I've tinkered around with the "Grant Access" settings in the web interface for EGroupware but haven't had any luck getting the entries to show across different user's calendars in Evolution.  Perhaps it's just not possible yet.
For me this works. Just login with your eGroupware account, go to your calendar and select the user or group you'd like to see in your calender. This other user of course needs to grant access to your user (or group to which your user is assigned to).

Just to clarify you used the EGroupware web login to configure the shared access with calendars and of course were able to see them there.  Afterwards syncing with Evolution you only had to add the credentials for user1 on one machine and user2 on another machine and the calendars on the local Evolution installation sync across?  I must be unlucky if that's the case cause the EGroupware web access syncs perfectly between the users (groups in this case) but I had to add credentials in Genesis for both users on both installations.

Installation and Upgrades / Re: eGroupware sync
« on: April 09, 2009, 06:40:28 am »
First I would like to apologize for posting that message when the answer was above.  The night before I posted it I read through the entire post and since it wasn't there decided to research the next day but after finding nothing posted without reading the update.  :)

On another note, I followed those directions and they worked beautifully so thanks for those.  Now my question is has anybody gotten calendar sharing to work cause I have my account synchronizing on my computer but would like to have the entries added from another user's account.  I've tinkered around with the "Grant Access" settings in the web interface for EGroupware but haven't had any luck getting the entries to show across different user's calendars in Evolution.  Perhaps it's just not possible yet.  :(

Installation and Upgrades / Re: eGroupware sync
« on: April 07, 2009, 08:10:55 pm »
Thank you very much for this post it is exactly what I was looking for this week.  Although I do have a problem since I'm trying to use Evolution to sync which according to EGroupware's site it is compatible with SyncML so I'm not sure how you put the settings into Evolution.  Has anybody else set it up with Evolution?  Last I checked Thunderbird doesn't have a notes application but if that has changed then I guess I can switch I prefer Thunderbird anyway.

Installation and Upgrades / Re: Thin Client
« on: April 04, 2009, 06:42:45 am »
This is a tip that will save you some time (I spent hours thinking I did something wrong with the LTSP setup).  You need to allow a few ports in the firewall under "internal networks to ebox".  This information came from

syslog 514 tcp
sieve 2000 tcp
unknown 9571 tcp

If you don't have those ports allowed you'll be able to login but it will be extremely slow and give error messages but never reach the complete desktop with the panel and everything.  Ebox is locked down tight which is great but if you aren't aware your applications use something bizarre then it's not fun to figure out.  :)

Installation and Upgrades / Multiple PXE boot services howto
« on: March 31, 2009, 05:54:27 am »
Ebox has built in support for adding network boot files into the DHCP server which is great and does work well.  However, I wanted to do 2 services via PXE boot one for new Ubuntu installs on workstations and the other for LTSP on a couple machines I have.  So I setup the PXE boot file for the global section in Ebox through the standard GUI interface as normal nothing special had to be done there to make the network installs work.  Of course I want the network installs to be global so every machine besides the ones I specify can do a new install if desired.  In order to make a certain machine have different boot options custom fields must be added to the the fixed IP section of that host.  Since I only have 2 machines that I want to LTSP boot I made the following change to /usr/share/ebox/stubs/dhcp/subnet.mas file on line 27:

*The following code was completely thanks to sixstone.  Thanks for your help with this!

%          foreach my $fixed (@{$fixedAddresses}) {
      host <% $fixed->{'name'} %> {
         hardware ethernet <% $fixed->{'mac'} %>;
         fixed-address <% $fixed->{'ip'} %>;
%          if ( ($fixed->{'name'} eq 'host1') or ($fixed->{'name'} eq 'host2') ) {
            filename "/ltsp/i386/pxelinux.0";
            option root-path "/opt/ltsp/i386";
%          }
%             }

I added the entire foreach loop in case the line ever changes from being on line 27 so you know where it needs to go.  Of course you'll need to change host1 and host2 with the names that you provide under the static IP settings in the DHCP configuration of Ebox.  Hope this helps someone else that wants to accomplish the same task.

I figured it out late last night. As soon as I enabled all TCP traffic on port 80 under "coming out from Ebox" it started allowing the traffic and my proxy works.  Thanks for the help though and hopefully it assists you in fixing the bug (if it is a bug).

I left the port on the proxy to the default 3128 and enabled firewall rules to allow requests coming into Ebox from the outside on 3128 and going out from Ebox on 3128.  I tell a workstation in Firefox to go to my IP address for the proxy at port 3128 and I can browse any content when I put "always allow" in the general settings but whenever I tell it to "filter" all browsing is denied not with the content block filter but with an access denied error.  Are there other rules I need to add to the firewall to let workstations use the content filtering?

Pages: 1 2 3 [4]