Skip to main content
Solved

Host is unreachable. Unable to install backup agent.


robns
  • Comes here often
  • 10 comments

Hi All,

 

I have this weird error happening on my Veeam server.

“Host is unreachable. Unable to install backup agent: cannot connect to 192.168.0.100 Error: The parameter is incorrect.”

The weird thing is, I’ve checked through all nodes of my Veeam installation and can’t find anything erroring or relating to this error (see pic).

In the ‘Name’ section below, those IP addresses do not relate to anything on the LAN, they aren’t even the same subnet. I have no idea where they are coming from.

 

 

Best answer by robns

OK, the Veeam notification email wasn’t coming from the current backup server but the old backup server that should have been powered down. 

The clue came from checking the internet headers of the Veeam email notification in a message analyser. The first hop submitting host entry showed the old server name.

Problem solved. Thanks for chipping in all.

View original
Did this topic help you find an answer to your question?

4 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8512 comments
  • February 12, 2025

Based on the error they are located under the manually added section of the console.  I would check there first and if nothing I would contact support for assistance as they will be able to check the logs and the database.


robns
  • Author
  • Comes here often
  • 10 comments
  • February 12, 2025

Hi,

 

Thanks for you for your response.

Yeah, except there’s nothing in the ‘Manually Added’ node.

I’ll see if I can decipher the local logs first.


robns
  • Author
  • Comes here often
  • 10 comments
  • Answer
  • February 12, 2025

OK, the Veeam notification email wasn’t coming from the current backup server but the old backup server that should have been powered down. 

The clue came from checking the internet headers of the Veeam email notification in a message analyser. The first hop submitting host entry showed the old server name.

Problem solved. Thanks for chipping in all.


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8512 comments
  • February 12, 2025

Great.  Glad to hear it was a simple fix.


Comment