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.
Good day,
+4It seems like the DNS on the VBR is not updating correctly or got stale DNS records. so when you do a flush it clears it out and then pull the new records that is why its working. might be that the server is not pointing to the same DNS server as the domain joined laptops. When you have the issue you should ping laptop and ping laptop.domain.x.x to see if respond on one of these. and also do a nslookup laptopname to see what the VBR is expecting in return what IP and compare it with the IP on the laptop.
You will have to look into the DNS more then network and what the can do in the meantime to avoid this issue is to reserve the laptops they backup on DHCP they will get the same IP and will not have this issue.
I discovered that the customer is using different gateway. gateway for workstation is not the same as the 1 for VBR, does it have impact?
+4Hey
Having different gateways for workstations and the VBR server is quite normal in multi-VLAN environments and is not a problem on its own, as long as routing between the subnets is open. Since they do sit on separate subnets and gateways though, I wanted to share what is likely happening and what would be worth checking on your side.
DNS registration lag may be the main issue. When laptops disconnect or switch connections, for example moving from Wi-Fi to LAN, they pick up a new IP from the workstation gateway or DHCP server. If dynamic DNS updates on the Active Directory DNS server lag behind, VBR will still try to connect or ping the old IP, so nslookup and ping will fail until DNS catches up or gets flushed.
It may also be worth checking the DHCP lease and DNS settings. Maybe you just confirm if the DHCP scope for workstations is set to register or update DNS records immediately on lease assignment? It may also help to lower the DNS record TTL for dynamic clients so stale records do not linger as long.
It would be good to take a look at routing and the inter-VLAN firewall too, just to confirm that traffic from the VBR gateway to the workstation gateway is not blocking ICMP or the Veeam Agent management ports.
As a workaround in the meantime, setting up DHCP reservations for the laptops being backed up would give them static IPs and bypass the DDNS delay entirely. This will help with your trouble shooting
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.