Hi @dhammett 

I would open the windows firewall on the hyperv, connect the hyperv to veeam and close the firewall again after successfull configuration.

For veeam Agent, that always works for me. The necessary ports are open after the agent installation and enabled windows firewall. Could work for HyperV too.

You can find more about the required ports on this page for manual configuration:

https://helpcenter.veeam.com/docs/backup/hyperv/used_ports.html?ver=110

For the credentials, please make sure to use the following format:

DOMAIN\USERNAME

I think this about covers it. One of these steps should address the issue. 

If that works, then it was firewall.

But I remember a topic in this forum that there was a problem abount special characters used in password. Just a tip, never knows.

I opened the firewall on the hyper-v host side and then tried all the same steps as before. Still I receive the same error. 

Referring to Marcofabbri’s reply could my password with special characters really be the reason I am unable to connect this server? I tried avoiding using the previous two accounts linked because I cannot confirm they are secure enough or not.

That might be a possibility but the only way to check that would be to change the password on the account you are using or test the connection with one of the other accounts to know for sure.

Very well, so using older password is working? If yes, we hit the spot!

For strong password, is better use passphrase. Long passphrase with “common special” character kill guessing and bruteforce. 

Can you verify that you are using Domain\Username format in the credentials?

This may seem weird, but try something for me. The domain password you are using, type it into Notepad++ on the local host/server/hypervisor you are using, copy it, and then paste it into the credentials setup in Veeam on the backup server, and then save the credentials. Weirdly, sometimes copying and pasting is the best way to deal with passwords in VMs. Caps lock may be on, something weird may be happening behind the scenes. It is a best practice taught to me by an IT veteran. It sounds dumb, but give it a shot.

@marcofabbri I will try a different account then! 

@bp4JC My account credentials worked once before when I was testing a VM backup as a file storage device. I assume that first verification is enough to know my account will work. Although if Marco’s idea doesn’t work then I will certainly test your theory and re-setup the server.

I changed the account with no luck and I also realized that my enterprise/domain/network account was not an admin on the server.  I already have admin access via domain admin account but I added it to netplwiz to see if that would fix the problem. Still no luck….

I also enabled file sharing on the server to see if that would allow information to be exchanged between the two servers but that did not seem to improve the situation.

I will copy and paste my credentials in next week. Have a great Thanksgiving!

You can always open a support case with veeam. With the logs, you get your answer in 1-2 days for such cases.

Local admin rights has nothing to do with windows' folders access permission. Try check credentials.

I copied and pasted my credentials in and received the same error… Any last suggestions?

@marcofabbri 

and 

@Chris.Childerhose 

At this point opening a Support ticket if you can would be the best thing.

Turned off the firewall on the server, went ahead with the config and turned the firewall back on. All looks to be good now. We’ll see how it performs overnight. 

Thanks for this.  It did the trick.

Disable firewall is not always best solution, even for a moment, better setting up with correct ports.

This is what Veeam to Hyperv uses:

https://helpcenter.veeam.com/docs/backup/hyperv/used_ports.html?ver=110

>Edited: correct link. Thanks @Mildur ]

@marcofabbri

This link is about Agents, this thread is about hyperv as far as I see. I have posted the link for hyperv already one month ago in my first answer in this topic.

For the workaround:

Disabling the windows firewall for a short moment will make sure, that veeam can be installed. Veeam then will setup the correct ports in the windows firewall for you.

I find it an acceptable workaround to have a fast solution. After the installation, windows firewall will be activated again by the administrator.

Thanks @Mildur , updated with correct link.

If you don’t want to disable firewall, you need to open ports 135, 137-139, 445, 6160, 6162, 6163, 2500-3300, 49152-65535

New-NetFirewallRule -DisplayName "Veeam default ports (manually added)" -group "Veeam Networking" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 135, 137-139, 445, 6160, 6162, 6163, 2500-3300, 49152-65535

You can use the -RemoteAddress parameters to further restrict