Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Hi
It turns out that the DHCP was misconfigured since it sent the wrong DNS server, the gateway one not the main samba server.
After changing it, now everything is working fine.

Thanks.
22
Just to clarify a bit, I am send some images.

Domain settings in the srv01 - zentyal 4



Users and computers in the srv01 - zentyal 4



Domain settings in the srv02 - zentyal 8



Users and computers in the srv02 - zentyal 8

23
Hi there.
I have two samba servers, let's say srv01 and srv02. For that matter, both are Zentyal Server 4 and 8, respectively.
In the srv01 there is samba version 4.1, which is in the network 182.168.200.0/24, and which is by the way also the gateway to both network.
In the srv02 there is samba version 4.15, which is in the DMZ network 10.10.100.0/24
The first is an additional controller for the second.
Everything is working fine, except for machine sync.
Let me explain:
- Between these two samba servers, I have a Windows 2022 server. I was able to put Windows 2022 in the samba domain without any problems, which was a bit of surprise to me, since I always used to install SMB1v and SMB2v, first and then add the Windows server into the samba domain.
- I can log in into the Windows 2022 server using the domain account created in the server with samba 4.15
- In fact users created in both samba servers appear on both servers.
- With pdbedit --list I can see the following:
srv01:
pdbedit --list
...
...
SRV01$:4294967295:SRV01$
SRV02$:4294967295:
WINSRV01$:4294967295:
srv02:
pdbedit --list
...
...
SRV01$:3000020:SRV01$
SRV02$:3000022:

As you can see, the windows 2022 server was added in the srv01, which has samba 4.1.17 and does not appear in srv02, which has samba 4.15.13.
Based on that, I wonder if this is something to do with these different versions, before I seek some help with the Zentyal guys.
And I wonder if there is any way to force a sync between the two samba servers, in regard to the samba machines account.

Thanks in advance.

---
Gilbert
24
Yes it is in /etc/netplan/netplan.yaml but I think it is also in the mysql db as I tried to add another interface and assign one of the old virt interfaces to it and it says it was a duplicate. Resaving the interfaces does not help either. If you added a gateway manually it also gets stuck.

Code: [Select]
cat /etc/netplan/netplan.yaml
network:
  version: 2
  renderer: NetworkManager
  ethernets:
    eth0:
      dhcp4: false
      dhcp6: false
      addresses:
        - x.x.x.x/29
      nameservers:
        search:
            - "xxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
      routes:
        - to: 'default'
          via: x.x.x.x
          metric: 1
          on-link: true
        - to: 10.254.254.0/24
          via: 192.168.183.243
    eth1:
      dhcp4: false
      dhcp6: false
      addresses:
        - 192.168.183.254/24
      nameservers:
        search:
            - "xxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
    eth2:
      dhcp4: false
      dhcp6: false
      addresses:
        - 192.168.42.254/24
      nameservers:
        search:
            - "xxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
    eth3:
      dhcp4: false
      dhcp6: false
      addresses:
        - 192.168.153.254/24
      nameservers:
        search:
            - "xxxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
    eth4:
      dhcp4: false
      dhcp6: false
      addresses:
        - 192.168.155.254/24
      nameservers:
        search:
            - "xxxxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
    eth5:
      dhcp4: false
      dhcp6: false
      addresses:
        - 192.168.55.254/24
      nameservers:
        search:
            - "xxxxxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
    eth6:
      dhcp4: false
      dhcp6: false
      addresses:
        - 192.168.156.254/24
      nameservers:
        search:
            - "xxxxxxxxxxx.com"
        addresses: [ 1.1.1.1, 1.0.0.1 ]
    eth0.eth01:
      dhcp4: false
      dhcp6: false
      match:
        name: eth0.eth01
      set-name: eth0.eth01
      addresses:
        - 10.1.10.254/24
#            label: "eth0:eth01"
    eth0.eth02:
      dhcp4: false
      dhcp6: false
      match:
        name: eth0.eth02
      set-name: eth0.eth02
      addresses:
        - 10.1.10.1/24
#            label: "eth0:eth02"
    eth1.eth11:
      dhcp4: false
      dhcp6: false
      match:
        name: eth1.eth11
      set-name: eth1.eth11
      addresses:
        - 192.168.183.1/24
#            label: "eth1:eth11"

ls -al /etc/netplan/netplan.yaml
-rw-r----- 1 root root 2244 May 16 10:42 /etc/netplan/netplan.yaml

25
Hi,

What repositories do you have configured? Perhaps you have some Ubuntu repository for previous versions that is causing this issue. Additionally, you can run the following commands to see from what repository is trying to fetch the packages:


Code: [Select]

sudo apt update

sudo apt policy zentyal-samba samba zentyal-openvpn openvpn frr zentyal-ips suricata


Finally, what errors do you get when you try to install those packages?

Best regards, Daniel Joven.
26
Hi,

If the webadmin module is running and the server does not have any lock file or load issues, the 504 error might be related to the bug we have fixed and released today in the package zentyal-core 8.0.3, below you have the commit.

- https://github.com/zentyal/zentyal/commit/da6fcd411e3a3acea43d8581eb972f3ba901556d#diff-f2da1cfc0ddd16974080efa028f11a9c2c83db2d36b364d89fabc8f70e797da0

Basically, the webadmin module does a HTTP query to the certain public web page, and if the server that manages that page has load issues, the webadmin module might thrown an error. With this fix, that issue should be solved.

Best regards, Daniel Joven.
27
Hi,

We have added the following section in the upgrade documentation regarding this deprecated feature in Zentyal 8.0.

* https://doc.zentyal.org/en/upgrade.html#virtual-interfaces
* https://doc.zentyal.org/es/upgrade.html#intefaces-virtuales

Thank you again for reporting this behavior.
28
Directory and Authentication / Trust issue
« Last post by killmasta93 on May 15, 2024, 07:32:49 pm »
HI
Currently we updated the zentyal server from 6 to the version patch for windows 11 issue and was working fine few months,
After a while were getting few computers the trust issue relationship

I was reading https://forum.zentyal.org/index.php/topic,35602.0.html
not sure if its an issue of samba or an issue of windows
https://forum.zentyal.org/index.php?topic=35598.0

Thank you
29
From my little experience. A restart from the firewall might help. Maybe check if some rules are incorrect?
30
Hi David,

I found a solution, the ESM repository is not updated from focal to jammy therefore lots of packages will stuck on focal.
May I suggest something into the upgrade article "disable all of extended or external repository source list, example: ESM, third party repo, etc)" or something similar... :-)

BR,
GáborS
Pages: 1 2 [3] 4 5 ... 10