Skip to main content
Solved

vCenter server warning

A
Forum|alt.badge.img+1
  • Anandu
  • Comes here often
  • 77 comments

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?

Best answer by Iams3le

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!
View original
    Jean.peres.bkp
    matheusgiovanini
    leduardoserrano
    3 people like this
    • Jean.peres.bkp
      Jean.peres.bkp
    • matheusgiovanini
      matheusgiovanini
    • leduardoserrano
      leduardoserrano
    Did this topic help you find an answer to your question?

    11 comments

    Mildur
    Forum|alt.badge.img+12
    • Mildur
    • Influencer
    • 1035 comments
    • March 8, 2022

    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
    Chris.Childerhose
    BertrandFR
    wolff.mateus
    5 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • BertrandFR
      BertrandFR
    • wolff.mateus
      wolff.mateus
    • Iams3le
      Iams3le
    • marcofabbri
      marcofabbri
    Iams3le
    Forum|alt.badge.img+11
    • Iams3le
    • Veeam Legend
    • 1395 comments
    • Answer
    • March 8, 2022

    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 (2021 -2025) | VMware vExpert 5x | Cisco Champion 3x | Object First Ace 2x]
    Chris.Childerhose
    wolff.mateus
    2 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • wolff.mateus
      wolff.mateus
    victorwu
    Forum|alt.badge.img+7
    • victorwu
    • Veeam Vanguard
    • 375 comments
    • March 8, 2022

    @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
    Link State
    wolff.mateus
    3 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • Link State
      Link State
    • wolff.mateus
      wolff.mateus
    Chris.Childerhose
    Forum|alt.badge.img+21

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

    Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
    Link State
    wolff.mateus
    Iams3le
    3 people like this
    • Link State
      Link State
    • wolff.mateus
      wolff.mateus
    • Iams3le
      Iams3le
    wolff.mateus
    Forum|alt.badge.img+11
    • wolff.mateus
    • Veeam Vanguard
    • 542 comments
    • March 8, 2022
    Chris.Childerhose wrote:

    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
    wolff.mateus
    2 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • wolff.mateus
      wolff.mateus
    Chris.Childerhose
    Forum|alt.badge.img+21
    wolff.mateus wrote:
    Chris.Childerhose wrote:

    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 - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
    Link State
    wolff.mateus
    2 people like this
    • Link State
      Link State
    • wolff.mateus
      wolff.mateus
    JMeixner
    Forum|alt.badge.img+17
    • JMeixner
    • On the path to Greatness
    • 2650 comments
    • March 8, 2022

    Yes, DNS is often a problem… 😎😎😎

    I have fallen for this several times….

    Jochen (Joe) Meixner | Veeam Vanguard 2024 | Veeam Legend 2021 - 2024 | Veeam Certified Architect (VMCA) | Twitter: @JoMeix | BlueSky: @jmeixner.bsky.social
    Chris.Childerhose
    Link State
    2 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • Link State
      Link State
    BertrandFR
    Forum|alt.badge.img+8
    • BertrandFR
    • Influencer
    • 528 comments
    • March 10, 2022

    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.

    Chris.Childerhose
    Link State
    wolff.mateus
    4 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • Link State
      Link State
    • wolff.mateus
      wolff.mateus
    • Iams3le
      Iams3le
    Link State
    Forum|alt.badge.img+11
    • Link State
    • Veeam Legend
    • 614 comments
    • March 10, 2022

    @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| AZ500 - AWS Cloud Practitioner - VMWare: VCP-DCV Vsphere 7.x - Cisco: CCNA (Expired)
    Chris.Childerhose
    wolff.mateus
    Iams3le
    3 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • wolff.mateus
      wolff.mateus
    • Iams3le
      Iams3le
    Iams3le
    Forum|alt.badge.img+11
    • Iams3le
    • Veeam Legend
    • 1395 comments
    • March 10, 2022
    Link State wrote:

    @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 (2021 -2025) | VMware vExpert 5x | Cisco Champion 3x | Object First Ace 2x]
    Chris.Childerhose
    Link State
    wolff.mateus
    3 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • Link State
      Link State
    • wolff.mateus
      wolff.mateus
    Iams3le
    Forum|alt.badge.img+11
    • Iams3le
    • Veeam Legend
    • 1395 comments
    • March 10, 2022

    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 (2021 -2025) | VMware vExpert 5x | Cisco Champion 3x | Object First Ace 2x]
    Chris.Childerhose
    Link State
    wolff.mateus
    3 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • Link State
      Link State
    • wolff.mateus
      wolff.mateus

    Comment


    Terms & Conditions