- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2025 08:21 AM
I need some urgent help. I am facing issue with Discovery Credential which is working for MidServer through MidServerServiceAccount but not working for another server.
I have created two windows servers in AWS in same VPC, subnet, Security Group and used one server for MidServer.
I am able to run discovery for midserver but other server it is not working. Even the MidServerService Account is also not passing the credential test.
MidServer IP is 2.0.0.7 and the other server IP is 2.0.0.195, when I run discovery it is getting all scan completed for 2.0.0.7 but not for 2.0.0.195
Please help
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2025 06:26 AM
Hi All,
Thanks for your suggestions.
I was able to sort it out by making the changes in Firewall of the VMs which I was trying to discover.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2025 08:38 AM
Hi @hanwar2 ,
Are you able to ping from the first IP to second IP?
Is there any Defender or any other application on Second IP which you can disable and try?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2025 06:26 AM
Hi All,
Thanks for your suggestions.
I was able to sort it out by making the changes in Firewall of the VMs which I was trying to discover.