Hi all. Running Windows Server 2019 as a standalone Hyper-V server. The server is in a workgroup.
I have installed the community edition of VBR 12, and configured my backup repository.
When trying to configure a new Hyper-V backup job, Veeam gives me a message to say that it cannot connect to the ADMIN$ share. However, if I type \\localhost\ADMIN$ into the run box, then the folder does open.
I’ve tried setting my host name to localhost, to the server name and to it’s IP address. I’ve also tried with the current logged in credentials, and have tried by enabling the administrator account.
Any help would be appreciated.
Thanks, and have a great weekend!
Answer
Failed to connect to ADMIN$ on local server
Best answer by coolsport00
This is a common question on here..I’ve also seen it where Win updates needed installed on both HV and VBR, then both servers rebooted, and connection then works.
When trying to use the admin account, maybe use .\ before it?
You also get this error with local admin accounts. The problem occurs due to remote UAC restrictions. Try the below to mitigate the issue
After you perform the above, go back to your Veeam server and test your credentials again, using the local account format I specified above (hostname\username). It should then be successful.
If the above doesn’t work, see if the Answer in the below Community post helps you:
+21For the credentials have you tried - hostname\username? Try this and see for the backup job.
+21Hi
Have you typed in hostname\username?
Have you disabled firewall to see if rules are messing with communication?
Disabled UAC?
Added the HV host into the hosts file on VBR?
+21This is a common question on here..I’ve also seen it where Win updates needed installed on both HV and VBR, then both servers rebooted, and connection then works.
When trying to use the admin account, maybe use .\ before it?
You also get this error with local admin accounts. The problem occurs due to remote UAC restrictions. Try the below to mitigate the issue
After you perform the above, go back to your Veeam server and test your credentials again, using the local account format I specified above (hostname\username). It should then be successful.
If the above doesn’t work, see if the Answer in the below Community post helps you:
Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
+5What
Matthias Beller - VMCA 2024/2022/2020 | VMCE 2024/2023/2021/2020 | Veeam Vanguard x3
I added the reg key. I didn’t actually have to reboot, but was then able to use .\username and connected successfully.
Thank you for your help!
+21Glad to hear the reg key add helped Chris.
Best.
Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
+21Great to hear you resolved the issue with the reg key. Comes in handy. 😂
Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.