Topics

1

Other modules / Routing over VPN Failure

« on: September 07, 2017, 08:43:53 pm »

I will ask this a different way, since I have seen many posts about this, but nobody has answered it that I have found.

Setting up Network with Site-To-Site VPN Connections, routing works fine between Zentyal Servers...
(See Zen-All Routes OK(1).png and zen server success.jpg )

...but their respective LANs will not route.
(See Zen-Lan Routes Fail.png, and zen lan route failure.jpg)

2

Installation and Upgrades / Problems joining domain

« on: August 11, 2017, 09:29:27 pm »

I have a domain server setup: (
Domain: internal.domain.com
FQDN: rc.internal.domain.com
IP of server: 10.0.0.200

Sometime back I set up FQDN: dc2.internal.domain.com and it works fine

Setup a third machine:
Domain: internal.domain.com
FQDN: dc.internal.domain.com
IP of server 10.0.0.202

from Third Machine:
Ping rc.internal.domain.com returns
NSLookup of rc.internal.domain.com returns proper IP address.

If I set up the Third machine as standalone domain server everything works fine.
When I try to set it up as an additional domain controller, the error message comes up:

-----
Some modules reported error when saving changes.  More information on the logs in /var/log/zentyal

The following modules failed saving their changes, their state is unknown:samba
-----

The log file error on dc being added:
2017/08/11 12:36:47 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command kinit -e arcfour-hmac-md5 --password-file='/var/lib/zentyal/tmp/wUHR9P' 'admin@INTERNAL.DOMAIN.COM' failed.
Error output: kinit: krb5_get_init_creds: unable to reach any KDC in realm INTERNAL.DOMAIN.COM

-----

Nothing is logged on the main DC (deleted the logs prior to attempting to connect to be sure)

The PDC works just fine for logging in to from workstations.