Problem description
During a DRaaS Failback operation, the job failed because the TCP connection to the source on destination port 50000 could not be established. This issue is typically caused by firewall restrictions on EC2 instances.
Traceback
During a DRaaS Failback operation, the job failed because the TCP connection to the source on destination port 50000 could not be established. This issue occurs when the Microsoft Windows Firewall or network security settings block TCP traffic on port 50000, which is required for the failback process.
Sample JOBID Logs for Failback:
Note: The following logs are blacked out due to sensitive customer information.
| 2025-10-15 20:09:55 | [i-06956ff4bd158ed6f] Starting Phase-1 || 2025-10-15 20:09:56 | [i-06956ff4bd158ed6f] Successfully attached vmdk restore-WIN2022-SCAN25-.vmdk to vm restore-WIN2022-SCAN25-. || 2025-10-15 20:16:58 | [i-06956ff4bd158ed6f] TCP Connection to source on data port 50000 is failing. Please check firewall settings. || 2025-10-20 10:16:21 | Job cancelled ……
This error can be reproduced when attempting a failback without allowing TCP port 50000 through the firewall.
Steps to Configure Firewall Rule
Open Windows Defender Firewall with Advanced Security
Press Win + R, type wf.msc, and press Enter.
Create a New Inbound Rule
In the left pane, click Inbound Rules.
In the right pane, click New Rule….
Select Rule Type
Choose Port and click Next.
Specify Port
Select ANY.
Choose Specific local ports and enter:
50000Click Next.
Allow the Connection
Select Allow the connection and click Next.
Apply Rule to Profiles
Check Domain, Private, and Public (as needed).
Click Next.
Name the Rule
Enter a name such as:
Allow TCP Port 50000 for Restore Operations
Click Finish.