Start with these checks
- Check that the remote PC is on and both devices have internet access, then try connecting again.
- Check that the firewalls on both devices allow AirDesk UDP traffic; if possible, try another network.
- If it keeps failing, send support ERR-2003, the time and connection logs from both devices. Do not send passwords or authentication tokens.
Advanced diagnostics · for administrators and support
The direct connection process, including UDP punching, did not finish in time. The timeout alone does not identify the failed stage or which device blocked the connection.
The host is the remote PC; the client is the PC you connect from. If you cannot locate logs, start by sending the error code and detailed reason from the error window.
The error code alone does not show whether a device failed or a firewall blocked the connection. Check the detailed reason and logs as well.