• EN
Solved

vCenter server warning

A
Userlevel 7
Badge +1

Hey guys,

Yesterday, I added a vCenter infrastructure to veeam but I got a warning saying the target machine actively refused it. Can anyone give a reason for that and suggest what needs to be done?

icon

Best answer by Iams3le 8 March 2022, 10:33

View original

11 comments

Mildur
Userlevel 7
Badge +12

Hi @Anandu 

Please make sure that no ports are blocked.

You can find the necessary ports on this Page.

Port 443 is required for Veeam to access the vcenter.
 

If that is no help, try to open a support case. It‘s really easy for veeam support to find the correct solution for a technical issue, after analyzing the debug logs.

Product Management Analyst @ Veeam Software
Iams3le
Userlevel 7
Badge +9

Hello @Anandu,

Like @Mildur mentioned above, there could be a number of reasons that could prompt this warning. Perhaps, ports 443 is not allowed (blocked), or also you do not have the necessary permission to do so etc. 

  • Either way, a quick look at the log will be able to guid you. Lastly, ensure the DNS name or IP address is pingable!
[Microsoft MVP | Veeam Legend 5* | VMware vExpert 4* | Cisco Champion 3* | Object First Ace]
victorwu
Userlevel 7
Badge +7

@Anandu Please make sure the compatibility of Veeam VBR and vCenter is supported. If yes, please check 443 port is allowed and the account access right for vCenter is no problem.

Victor Wu
Chris.Childerhose
Userlevel 7
Badge +20

As others have said port 443 and also DNS is very important for resolution.  One of those should address the issue.

Chris Childerhose - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
wolff.mateus
Userlevel 7
Badge +11

As others have said port 443 and also DNS is very important for resolution.  One of those should address the issue.

When in doubt, the problem is always DNS. :sweat_smile:

Good to remember Chris! 

IT Lover | Veeam Vanguard | VUG Leader | Blogger
Chris.Childerhose
Userlevel 7
Badge +20

As others have said port 443 and also DNS is very important for resolution.  One of those should address the issue.

When in doubt, the problem is always DNS. :sweat_smile:

Good to remember Chris! 

Yes I have had many issues in my homelab due to damn DNS.  :joy:

Chris Childerhose - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
JMeixner
Userlevel 7
Badge +17

Yes, DNS is often a problem… 😎😎😎

I have fallen for this several times….

Jochen (Joe) Meixner | Veeam Vanguard 2024 | Veeam Legend 2021 - 2023 | Veeam Certified Architect (VMCA) 2022 | Twitter: @JoMeix | BlueSky: @jmeixner.bsky.social
BertrandFR
Userlevel 7
Badge +8

Check permissions on your user?

Every actions is logged with Veeam, maybe check in %programdata%Veeam you should have a logs in reference to your actions with more verbosity.

Link State
Userlevel 7
Badge +7

@Anandu This error "he target machine actively refused it" as already said is a generic error .

  • Have you restarted vcenter (Windows)? XD:scream:
  • Wrong NAT?
  • It could also be asymmetric routing?
  • Vcenter local Firewall?
  • Firewall roles?

First you need to check the connectivity.

  • try to do a telnet with the ip of the VCenter on port 443, if it does not respond it is FW between networks, FW on the vcenter

 

  • try to do a tracert with ip of the Vcenter check how many hops it does and if it stops is a clue.

Then if there is connectivity check the user used if it has all the necessary permissions.
As mentioned by @BertrandFR  check the logs! the gospel :D
GL

 

Veeam: VMCA | VMCE | VMXP | Veeam Legend - Microsoft: MCITP | MCP | MCSA | 2008 R2 | 2012R2 | 2016 | MCSE Core Infrastructure | MCSE Cloud Platform - Azure: AZ900 | AZ104 - VMWare: VCP-DCV Vsphere 7.x - Cisco: CCNA (Expired)
Iams3le
Userlevel 7
Badge +9

@Anandu This error "he target machine actively refused it" as already said is a generic error .

  • Have you restarted vcenter (Windows)? XD:scream:
  • Wrong NAT?
  • It could also be asymmetric routing?
  • Vcenter local Firewall?
  • Firewall roles?

First you need to check the connectivity.

  • try to do a telnet with the ip of the VCenter on port 443, if it does not respond it is FW between networks, FW on the vcenter

 

  • try to do a tracert with ip of the Vcenter check how many hops it does and if it stops is a clue.

Then if there is connectivity check the user used if it has all the necessary permissions.
As mentioned by @BertrandFR  check the logs! the gospel :D
GL

 

Well Expanded!

[Microsoft MVP | Veeam Legend 5* | VMware vExpert 4* | Cisco Champion 3* | Object First Ace]
Iams3le
Userlevel 7
Badge +9

Hi @Anandu, could you please let us know if you have been able to resolve your issue and the steps you took to resolve it? If any of the answers in the comment section was vital to the resolution, kindly mark the comment so we all can learn from it :grin:

[Microsoft MVP | Veeam Legend 5* | VMware vExpert 4* | Cisco Champion 3* | Object First Ace]

Comment


Terms & Conditions