VMware Cloud Community
RParker
Immortal
Immortal

vCenter error can't connect to IP

vCenter is reporting an error in tasks, can't connect to IP 172.1.1.10.  Error is can't login administrator@172.1.1.10.

I can login and the IP is responding, my question is what is trying to login?  How can I determine why vCenter wants to connect to this IP?  I don't remember installing anything (such update manager) at that IP or machine, I did look at it, but there is no VM Ware services (other than the client) that is installed.

So how do I find out what service integrated in vCenter is trying to connect to the IP?

Reply
0 Kudos
5 Replies
arturka
Expert
Expert

Hi

Try this

from cmd run  netstat -ano  - try to find target IP in Foregin address column - if you would find it - note a PID from the PID column

start task manager - add PID column to view and try to find noted previously PID, if you find it then you have service name which you were looking for

Message was edited by: arturka

VCDX77 My blog - http://vmwaremine.com
Reply
0 Kudos
RParker
Immortal
Immortal

Good idea, however since the service cannot login, a connection doesn't get established, and therefore no IP address is found for that IP in netstat.

I did try it, but was not able to find a reference for that IP.

Reply
0 Kudos
arturka
Expert
Expert

this what I was affraid off :smileyplain:

does entry in a log appears in regular basis ? If it does, maybe would be possible to run netstat -ano every second ( for a minute) and export output to file ? - but in that you would have to export list of processes with PID's as well (via PWCLI Get-Process ) It's little bit manual work Smiley Happy

Second option is to use sniffer, such as http://www.wireshark.org/ for sure you will find out port number - but I'm not sure if wireshark can identify process name

VCDX77 My blog - http://vmwaremine.com
RParker
Immortal
Immortal

Thanks!  That was really helpful.. still not able to find the IP, it's weird no reference to that IP anywhere in vCenter (this is the appliance).  no logs, no config files, nothing.. that's why I am stumped.

No reason for vCenter to contact this IP at all..

But truly thanks for the help, you gave me some good info

Reply
0 Kudos
RParker
Immortal
Immortal

Mystery solved.. it's actually reporting servers that are trying to connect (task/events).

So I logged into those servers, changed the credentials and everything works with no errors

Reply
0 Kudos