Discussions specific to the Microsoft Hyper-V hypervisor
Post Reply
ChrisFIT
Influencer
Posts: 10
Liked: 2 times
Joined: Mar 13, 2019 3:34 pm
Full Name: Chris
Contact:

Problem adding Hyper-V server

Post by ChrisFIT » Mar 13, 2019 3:54 pm

Hello!

Today I downloded and installed the Veeam Backup & Replication Community 9.5 latest, but when adding a new Hyper-V Server I get warnings like this:

Collecting disks and volume info
Host discovery failed
Failed to discover updates for <Server DNS name> Error: IP-address is not IPv4
[<Server DNS name>] Disks and volumes discovery failed: Error: IP-address is not IPv4
Server has been added with warnings

(where <Server DNS name> is actually the fully resolved computer.domain.local name)

The status of the external ethernet in Network and Sharing Center shows IPv4 Connectivity: Internet, and IPv6 Connectivity: No network access.

What can I do?

Thank you!

Dima P.
Product Manager
Posts: 10697
Liked: 880 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Problem adding Hyper-V server

Post by Dima P. » Mar 13, 2019 5:55 pm

Hello Chris,

Please make sure that:

1. Host name can be properly resolved from this machine (i.e. you can bypass firewalls and antivirus software that might block the calls)
2. Check hosts file, you can even bind the ip address to host name for test purposes

Cheers!

RGijsen
Enthusiast
Posts: 92
Liked: 10 times
Joined: Oct 10, 2014 2:06 pm
Contact:

Re: Problem adding Hyper-V server

Post by RGijsen » Mar 15, 2019 9:59 am

We've had similar issues. Our Veeam host isn't domani joined, and therefore I manually added the DNS suffix to the Veeam host. That fixed it. Seems Veeam does lookups only by hostname, not the FQDN, I think I found several posts on that on the forum. Not sure how it would work in a multiple domain setup though.

ChrisFIT
Influencer
Posts: 10
Liked: 2 times
Joined: Mar 13, 2019 3:34 pm
Full Name: Chris
Contact:

Re: Problem adding Hyper-V server

Post by ChrisFIT » Mar 19, 2019 5:03 pm

Thank you both, I'll let you know how it goes!

ChrisFIT
Influencer
Posts: 10
Liked: 2 times
Joined: Mar 13, 2019 3:34 pm
Full Name: Chris
Contact:

Re: Problem adding Hyper-V server

Post by ChrisFIT » Mar 21, 2019 1:48 pm

Still not resolved, I've logged a case now, but any other ideas are welcome.

My Network Connections shows 4 items:

NIC1; Enabled; Broadcom card; IPv4 Connectivity - Not Connected; IPv6 Connectivity - Not Connected
NIC2; Disabled; Broadcom card
Ethernet; Disabled; Remote NDIS Compatible Device
vEthernet (External Network); Network 2; Hyper-V Ethernet Adapter; IPv4 Connectivity - Internet; IPv6 Connectivity - No network access; IPv4 Address 10.10.10.20; Link-local IPv6 Address fe80:: etc etc

Thanks again!

wishr
Veeam Software
Posts: 1298
Liked: 129 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: Problem adding Hyper-V server

Post by wishr » Mar 25, 2019 10:02 am

Hi Chris,

I would suggest disabling IPv6 completely in the NIC settings (for both) for testing purpose.

Thanks,
Fedor

ChrisFIT
Influencer
Posts: 10
Liked: 2 times
Joined: Mar 13, 2019 3:34 pm
Full Name: Chris
Contact:

Re: Problem adding Hyper-V server

Post by ChrisFIT » Mar 28, 2019 2:38 pm

Thanks everyone!

So the solution in this case is that when entering the DNS name during creation of the Managed Server, I have now used the format computer_name instead of computer_name.domain.local

Strange as the previous (=1st) time on a different server I used computer_name.domain.local (not computer_name on it's own).

Either it's not consistant, or I'm confused....


Does anyone know of an exact and fool-proof way to know what to enter as the DNS name when I am creating the Managed Server? (should I use some information from nbtstat? Or some other command? Or some other way?)

Thanks again,
Chris

wishr
Veeam Software
Posts: 1298
Liked: 129 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: Problem adding Hyper-V server

Post by wishr » Mar 28, 2019 4:53 pm

Hi Chris,

I believe there is some discrepancy on the DNS sever end. You can use "nslookup" and "ping" to troubleshoot it on both sides and check the records on the DNS server. "ipconfig /flushdns" might help as well. There are lots of guides on the internet explaining how all that stuff should be done in details.

From our perspective, a full DNS name or an IP address should be used.

Thanks,
Fedor

ChrisFIT
Influencer
Posts: 10
Liked: 2 times
Joined: Mar 13, 2019 3:34 pm
Full Name: Chris
Contact:

Re: Problem adding Hyper-V server

Post by ChrisFIT » Apr 04, 2019 11:23 am 1 person likes this post

Thanks again Fedor and everyone,

So I was advised by Veeam technical support that to find the correct DNS name: In cmd window type "net config workstation", and use the “Full Computer Name”.

Hope that helps someone!
All the best.

Post Reply

Who is online

Users browsing this forum: No registered users and 9 guests