-
Type:
Bug
-
Resolution: Done
-
Priority:
Medium
-
Affects Version/s: Discovery 3.1.10
-
Component/s: Assets Discovery
-
1
-
Severity 2 - Major
Issue Summary
If DNS is specified in the Scan Settings, the Discovery scan would fail because it fails to resolve the DNS to IP address.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Step 1: In the Scan Settings, enter a DNS to scan (ex: pc1.mydomain.com)
- Step 2: Initiate the Discovery scan
Expected Results
The expected result in that DNS resolution on the domain name will occur and Discovery will ping the remote device using IP address.
Actual Results
The actual result is that the scan of the remote device will fail with the error "An invalid IP address was specified". See the full error below.
The below exception is thrown in the Discovery log file:
7/27/2023 10:26:32 AM: [Normal] --------------- Start Discovery (3.1.10.0 - 11D28) scan --------------- 7/27/2023 10:26:32 AM: [Normal] ScanSetting: 00001 with entire Range: jira111.home.local 7/27/2023 10:26:32 AM: [Normal] Generating list of IP's to scan from range: jira111.home.local 7/27/2023 10:26:32 AM: [Error] Error sending ICMP request to: jira111.home.local 7/27/2023 10:26:32 AM: [Normal] Exceptions: 7/27/2023 10:26:32 AM: [Normal] An invalid IP address was specified. at System.Net.IPAddress.InternalParse(String ipString, Boolean tryParse) at Insight.Discovery.Tools.Networking.NetworkService.SendPing(String host, Int32 timeout) in C:\build\DISCOVERY-DISCOVERYCLOUDRELEASE145-BUILD\DiscoTools\Networking\NetworkService.cs:line 1101 7/27/2023 10:26:32 AM: [Normal] Can't generating ip list from range: jira111.home.local 7/27/2023 10:26:32 AM: [Normal] Getting 0 IP's to scan. 7/27/2023 10:26:32 AM: [Normal] -------------- Discovery scan Statistic -------------- 7/27/2023 10:26:32 AM: [Normal] Full scan time 0 seconds with 4 threads. 7/27/2023 10:26:32 AM: [Normal] -----------------------------------------------
Workaround
The Discovery Tool v3.1.8 and prior is not affected by this defect.