Thanks for the update! Based on the error message, it looks like the application is still trying to connect to Host 1 (192.168.0.120) even though you’ve disabled it. The error shows a connection attempt to ldap://192.168.0.120:389, which is being refused.
A few things you might want to check:
-
Domain Configuration: Make sure Host 2 (
192.168.0.127) is correctly set in the domain/server list and that Host 1 is either removed or deprioritized. -
Failover Logic: Some applications don’t automatically switch to the second host unless the first one is explicitly unreachable and the failover mechanism is properly configured.
-
IQService Settings: Double-check that the IQService host and port are pointing to Host 2 when testing the connection.
-
DNS Mapping: If you’re using domain names instead of IPs, ensure the DNS resolves correctly to Host 2.
Since you mentioned creating a new application and successfully testing Host 2, that confirms Host 2 is reachable. So the issue likely lies in how the original application is prioritizing or defaulting to Host 1.
You might want to check with the application team to confirm how host selection and failover are handled internally.