From 4f8cf745a6e3f3df3272576715e4e68d5dae9aab Mon Sep 17 00:00:00 2001
From: Dmitriy Alekseev <1865999+dragoangel@users.noreply.github.com>
Date: Thu, 16 Sep 2021 22:41:26 +0300
Subject: [PATCH] Update info about port checking under Windows

---
 docs/debug-common_problems.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/debug-common_problems.md b/docs/debug-common_problems.md
index dbc5ace30..92686019f 100644
--- a/docs/debug-common_problems.md
+++ b/docs/debug-common_problems.md
@@ -60,7 +60,7 @@ Docker and iptables-based firewalls sometimes create conflicting rules, so disab
 
 If you experience connection problems from home, please check your ISP router's firewall too, some of them block mail traffic on the *SMTP* (587) or *SMTPS* (465) ports. It could also be, that your ISP is blocking the ports for *SUBMISSION* (25).
 
-While Linux users can chose from a variety of tools[^1] to check if a port is open, the Windows user has only the command `telnet host port` available by default (and it has to be activated since Windows Vista).
+While Linux users can chose from a variety of tools[^1] to check if a port is open, the Windows user has only the PowerShell command `Test-NetConnection -ComputerName host -Port port` available by default.
 
 To enable telnet on a Windows after Vista please check this [guide](https://social.technet.microsoft.com/wiki/contents/articles/910.windows-7-enabling-telnet-client.aspx) or enter the following command in an terminal **with administrator privileges**: