Skip to main content
Question

VBR12 to 13

R

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.

      12 comments

      R
      • ROCHE
      • New Here
      • July 17, 2026

      Can you ping your gateway ip from the vbr 13 server.

        Jonty
        Forum|alt.badge.img+4
        • Jonty
        • VUG Leader
        • July 17, 2026

        Hi ​@Rendym
        What is the current network configuration? Could you provide any info on VLANs and how the laptops are connecting?

        Jonty
        Forum|alt.badge.img+4
        • Jonty
        • VUG Leader
        • July 17, 2026

        If 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.

        R
        • Rendym
        • Author
        • Comes here often
        • July 17, 2026

        Hi Jonty, 

        We are connecting using AD. 

          R
          • Rendym
          • Author
          • Comes here often
          • July 17, 2026

          Thank you very much for the advise. We will try that.

            R
            • Rendym
            • Author
            • Comes here often
            • July 17, 2026

            Hi Roche, Yes we can Ping.

              Jonty
              Forum|alt.badge.img+4
              • Jonty
              • VUG Leader
              • July 17, 2026

              Let us know happy to help where I can

              B

              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.
               

                R
                • Rendym
                • Author
                • Comes here often
                • July 20, 2026

                Hi Brendan, were you also doing laptop backup too?

                B

                Hi Brendan, were you also doing laptop backup too?

                Yes, Veeam Agent backups

                R
                • Rendym
                • Author
                • Comes here often
                • July 20, 2026

                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.

                 

                R
                • Rendym
                • Author
                • Comes here often
                • July 21, 2026

                Good day,

                 

                ​@Jonty ,I noticed something today, When we do we did dns flush and it worked fine. we disconnected the machine and it later changed the IP address. When we check again it was not connecting. it seems like there is a lag in connection. Please advise if there is something we need to do on VBR server or network side.

                Terms & ConditionsAccessibility statement