--- title: "Acronis Connection Blocked by Firewalls" canonical: "https://support.soteria-cloud.co.za/space/SCKB/50593816/Acronis%20Connection%20Blocked%20by%20Firewalls" format: markdown --- # Acronis Connection Blocked by Firewalls **Category:** Acronis Troubleshooting | Network & Connectivity Issues **Priority:** HIGH **Last Updated:** November 2025 --- ## Problem Acronis agents cannot communicate with cloud management services because corporate or system firewalls block required network connections. This prevents essential operations including agent registration, backup data transfer, management console access, policy updates, and monitoring data transmission. Acronis Cyber Protect requires bidirectional network communication across multiple ports and protocols to function properly. When firewalls restrict these connections, agents may appear offline, backups may fail during data transfer, registration may timeout, or management features may become unavailable. This issue is particularly common in enterprise environments with restrictive security policies or when deploying behind corporate firewalls, proxy servers, or network security appliances. --- ## Symptoms ### Agent Connectivity Issues **Common manifestations of firewall blocking:** - **Agent shows as “Offline”** in management console - **Device registration fails** during installation with timeout errors - **Backups start but fail** during data transfer phase - **Management console cannot connect** to cloud services - **Statistics and monitoring data** not updating - **Policy updates** not reaching agents - **Remote management features** unavailable ### Error Messages **Registration Errors:** `Connection timeout while connecting to cloud.acronis.com Unable to reach Acronis management services Registration failed: Network unreachable` **Backup Transfer Errors:** `Failed to upload backup data Connection interrupted during data transfer Timeout connecting to backup gateway` **Agent Communication Errors:** `Cannot establish secure connection to management server HTTPS connection failed on port 443 Gateway unreachable` ### Network Behavior - Initial connection attempts timeout (typically 30-60 seconds) - Intermittent connectivity if some ports open but not others - Successful installation but agent never comes online - Agent works on some networks but not others - Connectivity restored when firewall rules temporarily disabled --- ## Solution ### Step 1: Identify Required Network Connections Acronis Cyber Protect requires access to specific hostnames, IP addresses, and ports for full functionality. #### Primary Acronis Cloud Services **Core Management Services:** | Hostname | IP Addresses | Ports | Protocol | Purpose | | --- | --- | --- | --- | --- | | `cloud.acronis.com` | 45.11.129.61, 45.11.129.62 | 443 | HTTPS | Primary management API | | `eu2-cloud.acronis.com` | 45.11.129.31 - 45.11.129.34 | 443, 8443, 7770-7800 | HTTPS/Custom | EU data center services | **Branded Cloud Services:** | Hostname | IP Addresses | Ports | Protocol | Purpose | | --- | --- | --- | --- | --- | | `branded-eu2-cloud.acronis.com` | 45.11.129.69 - 45.11.129.70 | 80, 443, 7771, 7772 | HTTP/HTTPS | White-label services | | `agents-eu2-cloud.acronis.com` | 45.11.129.35 - 45.11.129.36 | 443 | HTTPS | Agent communication | **Frontend & Gateway Services:** | Hostname | IP Addresses | Ports | Protocol | Purpose | | --- | --- | --- | --- | --- | | `cloud-fes-eu2.acronis.com` | 62.138.220.82 - 62.138.220.99 | 443, 44445* | HTTPS | Frontend services | | `baas-fes-eu2.acronis.com` | 45.11.128.1 - 45.11.128.255 | 443, 44445* | HTTPS | Backup gateway | | `abgw-fra2-arp1-r01.acronis.com` | 62.138.220.82 - 62.138.220.99 | 443, 44445* | HTTPS | Regional gateway | | `abgw-fra2-arp1-r03.acronis.com` | 45.11.128.1 - 45.11.128.255 | 443, 44445* | HTTPS | Regional gateway | | `abgw-fra2-arp1-r04.acronis.com` | 45.11.128.1 - 45.11.128.255 | 443, 44445* | HTTPS | Regional gateway | | `abgw-fra2-arp1-r05.acronis.com` | 45.11.128.1 - 45.11.128.255 | 443, 44445* | HTTPS | Regional gateway | | `abgw-fra2-arp1-r06.acronis.com` | 45.11.128.1 - 45.11.128.255 | 443, 44445* | HTTPS | Regional gateway | **Resource & Backup Services:** | Hostname | IP Addresses | Ports | Protocol | Purpose | | --- | --- | --- | --- | --- | | `rs-eu2-cloud.acronis.com` | 45.11.129.31 - 45.11.129.34 | 8443 | HTTPS | Resource services | | `bc-eu2-baas.acronis.com` | 45.11.129.31 - 45.11.129.34 | 443, 8443 | HTTPS | Backup controller | | `cloud-wr-eu2.acronis.com` | 45.11.129.31 - 45.11.129.34 | 5060 | SIP | WebRTC communication | **Soteria Cloud Specific:** | Hostname | IP Addresses | Ports | Protocol | Purpose | | --- | --- | --- | --- | --- | | `arc01.soteriacloud.net` | 45.11.129.1 | 44445* | Custom | Statistics server | *** Port 44445 requires INBOUND connectivity for statistics servers only. All other ports are OUTBOUND.** #### Port Summary **Outbound Ports (Required on ALL agents):** - **443** - Primary HTTPS communication for management and API - **80** - HTTP fallback and redirect handling - **8443** - Alternative HTTPS for management console and services - **5060** - SIP protocol for WebRTC remote access features - **7770-7800** - Backup data transfer (31 ports) - **7771, 7772** - Branded cloud services (specific ports) **Inbound Port (Statistics servers only):** - **44445** - Statistics and monitoring data collection **Note:** Most client agents only need OUTBOUND connectivity. Only systems designated as statistics collection points need INBOUND port 44445 open. ### Step 2: Test Current Connectivity Before making firewall changes, test current connectivity to identify specific blockages. #### Basic Connectivity Test **Test DNS Resolution:** `nslookup cloud.acronis.com nslookup eu2-cloud.acronis.com` Expected: Should return IP addresses listed above. **Test ICMP (Ping):** `ping cloud.acronis.com ping 45.11.129.61` Note: Some Acronis servers may block ICMP. Ping failure doesn’t necessarily indicate firewall blocking. #### Port Connectivity Tests **Using Telnet (if installed):** `telnet cloud.acronis.com 443 telnet 45.11.129.61 443 telnet eu2-cloud.acronis.com 8443 telnet eu2-cloud.acronis.com 7770` **Expected Results:** - ✅ **Success:** Blank screen or connection accepted = Port is open - ❌ **Failure:** “Could not open connection” = Port is blocked **Using PowerShell (Recommended - More Reliable):** `# Test primary management portTest-NetConnection -ComputerName cloud.acronis.com-Port 443# Test backup data transferTest-NetConnection -ComputerName eu2-cloud.acronis.com-Port 7770Test-NetConnection -ComputerName eu2-cloud.acronis.com-Port 7800# Test management consoleTest-NetConnection -ComputerName eu2-cloud.acronis.com-Port 8443# Test WebRTCTest-NetConnection -ComputerName eu2-cloud.acronis.com-Port 5060` **Interpret Results:** `TcpTestSucceeded : True # ✅ Port is accessibleTcpTestSucceeded : False # ❌ Port is blocked` #### Comprehensive Test Script **Save as **`Test-AcronisConnectivity.ps1`**:** `# Acronis Connectivity Test Script$testResults= @()# Define test targets$tests= @( @{Host="cloud.acronis.com"; Port=443; Description="Primary Management"} @{Host="eu2-cloud.acronis.com"; Port=443; Description="EU Management"} @{Host="eu2-cloud.acronis.com"; Port=8443; Description="Management Console"} @{Host="eu2-cloud.acronis.com"; Port=7770; Description="Backup Transfer Start"} @{Host="eu2-cloud.acronis.com"; Port=7800; Description="Backup Transfer End"} @{Host="eu2-cloud.acronis.com"; Port=5060; Description="WebRTC"})Write-Host"Testing Acronis Connectivity..."-ForegroundColor CyanWrite-Host("="*70)foreach($testin$tests){$result= Test-NetConnection -ComputerName $test.Host-Port $test.Port-WarningAction SilentlyContinue$status=if($result.TcpTestSucceeded){"PASS"}else{"FAIL"}$color=if($result.TcpTestSucceeded){"Green"}else{"Red"}Write-Host("{0,-30} Port {1,-5} [{2}]"-f $test.Description,$test.Port,$status)-ForegroundColor $color$testResults+=[PSCustomObject]@{ Host =$test.Host Port =$test.Port Description =$test.Description Status =$status}}Write-Host("="*70)Write-Host""# Summary$passed=($testResults|Where-Object{$_.Status-eq "PASS"}).Count$failed=($testResults|Where-Object{$_.Status-eq "FAIL"}).CountWrite-Host"Results: $passed passed, $failed failed"-ForegroundColor Cyanif($failed-gt 0){Write-Host"`nBlocked Ports - Firewall configuration required:"-ForegroundColor Yellow$testResults|Where-Object{$_.Status-eq "FAIL"}|Format-Table-AutoSize}` Run with: `.\Test-AcronisConnectivity.ps1` ### Step 3: Configure Windows Firewall If Windows Firewall is blocking connections, create rules to allow Acronis traffic. #### Create Outbound Rules (All Agents) **Using GUI:** 1. Open **Windows Defender Firewall with Advanced Security** - Press **Win + R** → Type `wf.msc` → Press **Enter** 2. **Create Primary HTTPS Rule:** - Click **Outbound Rules** in left pane - Click **New Rule** in right pane - Select **Port** → Click **Next** - Select **TCP** → Specific remote ports: `443, 80, 8443` → Click **Next** - Select **Allow the connection** → Click **Next** - Check **Domain**, **Private**, **Public** → Click **Next** - Name: `Acronis - HTTPS Management` → Click **Finish** 3. **Create Backup Data Transfer Rule:** - Click **New Rule** again - Select **Port** → Click **Next** - Select **TCP** → Specific remote ports: `7770-7800, 7771, 7772` → Click **Next** - Select **Allow the connection** → Click **Next** - Check **Domain**, **Private**, **Public** → Click **Next** - Name: `Acronis - Backup Data Transfer` → Click **Finish** 4. **Create WebRTC Rule:** - Click **New Rule** - Select **Port** → Click **Next** - Select **TCP** → Specific remote ports: `5060` → Click **Next** - Select **Allow the connection** → Click **Next** - Check **Domain**, **Private**, **Public** → Click **Next** - Name: `Acronis - WebRTC Communication` → Click **Finish** **Using PowerShell (Faster for Multiple Systems):** `# Create Acronis outbound firewall rules# Rule 1: HTTPS ManagementNew-NetFirewallRule -DisplayName "Acronis - HTTPS Management" `-Direction Outbound `-Action Allow `-Protocol TCP `-RemotePort 443,80,8443 `-Profile Domain,Private,Public `-Description "Allow Acronis agent HTTPS communication"# Rule 2: Backup Data TransferNew-NetFirewallRule -DisplayName "Acronis - Backup Data Transfer" `-Direction Outbound `-Action Allow `-Protocol TCP `-RemotePort 7770-7800,7771,7772 `-Profile Domain,Private,Public `-Description "Allow Acronis backup data transfer"# Rule 3: WebRTCNew-NetFirewallRule -DisplayName "Acronis - WebRTC" `-Direction Outbound `-Action Allow `-Protocol TCP `-RemotePort 5060 `-Profile Domain,Private,Public `-Description "Allow Acronis WebRTC communication"Write-Host"Acronis firewall rules created successfully"-ForegroundColor Green` #### Create Inbound Rules (Statistics Servers Only) **Only required if system is designated as statistics collection point:** **Using GUI:** 1. Click **Inbound Rules** → **New Rule** 2. Select **Port** → Click **Next** 3. Select **TCP** → Specific local ports: `44445` → Click **Next** 4. Select **Allow the connection** → Click **Next** 5. Check appropriate profiles → Click **Next** 6. Name: `Acronis - Statistics Inbound` → Click **Finish** **Using PowerShell:** `New-NetFirewallRule -DisplayName "Acronis - Statistics Inbound" `-Direction Inbound `-Action Allow `-Protocol TCP `-LocalPort 44445 `-Profile Domain,Private,Public `-Description "Allow inbound statistics reporting to Acronis"` ### Step 4: Configure Network/Hardware Firewalls For enterprise deployments with dedicated firewall appliances (Cisco ASA, Palo Alto, Fortinet, pfSense, etc.). #### Create Address Objects Define Acronis IP ranges for easier management: **Acronis IP Networks:** `AcronisNet1: 45.11.128.0/24 (45.11.128.0 - 45.11.128.255) AcronisNet2: 45.11.129.0/24 (45.11.129.0 - 45.11.129.255) AcronisNet3: 62.138.220.0/24 (62.138.220.0 - 62.138.220.255)` **Example (Cisco ASA Syntax):** `object network ACRONIS-NET-1 subnet 45.11.128.0 255.255.255.0 description Acronis Cloud Services Range 1 object network ACRONIS-NET-2 subnet 45.11.129.0 255.255.255.0 description Acronis Cloud Services Range 2 object network ACRONIS-NET-3 subnet 62.138.220.0 255.255.255.0 description Acronis Frontend Services object-group network ACRONIS-NETWORKS network-object object ACRONIS-NET-1 network-object object ACRONIS-NET-2 network-object object ACRONIS-NET-3` **Example (pfSense/OPNsense):** 1. Navigate to **Firewall → Aliases** 2. Create new Alias: - Name: `Acronis_Networks` - Type: `Network(s)` - Networks: - `45.11.128.0/24` - `45.11.129.0/24` - `62.138.220.0/24` - Description: `Acronis Cloud Services` 3. Save #### Create Service Objects Define port groups for easier rule management: **Example (Generic Firewall Syntax):** `Service Group: Acronis-Management TCP/443 TCP/80 TCP/8443 Service Group: Acronis-Backup TCP/7770-7800 TCP/7771 TCP/7772 Service Group: Acronis-WebRTC TCP/5060 Service Group: Acronis-Statistics TCP/44445` #### Create Firewall Rules **Outbound Rule (Standard Agents):** **Example (Palo Alto):** `Name: Allow-Acronis-Outbound Source Zone: Internal Destination Zone: External Source Address: Internal-Networks Destination Address: ACRONIS-NETWORKS Application: ssl, web-browsing, custom-tcp-7770-7800 Service: Acronis-Management, Acronis-Backup, Acronis-WebRTC Action: Allow Log: Yes` **Example (Fortinet FortiGate):** `config firewall policy edit 0 set name "Acronis Outbound" set srcintf "internal" set dstintf "wan1" set srcaddr "all" set dstaddr "Acronis_Networks" set action accept set schedule "always" set service "HTTPS" "HTTP" "Acronis_Backup_Ports" "Acronis_WebRTC" set logtraffic all next end` **Inbound Rule (Statistics Servers Only):** `Name: Allow-Acronis-Statistics-Inbound Source Zone: External Destination Zone: Internal Source Address: ACRONIS-NETWORKS Destination Address: Statistics-Server Service: TCP/44445 Action: Allow Log: Yes` ### Step 5: Configure Proxy Servers If your environment uses a proxy server for internet access, configure Acronis agents to use it. #### Configure Proxy in Acronis Agent **Using Acronis Agent GUI:** 1. Open **Acronis Agent** (system tray icon or Start menu) 2. Click **Settings** (gear icon) 3. Navigate to **Network** or **Proxy settings** 4. Enable **Use proxy server** 5. Enter proxy details: - **Address:** `proxy.company.com` or `10.0.0.100` - **Port:** `8080` (or your proxy port) - **Protocol:** HTTP or HTTPS 6. If authentication required: - Check **Proxy requires authentication** - Enter **Username** and **Password** 7. Click **Test Connection** (if available) 8. Click **Save** or **Apply** #### Configure Proxy via Registry (Deployment) For mass deployment, configure via registry: `# Set proxy for Acronis Agent$proxyServer="proxy.company.com:8080"$proxyUsername="domain\acronis_service"$proxyPassword="SecurePassword123"# Registry path$regPath="HKLM:\SOFTWARE\Acronis\Global\HttpProxy"# Create registry keysNew-Item-Path $regPath-Force |Out-NullSet-ItemProperty-Path $regPath-Name "Server"-Value $proxyServerSet-ItemProperty-Path $regPath-Name "Username"-Value $proxyUsernameSet-ItemProperty-Path $regPath-Name "Password"-Value $proxyPasswordSet-ItemProperty-Path $regPath-Name "Enabled"-Value 1# Restart Acronis servicesRestart-Service-Name "mms"-ForceRestart-Service-Name "AcrSch2Svc"-ForceWrite-Host"Proxy configuration applied"-ForegroundColor Green` #### Proxy Bypass List Configure proxy bypass for direct connections when on internal network: **Typical Bypass Entries:** `localhost 127.0.0.1 *.local *.company.com 10.* 192.168.*` **In Proxy Server Configuration (if applicable):** - Add Acronis hostnames to bypass list if proxy causes issues - Consider direct routing for Acronis traffic ### Step 6: Verify and Test After firewall configuration, verify connectivity is restored. **1. Restart Acronis Services:** `net stop mms net stop AcrSch2Svc net stop afcdpsrv net start mms net start AcrSch2Svc net start afcdpsrv` **2. Re-run Connectivity Tests:** `.\Test-AcronisConnectivity.ps1` All tests should now show **PASS**. **3. Check Agent Status:** - Open Acronis management console - Navigate to **Devices** - Verify agent shows as **Online** - Check last communication timestamp **4. Test Backup Operation:** - Run a test backup (can be small file-level backup) - Monitor backup progress through all phases: - Initialization - Snapshot creation - Data transfer - Completion - Verify backup completes successfully **5. Review Logs:** Check agent logs for connectivity errors: `C:\ProgramData\Acronis\Agent\var\log\` Look for successful connection messages: `Connected to cloud.acronis.com:443 Backup data transfer initiated to eu2-cloud.acronis.com:7770 Statistics sent to arc01.soteriacloud.net:44445` --- ## Prevention ### Pre-Deployment Planning **1. Network Architecture Assessment** Before deploying Acronis: - Document network topology - Identify all firewalls (network and host-based) - Map proxy server locations and configurations - Identify NAT gateways and routing paths - Document security policies and change control procedures **2. Security Team Coordination** Engage security team early: - Present Acronis network requirements - Explain ports and protocols needed - Justify business need for each connection type - Address security concerns proactively - Obtain formal approval for firewall changes **3. Change Management** Follow organizational change procedures: - Submit firewall change requests with full justification - Include IP ranges, ports, protocols, and business purpose - Schedule changes during approved maintenance windows - Plan rollback procedures - Document changes in configuration management database ### Deployment Best Practices **1. Phased Rollout** Test connectivity in stages: - **Phase 1:** Test lab environment - Configure firewall rules - Install agent on test system - Verify full functionality - Document any issues - **Phase 2:** Pilot deployment (5-10% of production) - Deploy to representative systems - Monitor for connectivity issues - Validate across different network segments - Gather feedback from pilot users - **Phase 3:** Gradual production rollout - Deploy in waves by department/location - Monitor connectivity metrics - Address issues before next wave - Maintain deployment documentation **2. Network Segmentation Considerations** For segmented networks: - Test connectivity from each network segment - Verify routing between segments and internet gateway - Ensure firewall rules apply to all relevant segments - Document segment-specific configurations **3. Multi-Site Deployments** For organizations with multiple sites: - Test connectivity from each site - Consider site-specific firewall rules - Account for varying internet connections (speed, reliability) - Test VPN connectivity if applicable - Document site-specific requirements ### Documentation Requirements **Maintain Comprehensive Documentation:** **1. Network Diagram:** `[Acronis Agents] → [Windows Firewall] → [Internal Network] → [Network Firewall] → [Proxy Server (Optional)] → [Internet] → [Acronis Cloud Services]` **2. Firewall Rule Documentation:** Create reference sheet: `Rule Name: Acronis-HTTPS-Management Direction: Outbound Protocol: TCP Ports: 443, 80, 8443 Destination: 45.11.128.0/24, 45.11.129.0/24, 62.138.220.0/24 Purpose: Allow agent communication with management services Applies To: All systems with Acronis agent Created: 2025-01-15 Created By: Network Team Change Ticket: CHG000123` **3. Troubleshooting Runbook:** Document procedures for: - Testing connectivity - Identifying blocked ports - Escalation paths - Common issues and resolutions - Contact information for support teams ### Automated Monitoring **1. Connectivity Monitoring Script** Deploy scheduled monitoring: `# Acronis Connectivity Monitor# Schedule: Every 15 minutes via Task Scheduler$logFile="C:\Scripts\Logs\AcronisConnectivity_$(Get-Date -Format 'yyyyMMdd').log"$alertThreshold= 2 # Number of failures before alerting# Test critical connection$result= Test-NetConnection -ComputerName cloud.acronis.com-Port 443 -WarningAction SilentlyContinue$logEntry="$(Get-Date -Format 'yyyy-MM-dd HH:mm:ss') - "if($result.TcpTestSucceeded){$logEntry+="SUCCESS - cloud.acronis.com:443 reachable"}else{$logEntry+="FAILURE - cloud.acronis.com:443 unreachable"# Check failure count$recentFailures=(Get-Content$logFile-ErrorAction SilentlyContinue |Select-String"FAILURE"|Select-Object-Last 5).Countif($recentFailures-ge $alertThreshold){# Send alert$emailParams= @{ To ="it-alerts@company.com"From="monitoring@company.com" Subject ="Acronis Connectivity Alert - $env:COMPUTERNAME" Body ="Acronis cloud connectivity has failed $recentFailures times. Firewall may be blocking connection." SmtpServer ="smtp.company.com"}Send-MailMessage @emailParams}}Add-Content-Path $logFile-Value $logEntry` **2. Centralized Logging** Forward connectivity logs to SIEM or centralized logging: - Track connectivity trends - Identify patterns of failures - Alert on connectivity issues - Generate reports for management **3. Dashboard Creation** Build monitoring dashboard showing: - Agent online/offline status per site - Connectivity test results by location - Backup success/failure rates - Firewall rule hit counts - Proxy performance metrics ### Firewall Rule Maintenance **1. Regular Review** Quarterly review schedule: - Verify rules still required - Check for unused rules (low hit count) - Update IP ranges if Acronis changes infrastructure - Review security posture - Document changes **2. Change Tracking** Maintain change log: `Date: 2025-11-15 Change: Added port 5060 for WebRTC Reason: Enable remote management features Approved By: Security Manager Impact: None - outbound only` **3. Compliance Audits** For regulated industries: - Document justification for firewall rules - Maintain audit trail of changes - Review rules against security policies - Ensure rules meet compliance requirements ### Disaster Recovery Considerations **1. Firewall Configuration Backup** Regularly backup firewall configurations: - Export rules to version control - Document recovery procedures - Test restoration process - Maintain off-site copies **2. Emergency Procedures** Document emergency bypass: - Temporary rule to allow all Acronis traffic - Approval process for emergency changes - Rollback procedures - Communication plan **3. Alternative Connectivity** Plan for firewall failures: - Document manual workarounds - Consider backup internet connections - Test agent behavior during connectivity loss - Verify backup queuing and retry mechanisms --- ## Additional Resources - **Acronis Network Requirements:** [Official Documentation](https://www.acronis.com/support/documentation/) - **Acronis Port Checker Tool:** Available from Acronis support - **Microsoft Documentation:** [Windows Firewall with Advanced Security](https://learn.microsoft.com/en-us/windows/security/threat-protection/windows-firewall/) --- ## Common Scenarios and Solutions ### Scenario 1: Agent Shows Offline After Installation **Symptoms:** Agent installs successfully but never appears online in console **Diagnosis:** `Test-NetConnection -ComputerName cloud.acronis.com-Port 443` **Solution:** - If test fails: Open outbound port 443 to Acronis IPs - Verify DNS resolution - Check proxy settings if applicable - Restart Acronis services after firewall changes ### Scenario 2: Backup Starts But Fails During Transfer **Symptoms:** Backup initializes but fails when transferring data **Diagnosis:** `Test-NetConnection -ComputerName eu2-cloud.acronis.com-Port 7770` **Solution:** - If test fails: Open outbound ports 7770-7800 - Check for traffic shaping/QoS policies limiting bandwidth - Verify no intermediate firewall blocking data transfer ports ### Scenario 3: Management Console Inaccessible **Symptoms:** Cannot access Acronis management console from browser **Diagnosis:** `Test-NetConnection -ComputerName eu2-cloud.acronis.com-Port 8443` **Solution:** - Open outbound port 8443 - Check browser proxy settings - Verify SSL/TLS not blocked by security appliances - Clear browser cache and try again ### Scenario 4: Statistics Not Updating **Symptoms:** Agent online but statistics not appearing in console **Diagnosis:** `Test-NetConnection -ComputerName arc01.soteriacloud.net-Port 44445` **Solution:** - If statistics server: Open inbound port 44445 - Verify correct statistics server configuration - Check NAT/port forwarding if behind firewall - Review agent logs for statistics transmission errors ### Scenario 5: Works on Some Networks But Not Others **Symptoms:** Agent functions on home network but not corporate network **Diagnosis:** - Likely corporate firewall blocking - May also be proxy requirement **Solution:** - Configure Windows Firewall rules (as documented above) - Request corporate firewall exceptions - Configure proxy settings in agent - Test from corporate network after changes --- ## Related Issues - Agent appears offline in management console - Backup fails with “Connection timeout” - Cannot access management console from web browser - Registration fails during installation - Statistics server not receiving data - Device goes offline intermittently - Proxy authentication failures --- ## Keywords `firewall blocked`, `connection timeout`, `agent offline`, `port 443`, `port 8443`, `port 44445`, `network blocked`, `cannot connect`, `telnet test`, `outbound connection`, `Acronis ports`, `proxy configuration`, `Test-NetConnection`, `cloud.acronis.com`, `network firewall`, `connectivity issues`, `registration timeout` --- **Need Additional Help?** If connectivity issues persist after configuring firewalls: 1. **Collect Network Diagnostics:** `# Save to file for supportTest-NetConnection cloud.acronis.com-Port 443 > connectivity_test.txtipconfig /all >> connectivity_test.txtroute print >> connectivity_test.txt` 2. **Verify DNS Resolution:** `nslookup cloud.acronis.com > dns_test.txt` 3. **Check Proxy Logs:** Review proxy server logs for blocked Acronis connections 4. **Collect Acronis Logs:** `C:\ProgramData\Acronis\Agent\var\log\` 5. **Contact Network Team:** Provide list of required IPs and ports 6. **Engage Acronis Support:** Submit diagnostics with: - Connectivity test results - Network topology diagram - Firewall configuration export - Proxy configuration details - Agent logs showing connectivity errors