ServiceNow Discovery Credential is working for midserver but not for other server

hanwar2
Kilo Sage

@Runjay Patel @Dr Atul G- LNG 

 

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

 

1 ACCEPTED SOLUTION

hanwar2
Kilo Sage

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. 

View solution in original post

11 REPLIES 11

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?


hanwar2
Kilo Sage

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.