Windows target machine not discover - Host not reachable error

[Amit39]

Hi,

I am trying to discover one windows machine. I have selected the IP address of the particular machine and the MID server, however, I am getting the discovery completion error as "x.x.x.x is not a reachable host" and discovery completed.

May I know how to troubleshoot this error and can able to get a successful discovery result so that I can keep the CI information in CMDB.

Q1. Is there any firewall issue which block me to make it discovered.

Q2 . Is there any account related issue, however can see the account has full access to the system

Q3. is there any issue related to windows port (on/off)

Appreciate your quick help to fix the issue.

Thank you in advance.

Thank you.

Regards,
Amit

[VivekSattanatha · Accepted solution]

Hi Amit,

1) First, try to ping the server from MID Server.

2) if ping successful then check the port 135 is opened or not by using telnet.

Regards,

Vivek

Based on the impact hit like, helpful or correct

[Vini]

Hi Vivek,

I have same issue on Windows discovery.

We are able to Ping from MID server and also able to telnet 135 from MID server.

What else we need to check, is RDP Port#3389 need to be open?

Thanks in Advance,

Vinil.

[VivekSattanatha]

Hi Vinil,

Port 3389 does not required to be as opened.

Try run wmi commands from Mid server. If you are facing problem running those commands then it could be a problem with RPC. Also be sure your credentials are working from Mid server.

There are lot of good posts in community to fix RPC and Wmi related issues. You could try those and post us if you resolved.

Regards,

Vivek

[sukran]

Hello Vivek

How to check port 135 is opened ? we are facing some CI were not discovered more than 30 days ..