How Can We Help?
-
Getting Started
-
Command Center
-
User Account
-
Tutorial Videos
-
Remote Access
-
Remote Monitoring
-
Troubleshooting
- Corrupt .NET Tmp folder
- Windows Viewer won't launch .NET error
- Windows XP and 2003 Server
- Web client problem loading
- Black Screen / Headless Display
- WOL - Troubleshooting Wake on Lan
- Metrics unknown or wrong values
- 2008 Server ctr-alt-del Workaround
- General Troubleshooting Ideas
- Connection Problems
- Installation Problems
- Metrics not showing up
- Disconnecting connection
-
Firewall
-
Remote Rescue
Ports
Created On
bySteve White
RemoteToPC traverses most firewalls, but some firewall software actively stops activity for applications automatically because it has been configured to. Also, for network administrators that block all outbound firewall traffic, you’ll need to open outbound TCP ports for the host and join side computers: 5222, 5223, and 3478, as well as outbound UDP ports 3478, and 49152-65535. (Note: Monitoring uses outbound TCP port 5672 and 5671)
Try our connection test tool to see if anything on the system or network is blocking RemoteToPC: Connection Test
