Resolution 1:
- Open Run in Windows and use "secpol.msc" is the tool you need to run to change it. Or Open via Control Panel/Administrative Tools/Local Security Policy
- In the new window please expand Local Policies | select Security Options.
- The Windows security policy “Network security: LAN Manager authentication level” is not set by default. Change to “Send LM & NTLM – use NTLMv2 session security if negotiated” to fix the problem.
Resolution 2:
For Hyper-V hosts, go to the Repository's Storage GUI directly and Monitor logs or events that appear when a backup task is run.
- If you see vRanger's successful Log On but Hyper-V's Log On is refused.
- Proceed to vRanger's GUI | Inventory | Right-click a host and Reinstall Agent.
Afterwards, run a backup from a VM residing on that Host and check if it is successful.
Other Troubleshooting considerations:
- Check for special characters on the passwords as this could be causing issues.
- You can create a local account on your Repository Storage with Admin rights and a simple password (no special characters) and update the settings on vRanger.
- Try to access \\<RepoIP>\folder from vRanger and Hyper-V host with your domain and new local credentials to test the users' access.
- Besides browsing and creating+deleting a file or folder, you may want to try 'net use' to make sure the Log On is successful.
- net use x: \\server\fileshare /user:domain\username *
- Check if vRanger server or Hyper-V hosts recently installed Windows Update KB3002657 or KB3068457.
- Check Control Panel | All Control Panel Items | Credential Manager | Stored Cred/Windows Vault if it has some stale info related to the share. Delete entry if necessary.
- Check Firewall and Antivirus. Disable if needed.
- Check in the Event Viewer if vRanger and the vCenter are able to communicate with the Domain Controller.
- Check if those servers have the same Time.
