NethServer Version: 7.6
Module: Samba AD 4.8.12
Ihave a client with a network 192.168.175.x/24 and a secondary network 172.16.x.x/16.
The default Gateway is 192.168.175.1. To reach the 172.16.x.x network a route needs to be added manually.
Using Static Routes this works for the NethServer.
One Client Notebook needs to work time to time in the 172.16.x.x network, and still have access to files on the Nethserver.
The NethServer can be reached, and awnsers to pings. The NethServer-AD, with the IP 192.168.175.11, is not reachable. I think the AD ignores any additional routes, that the Nethserver honours…
How can I check this?
Ping from the Nethserver to a host in 172.16.x.x works. Both ways. But not with the NethServer AD…
Not sure if this is a Bug or a Support case…
Thanks for any ideas…