none
WMI Error//Failed - Socket not connected//AD DS Discovery Method RRS feed

  • Question

  • Hi

    I am getting the error Failed - Socket not connected,  on the WMI status when trying to scan laptop workstations. These machines have been shown to be connected to the domain but MAP is still returning the error. I have confirmed that all required firewalls and ports are open. I am trying to scan them using the AD DS discovery method.

    A suggested explanation was that because the machines are connecting through DirectAccess (IpV6) that this was causing the problem. Can this be true?

    I cant find any threads where this error is suggested. Any help at all is most appreciated.

    regards,

    Kigen


    IT Services | Insight Nordics

    Monday, February 3, 2014 10:16 AM

Answers

  • I have discovered that disabling IP Helper service (iphlpsvc) worked for the few with Failed - Socket not connected errors.


    • Marked as answer by Insight Nordic Tuesday, February 11, 2014 1:37 PM
    Monday, February 3, 2014 9:50 PM