Skip to main content
Commonmark migration
Source Link

While doing some troubleshooting I came around [this post][1]this post which states:

If you configured your vmware VM to run in a virtualized NAT network, then you will not be able to access/ping your VM from the Host,

This is the statement that I consider as false due to the fact that I can actually do so, meaning ping from my host (win7 laptop) to the guest (vm running kali) in Vmware workstation 14 pro.

However that is just a statement before providing two workarounds, so although it does not invalidate entirely the answer, it can be somewhat misleading for future readers.

The catch that bothers me is that from my pov this might be a false sentence, however depending on customers specs and environment this might be completely true.

How does one proceed in this type of scenario? [1]: https://stackoverflow.com/questions/36787490/vmware-unable-to-ping-using-nat-ip-address-but-can-ping-physical-ip

While doing some troubleshooting I came around [this post][1] which states:

If you configured your vmware VM to run in a virtualized NAT network, then you will not be able to access/ping your VM from the Host,

This is the statement that I consider as false due to the fact that I can actually do so, meaning ping from my host (win7 laptop) to the guest (vm running kali) in Vmware workstation 14 pro.

However that is just a statement before providing two workarounds, so although it does not invalidate entirely the answer, it can be somewhat misleading for future readers.

The catch that bothers me is that from my pov this might be a false sentence, however depending on customers specs and environment this might be completely true.

How does one proceed in this type of scenario? [1]: https://stackoverflow.com/questions/36787490/vmware-unable-to-ping-using-nat-ip-address-but-can-ping-physical-ip

While doing some troubleshooting I came around this post which states:

If you configured your vmware VM to run in a virtualized NAT network, then you will not be able to access/ping your VM from the Host,

This is the statement that I consider as false due to the fact that I can actually do so, meaning ping from my host (win7 laptop) to the guest (vm running kali) in Vmware workstation 14 pro.

However that is just a statement before providing two workarounds, so although it does not invalidate entirely the answer, it can be somewhat misleading for future readers.

The catch that bothers me is that from my pov this might be a false sentence, however depending on customers specs and environment this might be completely true.

How does one proceed in this type of scenario?

Source Link
DRP
  • 168
  • 7

What happens if an answer has a statement that is false but does not invalidate the answer entirely?

While doing some troubleshooting I came around [this post][1] which states:

If you configured your vmware VM to run in a virtualized NAT network, then you will not be able to access/ping your VM from the Host,

This is the statement that I consider as false due to the fact that I can actually do so, meaning ping from my host (win7 laptop) to the guest (vm running kali) in Vmware workstation 14 pro.

However that is just a statement before providing two workarounds, so although it does not invalidate entirely the answer, it can be somewhat misleading for future readers.

The catch that bothers me is that from my pov this might be a false sentence, however depending on customers specs and environment this might be completely true.

How does one proceed in this type of scenario? [1]: https://stackoverflow.com/questions/36787490/vmware-unable-to-ping-using-nat-ip-address-but-can-ping-physical-ip