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

Pages: 1 ... 61 62 [63] 64 65 ... 67
931
Installation and Upgrades / Re: Can't create ldapi connection
« on: April 15, 2008, 03:03:05 pm »
Please, when trying to join the machine to your domain, take a look at the logs stored in /var/log/samba/*

A stupid question, both machines are in the same network, right?

I successfully added windows XP SP 1 machines to eBox. What's your windows box?

932
Installation and Upgrades / Re: Can't create ldapi connection
« on: April 15, 2008, 12:43:32 pm »
So  could you add machines to the PDC before you had to reinstall ebox-samba and stuff?

If that's the case, maybe there's some kind of inconsistency due to the reinstall. You could try purge samba along with ebox-usersandgroups and ebox-samba and reinstall again following the above steps. That should give you a completely clean installation as far as samba is concerned.

933
Ok, let's go step by step:

Can you post the output of the following commands please:
Code: [Select]
ps aux | grep apache
Code: [Select]
sudo netstat -laptn | grep apache

Thanks!

934
Installation and Upgrades / Re: Samba + ClamAV?
« on: April 14, 2008, 08:24:28 am »
It doesn't yet. But it would be a nice feature to add

935
Installation and Upgrades / Re: Can't create ldapi connection
« on: April 14, 2008, 08:23:09 am »
Did you reboot the machine? If you did and you didn't have the last available version of slapd, it's probably, as drdebian says, that slapd didn't start properly at boot time. Make sure you update your slapd package.

Anyway,  as you removed slapd now you have to initialise the openLDAP directory and configure samba again. You have to keep in mind that for eBox your slapd directory and samba have already been initialised. That initialisation takes place when you enable the module for first time.

I have a script to set the service as not configured, this way you are able to go to module status and enable the module again.

This is the script:

Code: [Select]
#!/bin/perl

use EBox;
use EBox::Global;

EBox::init();

my $module = $ARGV[0];

unless (defined($module)) {
    print "Usage: $0 module";
    exit 1;
}

my $global = EBox::Global->getInstance();

unless ($global->modExists($module)) {
    print "Module $module doesn't exists";
}

my $mod = $global->modInstance($module);
$mod->st_set_bool('_serviceConfigured', undef);


You can also download it from here.

Once you have installed ebox-samba and ebox-usersandgroups again, run the above script as follows:

Code: [Select]
sudo ./ebox-reconfigure-module.pl users
sudo ./ebox-reconfigure-module.pl samba

Now you can go to module status and enable users and groups and samba

936
by the way, is your samba server running in eBox or on another machine within your LAN?

937
Installation and Upgrades / Re: Adding a new printer not in list
« on: April 13, 2008, 07:45:20 pm »
So which distro  version are you using exactly?

938
You can edit the file /usr/share/perl5/EBox/Iptables.pm

Add the line pf '-t nat -I POSTROUTING -s 10.10.2.0/24 -o eth1 -j MASQUERADE';
within sub start() function after the call to setStructure, it should look like this:

Code: [Select]
sub start
{
        my $self = shift;

        $self->_loadIptModules();

        $self->setStructure();

        pf '-t nat -I POSTROUTING -s 10.10.2.0/24 -o eth1 -j MASQUERADE';

        my @dns = @{$self->{net}->nameservers()};
        foreach (@dns) {
                $self->setDNS($_);
        }

Save the file and run the following command to check there isn't any syntax error:

Code: [Select]
perl -c /usr/share/perl5/EBox/Iptables.pm
If everything looks ok, restart the firewall by executing:

Code: [Select]
/etc/init.d/ebox firewall restart

Regarding the SMB thing, you are saying that you are actually seeing SMB broadcast packets and stuff on your VPN client interface, right?

939
Does the internal machine (the one you are pinging from the vpn) have set eBox as its gateway?

If not, you can try this to see if works:

sudo iptables -t nat -I POSTROUTING -s 10.10.2.0/24 -o eth1 -j MASQUERADE

940
Your VPN network subnet (netmask) is wrong, it shoud be 255.255.255.0

If you still have issues we'd need more info, tell us your network configuration, external and internal interfaces, gateways...


941
If you only got the "it works" page, that means you have accessed just the apache2 server installed on that machine, but not the eBox one.

If possible, tell me which package you have installed by running:

apt-cache policy ebox

You can try run:

/etc/init.d/ebox apache restart

By the way, when you installed eBox and you were asked to type a listening port for eBox's apache, what did you introduce? 443 which is default, or another one?

942
Installation and Upgrades / Re: OpenVPN + Samba + only 1 NIC
« on: April 10, 2008, 12:07:17 am »
You won't have any problem with the samba PDC stuff, but with the openVPN you will need at least two network interfaces.

I can tell you how to workaround but you will have to modify a couple of files

943
Installation and Upgrades / Re: OpenVPN Not Bridging Networks
« on: April 08, 2008, 11:34:52 am »
Hi,

Sorry I didn't read your reply before.

There's an option to solve your problem based on adding a couple of lines to a file, using iptables. Tell me if you are still interested.



944
Installation and Upgrades / Re: Server into an internal net
« on: April 08, 2008, 11:31:59 am »
Glad to hear that :)

945
Installation and Upgrades / Re: Server into an internal net
« on: April 07, 2008, 10:30:38 am »
The redirections work as follow:

You can redirect packets coming in from your external interface to machines in your local networks connected to your internal interfaces.

Can you post the configuration of your network interfaces, and tell us which is internal and which is external?

Thanks,

Javi

Pages: 1 ... 61 62 [63] 64 65 ... 67