I have a customer environment that was running Veeam 12 and we now upgraded to veeam 13. we have to backup the laptops and previous setting was fine but now the problem is that we cannot ping most of the laptops from the VBR13, but we can ping from the laptops the VBR13 server using ip and dns name. We have disabled the firewall on the workstations and the problems still persists, whereby we cannot ping and nslookup fails from the VBR13 server side.
Question
VBR12 to 13
+4Hi
What is the current network configuration? Could you provide any info on VLANs and how the laptops are connecting?
+4If they can ping the IP address of the laptop but not the dns name it might be a dns issue. They can then try to do a dnsflush and register dns on the vbr. If they still cannot ping the name the work around will be to reseve the ip addresses on DHCP and add the entries in the vbr host file for a work around. Also try to disable IPV6 if its enabled.
+4Let us know happy to help where I can
We had the same issue when using the v13 Linux appliance, when switching to a v13 Windows server deployment all our issues were resolved.
The VBR linux appliance requires FQDN but has tons of Kerberos issues which in turn causes DNS queries to fail.
You will also be receiving a lot of user name and password incorrect issues even when using the correct credentials also due to the FQDN not being resolved due to Kerberos issues.
So if you have an older environment with legacy NAS, file shares, Agent based backups, older repositories I’d stick to using a Widows based VBR v13 server.
Thank you. Please advise on the upgrade requirements criteria? Just incase there is something we should verify. Our VBR12 had no issues that we are currently experiencing and we are on windows.
Also advise on anything we should look at if is okay with you.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.