Article ID: 5422, created on Jul 3, 2008, last review on May 5, 2014

  • Applies to:
  • Virtuozzo containers for Windows 4.0

Symptoms

Start of the service container fails with the following error:

Creating port mapping for IP address 192.168.34.16 on port 80 failed.
Error=10013 Port mapping creation for VE 1 FAILED
Creating port mapping for IP address 127.0.0.1 on port 80 failed.
Error=10013 Port mapping creation for VE 1 FAILED
Unable to create port mappings for VE adapter 'venet0' (VE=1)
Setting up adapter failed, Err=0x00000057 (Container 1,netif0)
Failed to initialize network for container 1

Cause

The reason for the problem is that port mapping is not created for Parallels Infrastructure Manager because some application is occupying port 80. More often, there are IIS services running on the Hardware Node that prevent proper port mapping configuration.

Resolution

To fix the issue, it’s necessary to stop and disable IIS services or any other services or applications that are listening on the 80 and 4643 ports on the node. Then restart the service container.

If IIS services are used and cannot be disabled on the node, it’s necessary to change port mapping settings in the service container .conf file:

1.  Open the vz\conf\1.conf file.
2.  Change from the 443 and 80 ports to a free one.
3.  Save the 1.conf file.
4.  Start the service container.

Here is an example of the original record of port mapping in the 1.conf file:

PortMapping="TCP:22-22;TCP:4643-4643;TCP:4646-4646;TCP:8443-8443;TCP:443-4643;TCP:80-4642"

Port mapping is reconfigured here:

PortMapping="TCP:22-22;TCP:4643-4643;TCP:4646-4646;TCP:8443-8443;TCP:8843-4643;TCP:8888-4642"

Note that PIM and PPP will be accessible on ports 8843 or 8888 in this case (http:\\ip_of_the_node:8888).

28d0f7cc091e3b9304fa556c03f9a940 965b49118115a610e93635d21c5694a8 d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF