Skip to main content
Solved

Network path not found, or invalid credentials supplied


I have setup a new server on our network. Connected to domain, network, hyper-v installed and I am unable to add this server to the Virtual Infrastructure > Microsoft Hyper-V > Standalone Hosts > (server).  I have my Veeam server trying to contact our new server and there seems to be a road block. I am running Veeam V11a trying to setup a new 2019 windows server. During the hyper-v setup process I have added the name and/or IP address, I have selected the last option (standalone) which matches the description of the new server.  My credentials do work because I ran a test to setup a VM running server 2019 and I was able to set that up right away. For some reason the physical server is blocking the Veeam connection.  Is there a firewall exception I need to add?  I did attempt to manually add the physical server to Veeam so the agent might create its own firewall exceptions. I was unsuccessful at that as well.

Best answer by Mildur

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

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

19 comments

Mildur
Forum|alt.badge.img+12
  • Influencer
  • 1033 comments
  • Answer
  • November 23, 2021

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


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8119 comments
  • November 23, 2021
Mildur wrote:

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. :thumbsup_tone2:


marcofabbri
Forum|alt.badge.img+13
  • On the path to Greatness
  • 990 comments
  • November 24, 2021

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.


  • Author
  • New Here
  • 5 comments
  • November 24, 2021

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.


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8119 comments
  • November 24, 2021
dhammett wrote:

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.


marcofabbri
Forum|alt.badge.img+13
  • On the path to Greatness
  • 990 comments
  • November 24, 2021
dhammett wrote:

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.

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. 


bp4JC
Forum|alt.badge.img+3
  • Influencer
  • 136 comments
  • November 24, 2021
dhammett wrote:

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.

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.


  • Author
  • New Here
  • 5 comments
  • November 24, 2021

@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.


  • Author
  • New Here
  • 5 comments
  • November 24, 2021

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!


Mildur
Forum|alt.badge.img+12
  • Influencer
  • 1033 comments
  • November 24, 2021
dhammett wrote:

 


​​​​​​
​​​​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.


marcofabbri
Forum|alt.badge.img+13
  • On the path to Greatness
  • 990 comments
  • November 25, 2021
dhammett wrote:

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!

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


  • Author
  • New Here
  • 5 comments
  • November 30, 2021

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

 

@marcofabbri 

and 

@Chris.Childerhose 


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8119 comments
  • November 30, 2021
dhammett wrote:

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.


  • Author
  • New Here
  • 5 comments
  • December 1, 2021

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. 


  • New Here
  • 1 comment
  • January 13, 2022
dhammett wrote:

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.


marcofabbri
Forum|alt.badge.img+13
  • On the path to Greatness
  • 990 comments
  • January 13, 2022

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 ]


Mildur
Forum|alt.badge.img+12
  • Influencer
  • 1033 comments
  • January 13, 2022
marcofabbri wrote:

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

This is what Veeam uses:

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

@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.

 


marcofabbri
Forum|alt.badge.img+13
  • On the path to Greatness
  • 990 comments
  • January 13, 2022

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


Comment