Help! PRTG Sensors Can’t Connect After Changing Veeam Server to Workgroup

0
3
Asked By TechWhiz24 On

I recently took our Veeam Backup & Replication Server out of the domain and switched it to a Workgroup setup. While everything else is functioning as it should, my PRTG sensors for monitoring Veeam Backup Jobs are having trouble connecting. I keep getting an "Enterprise Manager Login failed: 401: Unauthorized" error, even when I use the local admin credentials for the Veeam server. Has anyone encountered this issue? Any suggestions or tips would be greatly appreciated!

2 Answers

Answered By FirewallWizard92 On

Make sure to check your local firewall rules! Since you switched your Veeam server to a Workgroup, it may have changed how the network sees it—firewall policies could differ. Try accessing your Veeam server from another machine with the same credentials to confirm they work. Also, check the Windows security event logs on the Veeam server; they might provide some insight.

TechWhiz24 -

I can RDP fine from my jump server, and I tested the admin share access with the local Veeam credentials, so I believe that part works. I checked the third-party firewall too, and it seems empty. I suspect that's not the issue. Appreciate the help!

NetworkNinja57 -

Glad to hear some things are working! But keep an eye on the security events just in case, and make sure the Windows network profile is set correctly.

Answered By NetworkNinja57 On

It sounds like PRTG might still be attempting to use domain credentials to connect, which would fail now that you're in a Workgroup. Try creating a dedicated local account on your Veeam server, and ensure that PRTG uses these new credentials to connect. That should resolve the issue!

SecurityGuru99 -

Just a heads up, though. Using hard-coded credentials can reduce your security. Instead, consider having agents on the Veeam server that allow reporting without needing credentials. It might be worth checking if PRTG has a similar setup option.

CuriousCat88 -

Thanks for the suggestion! I actually tried creating a new machine just for testing and entered only the local admin credentials for the Veeam server in the PRTG settings, but I'm still getting the same error.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.