Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

TCP ports used on Insight discovery

Hi, 

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?

Thank you.

1 answer

0 votes
Gustavo Delazari Borges
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Aug 31, 2022

Hi Jason,

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.

Hi Gustavo,

I can confirm that the credential is working with administrative privileges. TCP port 135 and 5985 are opened on one of our testing machine Windows firewall. But it still saying "No working credential". 

Gustavo Delazari Borges
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 05, 2022

Hi Jason,

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 @Gustavo Delazari Borges

What kind of access do I need for the server to upload the collected data to the Jira Cloud? Does my server need internet access to upload?

 

Thanks

Jason

Gustavo Delazari Borges
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 20, 2022

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:

https://support.atlassian.com/jira-service-management-cloud/docs/export-data-from-insight-discovery-to-insight-cloud/

I hope it might help you.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events