You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have a problem when trying to scan a PC on the same subnet, it said, "No working credential for IP ADDRESS", tried to test with the program and it said, "Cannot connect with credentials".
But the credential is valid and works if I'm trying to scan the local machine.
According to the documentation , insight discovery is using the WMI for credential, any chance that the Windows firewall rule blocked it? What services and ports have to be opened to make it work?
In our organization we have been using Discovery to scan Windows machines, and the used port for that is 135. According to your error message, I think it's a good idea to check if the credentials you are using to connect have administrator privileges on your servers. I remember I had some issues related to it during our tests.
Let me know if you need further help.
In Discovery settings (if you are hosting it in a Windows server), where you store your credentials, you can test them trough the tab "Credentials" using the button "Test". Have you tried this in order to validate those credentials with your servers?
If you still can't establish a connection, try to inform the domain before the user (domain/user) on the "Credentials" tab.
Hi @Jason Chan
We have been using Jira Data Center with Insight, so I am not sure how Cloud works.
I have found this documentation:
I hope it might help you.