A host that couldn't be scanned due to exception "An existing connection was forcibly closed by the remote host" is considered a full-scanned host

XMLWordPrintable

    • 1
    • Severity 2 - Major

      Issue Summary

      A host that couldn't be scanned due to exception "An existing connection was forcibly closed by the remote host" is considered a full-scanned host

      Affects Version/s

      Discovery tool 2.29.0

      Steps to Reproduce

      1. Perform Discovery scan for SNMP devices.
      2. When the scan is completed, check the logs to find the discovery scan statistic and also the detail of the scan. Example discovery scan statistic 
        23/02/2022 16:18:21 : -------------- Discovery scan Statistic --------------
23/02/2022 16:18:21 : Possible IPs: 1
23/02/2022 16:18:21 : Reachable Host/Devices: 1
23/02/2022 16:18:21 : Full-Scanned Hosts: 1
23/02/2022 16:18:21 : Full scan time 94 seconds with 32 threads.
23/02/2022 16:18:21 : -----------------------------------------------

      Expected Results

      If there's a host that is unreachable due to exception "An existing connection was forcibly closed by the remote host", this host should not be counted as a full-scanned host. Example exception

      23/02/2022 16:18:11 : V2 Response error for command: 1.3.6.1.2.1.1.1.0
23/02/2022 16:18:11 : Exceptions:
23/02/2022 16:18:11: An existing connection was forcibly closed by the remote host
   at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver, UserRegistry registry, Socket udpSocket)
   at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver, Socket udpSocket)
   at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver)
   at Lextm.SharpSnmpLib.Messaging.Messenger.Get(VersionCode version, IPEndPoint endpoint, OctetString community, IList`1 variables, Int32 timeout)
   at Insight.Discovery.ProviderClasses.SNMPProvider.ExecuteCommand(String command, ScanProcessType scanProcessType, Boolean silentTimeout, String contextName, Boolean useCache) in C:\SourceCode\discovery_repo\ProviderClasses\SNMPProvider.cs:line 115
23/02/2022 16:18:11 : Try to get V1 response result.
23/02/2022 16:18:11 : V1 Response error for command: 1.3.6.1.2.1.1.1.0
23/02/2022 16:18:11 : Exceptions:
23/02/2022 16:18:11 : An existing connection was forcibly closed by the remote host
   at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver, UserRegistry registry, Socket udpSocket)
   at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver, Socket udpSocket)
   at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver)
   at Lextm.SharpSnmpLib.Messaging.Messenger.Get(VersionCode version, IPEndPoint endpoint, OctetString community, IList`1 variables, Int32 timeout)
   at Insight.Discovery.ProviderClasses.SNMPProvider.ExecuteCommand(String command, ScanProcessType scanProcessType, Boolean silentTimeout, String contextName, Boolean useCache) in C:\SourceCode\discovery_repo\ProviderClasses\SNMPProvider.cs:line 134
23/02/2022 16:18:11 : Trying SNMP-Connection (SNMP_V1_V2) (0ad84a7c-ebdd-4a8b-aca6-ba73c506c8a2) to 10.10.10.10 - used 0,0168976 seconds - result: False

      Actual Results

      The host is considered as a full-scanned host, even though there wasn't any info about the host returned from the scan

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            vgedzhev (Inactive)
            Reporter:
            Michelle Chin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: