Check Internal Port and Hostname Configuration If the service is running but still refusing connections, there may be a mismatch in how the components identify each other post-migration.
• instanceconfig.xml: Verify that the Presentation Services configuration points to the correct hostname and port for the Scheduler.
• NQSConfig.ini: Ensure the [SCHEDULER] section contains the correct RPC_SERVICE_OR_PORT and that it matches the port being called in the error log.
• Firewall Rules: Ensure that the internal communication ports (default is often 9705 for the Scheduler) are not blocked by the OS firewall (e.g., iptables or firewalld) on the server.
3. Inspect Server-Side Logs Since you have OS-level access, you should examine the following logs for specific failure reasons (such as database connectivity issues or credential errors):This will provide more context on the "remote end point" the Presentation Services is attempting to reach when the connection is refused.

Check Internal Port and Hostname Configuration If the service is running but still refusing connections, there may be a mismatch in how the components identify each other post-migration.
• instanceconfig.xml: Verify that the Presentation Services configuration points to the correct hostname and port for the Scheduler.
• NQSConfig.ini: Ensure the [SCHEDULER] section contains the correct RPC_SERVICE_OR_PORT and that it matches the port being called in the error log.
• Firewall Rules: Ensure that the internal communication ports (default is often 9705 for the Scheduler) are not blocked by the OS firewall (e.g., iptables or firewalld) on the server.