I just noticed one more thing...  On the network Editor, I think you changed the subnet IP to the same as your host network.   That is not going to work.  NAT needs to translate across unlike subnets.  On the network configuration, don't make the subnet IP on the same as the host network.   Make it something like 10.179.254.0 (notice 3rd number in bold) with a mask of 255.255.255.0 or use the value that the Network Editor suggests the first time you open it.   Don't use 10.179.89.0.   

With NAT (Network Address Translation) the guest VM will be able to send data out and responses can come back.  You will have "full duplex" communication provided your guest VM initiates the communication.  If some other computer in your network happens to know the name or IP address of your guest VM, that computer will not likely be able to communicate with your guest VM in an unsolicited manner.  This is because the guest VM is "hiding" behind a different subnet and the VM's host is doing the NAT conversion.  You could probably install a route in your host OS to point to your guest VM but, I suspect the owner of 10.179.89.0 will either not like that or will ignore the route because they are not running a routing protocol at that level of the network.