This website uses absolutely necessary cookies. If you consent to the use of convenience cookies, please click “Yes, I agree.” By clicking on “Privacy Settings.” you can change this setting at any time and withdraw your given consent.
see more
You can find detailled information in
our Privacy Policy
see less
Decide which cookies you want to allow.
You can change these settings at any time. However, this can result in some functions no longer being available. For information on deleting the cookies, please consult your browser’s help function.
Decide which cookies you want to allow.
read more
You can change these settings at any time. However, this can result in some functions no longer being available. For information on deleting the cookies, please consult your browser’s help function.
read less
Necessary
Comfort
Statistics
Targeting
Version(s): all
Description:
When using a fixed IP addresses in a multi-subnet Dicentis system, certain settings need to be made for the system to function well. If the settings are not made correctly, the system can stop functioning & disconnect from the server.
Solution:
The IP address of the server should lie outside the DHCP scope for the rest of the system, otherwise IP address conflicts may occur.
When using a multi-subnet, a DNS suffix needs to be added to the IP settings of the server in order for the devices in the system to find the server.
Steps:
In order to use a computer in a Dicentis system to which you want to assign a fixed IP you should make the settings similar to below. The settings should of course match the definitions made for your network.
Test:
A quick test to verify if the settings are correct, is to run the command as in the screen capture below. If you see a list of DICENTIS devices registered in the domain parent.bosch.omneo (and/or other domains in the multi-subnet system) then it is fine. The Bosch-arni is registered twice, once in the “local” domain and a second time in the “parent.bosch.omneo” domain, this is normal.
Steps:
If you only see the Bosch-arni registered in “local” domain, the DNS settings are wrong.