-
Bug
-
Resolution: Unresolved
-
Low
-
Discovery 7.1.2
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
The error information is incorrect when testing WMI credentials against a Windows host. Error messages are crucial for diagnosing and resolving issues, both for users and developers. They should be clear, accurate, and informative. If an error message provides misleading or incorrect information, it can lead to confusion, misdiagnoses, and potentially make troubleshooting more difficult.
Steps to Reproduce
Requires 2 Windows host:
- Discovery Tool Host
- Target Windows Host
Steps:
- Block incoming connection on port 135 on the target Windows Host
- Install Discovery Tool 7.1.2 on Discovery Tool Host
- In the Credentials Tab, create a new credential and provide the target Windows Host Administrative Credentials
- Click the "Credential Test", provide the target Windows Host IP
- Ok
Expected Results
Provide correct information on the port that is blocked.
For example: The connection port 135 is not reachable on host x
Actual Results
A Windows pop-up "The connection port 5985 is not reachable."
This is also written to the discovery/logs/
Workaround
In PowerShell use the Test-NetConnection cmdlet instead to test if ports are open
Test-NetConnection -ComputerName <IP or Hostname> -Port <Port#>
- mentioned in
-
Page Failed to load
[JSDSERVER-16197] Assets Discovery - Incorrect error information "The connection port 5985 is not reachable."
| Assignee | New: Puneet Saini [ a99cf1f76b82 ] |
| Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
| Status | Original: Gathering Impact [ 12072 ] | New: In Progress [ 3 ] |
| Fix Version/s | New: Discovery 7.1.3 [ 113199 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 1015923 ] |
| Support reference count | New: 1 |
| Description |
Original:
h3. Issue Summary
The error information is incorrect when testing WMI credentials against a Windows host. Error messages are crucial for diagnosing and resolving issues, both for users and developers. They should be clear, accurate, and informative. If an error message provides misleading or incorrect information, it can lead to confusion, misdiagnoses, and potentially make troubleshooting more difficult. h3. Steps to Reproduce Requires 2 Windows host: * Discovery Tool Host * Target Windows Host Steps: # Block incoming connection on port 135 on the target Windows Host # Install Discovery Tool 7.1.2 on Discovery Tool Host # In the Credentials Tab, create a new credential and provide the target Windows Host Administrative Credentials # Click the "Credential Test", provide the target Windows Host IP # Ok h3. Expected Results Provide correct information on the port that is blocked. For example: The connection port 135 is not reachable on host x h3. Actual Results A Windows pop-up "The connection port 5985 is not reachable." This is also written to the discovery/logs/ h3. Workaround In PowerShell use the Test-NetConnection cmdlet {code} Test-NetConnection -ComputerName <IP or Hostname> -Port <Port#>{code} |
New:
h3. Issue Summary
The error information is incorrect when testing WMI credentials against a Windows host. Error messages are crucial for diagnosing and resolving issues, both for users and developers. They should be clear, accurate, and informative. If an error message provides misleading or incorrect information, it can lead to confusion, misdiagnoses, and potentially make troubleshooting more difficult. h3. Steps to Reproduce Requires 2 Windows host: * Discovery Tool Host * Target Windows Host Steps: # Block incoming connection on port 135 on the target Windows Host # Install Discovery Tool 7.1.2 on Discovery Tool Host # In the Credentials Tab, create a new credential and provide the target Windows Host Administrative Credentials # Click the "Credential Test", provide the target Windows Host IP # Ok h3. Expected Results Provide correct information on the port that is blocked. For example: The connection port 135 is not reachable on host x h3. Actual Results A Windows pop-up "The connection port 5985 is not reachable." This is also written to the discovery/logs/ h3. Workaround In PowerShell use the Test-NetConnection cmdlet instead to test if ports are open {code:java} Test-NetConnection -ComputerName <IP or Hostname> -Port <Port#>{code} |