So what you are saying is that you imported a VM into a network that is based on 192.168.10.0/24, but it has an IP of 192.168.63.177 and you didn't customize it.
Firebird89 wrote:
Scenario 3:
Cloned imported VM in a fenced isolated network deployment with NAT. The imported VM has an imported IP of 192.168.63.177. The external IP of imported VM in the DTST Routed Network - 192.168.10.3
Ping Source | Ping Destination | Status |
192.168.63.177 | 192.168.63.205 | FAIL |
192.168.63.205 | 192.168.10.3 | FAIL |
So the router will have a rule set based on 192.168.10.0/24 (10.1 - 10.255) ....
Did you re-customize this guest to say the Default Gateway is 192.168.10.1? Ideally, you would want to re-customize the guest to actually use an IP from the 192.168.10.0/24 network. so that it's part of the actual network schema, not some manual IP given by something else.
The ping works to 192.168.10.1 probably because it'll see the ICMP request and reply, as it's the only gateway on the inside of the NAT network.
From the outside in 10.3 -> 192.168.63.177 would fail since the return route won't use the correct gateway given the VM configuration.
If the 192.168.11.1 is a routed network on the same edge gateway device, then it might work since it's internal to the GW and a known address.
the last one I can't explain in scenario 3 without seeing an actual network topology, and complete IP config of the source NIC Card, nat rules (SNAT vs 1:1, etc)
