The problem with virtualization on esxi, network services are not visible, what's the problem?

Question

VPN

I'm using a free ESXI license for one core, with the following
Intel dg45id hardware, Intel® Core™2 Duo Processor E8500, 8GB ram.
3 Zabbix Appliance (Ubuntu server) virtual machines, Windows Server 2008 R2, CentOS 7 running at the same time
I noticed the following problem, third-party services do not start that require a dedicated port.
The btsync that I tried to run on the Zabbix server wrote that it was listening on its port 8888 before there was no access from the local network. While netstat -tulpn | grep btsync showed 127.0.0.1:8888 LISTEN.
Today I tried to install an OpenVPN server on CentOS, did everything according to the guides from one hosting, did internal checks and also made sure that there was no problem in the virtual machine, opened ports on the router.
Could there be a problem with ESXI? Or the nuances of setting up specific services in a virtual environment?

Answer 1

Setevok how many - more than one? IP on management configured? It doesn't matter that it's free, anyway, the management port rises in order to steer the host with a thick client from Windows or a browser. If there is only one network, check that the virtual card is connected to the real one (vSwitch for a single card is created automatically). If there is more than one network, you need to create a vSwitch for the second one, configure its IP and bind a virtual card.
It is useless to bind to 127.0.0.1, this is usually done in order to get to the server only from it - from the console, from the web server, etc. You need to bind to the IP that is allocated to the network card, or not to bind a specific IP at all - usually in this case all addresses are listened to.