Surebackup VM cannot ping each other

[dgrant]

Three machines powered on using same network subnet they can each ping the production gateway IP address but cannot ping each other.
e.g
VMs have IP of 192.168.255.115, 192.168.255.116 and 192.168.255.117

Production gateway ip is 192.168.1.2

Each VM can ping 192.168.1.2 but cannot ping each other using the 192.168.255 subnet.
Veeam host server can connect to each of the 192.168.255 machines.

I would like the machines to talk to each other for restore testing purposes..

[david.domask]

Hi Darren, welcome to the forums.

Just a quick sanity check, if they're Windows based machines, can you confirm if the Network Profile was changed to Public during the SureBackup? Public Network Profiles can cause some disruption of expected Firewall behavior as noted in the KB article.

If it's not the case, then please open a Support Case and provide logs from the SureBackup job and allow Veeam Support to review the Virtual Lab configuration.

Please share the case number here once the case is created. Thanks!

[Andreas Neufert]

Did you enable routing in the virtual lab creation/config wizard if you have multiple networks in the lab?

Within the lab the VMs have their original IP and they can work with each other under this IP.
My guess is that the VMs in the production have 192.168.1.x so they will keep the same IPs in the lab and the server in the lab need to communicate with these IPs. From the outside the 192.168.255.x is used by the virtual lab appliance to translate it lab internal into 192.168.1.x .

If you have Windows Firewalls enabled, likely the network is detected from scratch which means like David shared the network firewall profile public got chosen and you can not ping by default unless you allow it for public networks in the the win firewall before backup, too.