| | How to use PowerShell cmdlet 'Test-NetConnection' to test access to Port on Server? |
| Resolution | [BCB:3:Network warning:ECB]
[BCB:4:Operating system warning:ECB]
[BCB:5:Third-party support:ECB]
NOTE: Test-NetConnection cmdlet requires Windows 8 or higher - Open Windows PowerShell (Start, Windows PowerShell, Windows PowerShell or Press WinKey+R, Enter: powershell, click OK)
- Type: Test-NetConnection -Computername -Port -InformationLevel "Detailed"
NOTE: Do not include <> when entering Server (or IP Address) and Port (Example: Test-NetConnection -Computername Server101 -Port 10000 -InformationLevel "Detailed" ) - Press Enter
- Review the 'TcpTestSucceeded' field
- True = The workstation successfully communicated with the Server on the port specified
- False = Either the service that runs on the specifed port is not running or Firewall is blocking access to it
- If TcpTestSuccessed returns FALSE result, log into the Server and verify the service is running and\or create an Inbound Firewall Rule for the application or Port
Sample Output of failed connection to port '10000' on Server:
 DocLink: What firewall port exceptions to set for Sage 300 CRE?
DocLink: Error: "Connection failure to host: [TCP]::NODELAY;STREAM"
DocLink: Antivirus exclusions: Which files should I exclude from antivirus and firewall for Sage 100 Contractor SQL
[BCB:155:Chat 100 US:ECB] |
|