I have routinely used NAT VMs to work as IIS servers with other VMs. So, there is no limitation in VM not to allow port 80 traffic (with version 15.x or earlier, not done it since that).

In your case, I would check the following:

- perhaps far-fetched based on your description, but the HOST DNS functionality gets confused with VM copies, which they often are. Thus, the VM node name might not work, initially at least. You can overcome this by editing on the Windows-side /etc/hosts file to include the tcp/ip-name resolution. A Windows reboot is required in order to get that to work (ping works without a reboot, don't get fooled). You don't need to do it on the VM, which a VM always "knows" its Host

- I don't know CentOS, but isn't it the idea that server ports are NOT open in Linux before you open them? Have you done that in CentOS ... you said you have Apache there, but still? I cannot deduct from your listing, but do you need to double-check this in CentOS?

- you asked also what to do on Windows? Not sure if this was the intent. However, in Windows you need to configure Firewalling and probably reboot after that. Not sure why this is necessary, if you can access Internet on your NAT VM computer ... by default it works without any reconfiguration of the Firewall. Or perhaps you need to reconfigure something else which you might have installed on Windows, like a Virus scanner which may have kind-of stealth firewalling and can start to work incorrectly, seen that happening.