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.
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.
Statistics: Posted by Andreas Neufert — Aug 21, 2024 2:54 pm
