Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Assets Discovery fails during "WMI/PowerShell-Connection"

duotor0
July 23, 2026

Assets Discovery fails during "WMI/PowerShell-Connection" with the message "IP Address is not reachable".

However, from the same Discovery server and using the same credentials, classic WMI queries succeed:

  • Get-WmiObject Win32_OperatingSystem
  • Get-WmiObject Win32_BIOS
  • Get-WmiObject Win32_Service

DNS resolution works and the host name is resolved correctly by Discovery.

Discovery finds a matching credential but aborts immediately during the WMI/PowerShell connection phase.

We would like to understand what exact checks are performed during the "WMI/PowerShell-Connection" stage and what condition triggers the "IP Address is not reachable" message.

I have force scan on: ~

 

We have 1 possible credentials for the ip 192.xx.x.xx

Start WMI/PowerShell-Connection (...)

IP Address is not reachable.

Failed to connect during to: IP Address is not reachable.

Finish WMI/PowerShell-Connection (...) result: False

2 answers

0 votes
duotor0
July 28, 2026

I enabled "Use PowerShell" and then it worked..I don't know what is the problem with WMI then.

0 votes
Kai Krause
Community Champion
July 26, 2026

Hi,

Configure common settings | Atlassian Support | Atlassian Documentation 

Please have a look to trhe use Use PowerShell parameter in the config. 


Enable PowerShell if:

  • The Discovery-Tool is used in a Domain Environment(PowerShell work only in a Domain!)
  • A DNS Server is reachable(PowerShell needs a FullQualifiedDomain-Name for the remote machine, so for each IP address the Discovery-Tool perform a DNS-Reverse Lookup)

 I think to can cause trouble when you are not in a domain . But i didnt know your network a config. 

Such a guess , not an answer 

BR
Kai  

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events