DorsanDesk Troubleshooter: check errors and choose a fix
The DorsanDesk unified troubleshooter (Dorsan-Unified version 3.6.3, signed) is a tool for checking, fixing errors and maintaining the app on Windows. With one click and no questions asked, it runs its checks, corrects the Windows clock (without changing the time zone), removes blocking firewall rules and leftovers from old installations, and puts the report in a compressed file on the desktop. For specific problems, choose only the fix related to that problem: from checking the logs and system clock to dealing with a duplicate ID and the app cache.
To get the main remote desktop app, go to the DorsanDesk download page.

Three steps to check a problem
Download the troubleshooter with the button on this page and run it on the Windows computer that has the problem. If the problem is on the host, the check must be run on that host.
Click the “Check and fix” button. The checks run in parallel without asking any questions and usually take less than a minute. At the end, read the status and result columns; the compressed report file (….zip, whose Persian name means “DorsanDesk report”) is saved to the desktop.
Only perform the action that matches the check result. Afterwards, try the problem again in DorsanDesk and use “Clear results and check again”.
If DorsanDesk won’t connect
Check that the app is open on both devices, that the ID and temporary password are correct, and that the internet connection works. Reproduce the error once, then run the tool’s check so the new event shows up in the report. A working general internet connection does not necessarily mean all DorsanDesk services are reachable.
- If the problem started after installing or updating, check the installation status. The tool has “Download and install new version” and “Installer location” options.
- “Clear old registry entry” is for a situation related to an old installation; do not run it as a general fix for every error.
- If the connection only has problems on one network, compare the result with another network and note the conditions of each test in the report.
- For advanced network setup, see the DNS guide, and to check ESET restrictions, see the antivirus guide.
Manual network checks on Windows, Mac and Linux
On Windows, use nslookup dorsandesk.ir to check name resolution. The same command is available in many Mac and Linux environments too. Get the current destinations and ports from the firewall section on the download page.
On Windows, the TCP test pattern is Test-NetConnection HOST -Port PORT, and on Mac and Linux it is nc -zv HOST PORT. Replace HOST and PORT with the published destination and port. A failed ping alone does not prove the service is down; ICMP replies may be restricted. A successful TCP test does not confirm UDP status either.
What should you send to support?
Prepare the exact error text, the time it happened, the DorsanDesk version, the Windows version, the network type and the check result, along with a short description of the problem. If the tool shows “Tool did not finish running”, keep the technical details of that message; do not treat an incomplete result as a success.
Review the report before sending it. Do not put the temporary connection password, your account password or the password backup file in a public report or an unrelated conversation. To contact the support team, use the website’s online chat.
“Your request could not be processed” and the system clock
This message alone does not identify the cause of the error. If the log contains server_time is outside the allowed skew window, a system clock difference is one possible cause to check.
“Check and fix” corrects the Windows clock automatically and does not change the time zone. If the time zone is also wrong, the tool has a “Fix clock and set Tehran” option. Only choose Tehran if Tehran is the intended time zone of your computer. For computers outside Iran or devices managed by an organization, follow that environment’s time zone and time policy.
- On Windows, open Settings → Time & Language → Date & Time.
- Check the date, time and time zone; for Tehran, the UTC offset is +03:30.
- Sync the clock, reopen DorsanDesk and try signing in.
- If the error persists, run a fresh check and prepare the new error text for support.
Fixing a duplicate or random ID
If several devices have the same ID after cloning Windows or transferring settings, consider the “Fix random ID” option on the affected device. A device’s ID staying the same is not a problem in itself.
- Back up the necessary connections and settings before taking action.
- Note that changing the ID may end the current remote session; be prepared to regain access to the host.
- Read the tool’s message and the scope of the operation, and only continue if it matches the problem.
- When finished, run DorsanDesk again and check the ID; if it has changed, give the new ID to the authorized person.
Clearing the DorsanDesk cache
The “Clear app cache” option in the new tool brings the cleanup operation together in one place. Before running it, read the tool’s own description of the files affected and keep the report you need for troubleshooting.
If the problem continues, instead of repeating the cleanup, reproduce the error and run a fresh check.
Backup and restore
Back up connections and passwords
Use the “Back up connections and passwords” option and note where the output file is saved. This file may contain sensitive information; keep it in a safe place.
Restore a backup
To restore your data, use “Restore backup”. Choose the correct file and read the data replacement message before continuing.
Frequently asked questions
Does the troubleshooter replace the main DorsanDesk app?
No. This tool is for checking errors and maintenance. For remote connections, you need the main DorsanDesk app.
Does this file run on Mac and Linux?
The file offered on this page is an EXE for Windows only and requires .NET Framework 4.8 (if it doesn’t open on Windows 7, install .NET 4.8). On Linux, the dorsandesk --diagnose command does the same job. For Mac, use the Mac version launch guide and the permissions guide. The manual network check method is described above.
Do I need to run all the repair buttons?
No. First run “Check and fix” and choose only the action related to the result. Changing the clock, the ID, the registry and restoring backups serve different purposes.
What is the difference between “Check and fix” and a fresh check?
“Check and fix” checks the system status and logs and fixes common problems automatically. A fresh check helps you see events after the previous check separately and determine whether the error has happened again after your action.
What should I do if the tool itself shows an error?
Don’t assume the operation succeeded. Prepare the technical details text, the step where the error occurred and the file version for support.