05.08.2013 Views

[PDF] Parallels Server 5 Bare Metal

[PDF] Parallels Server 5 Bare Metal

[PDF] Parallels Server 5 Bare Metal

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Managing <strong>Parallels</strong> <strong>Server</strong> <strong>Bare</strong> <strong>Metal</strong> Network<br />

In this figure, the private network also includes two private subnets—Subnet 1 and Subnet 2, but<br />

the virtual machines and Containers included in these subnets reside on two physical servers.<br />

Container 101 and VM1 are joined to Subnet 1, and Container 102, Container 203, and VM2 are<br />

joined to Subnet 2. The virtual machine and Container on Subnet 1 can connect to each other but<br />

cannot access the virtual machines and Containers on Subnet 2, and vice versa.<br />

Weak Private Networks<br />

By default, when you create a private network, no virtual machine or Container on this network can<br />

access<br />

• virtual machines and Containers that are joined to other subnets in the private network<br />

• virtual machines and Containers that are not part of the private network<br />

• computers that are located on external networks<br />

However, you can configure a private network so that its virtual machines and Containers cannot<br />

communicate with virtual machines and Containers on other subnets in the private network, but<br />

can connect to virtual machines and Containers outside the private network and to computers on<br />

external networks. Such private networks are called weak private networks. "Weak" in this context<br />

means that these networks can be accessed by computers on external networks and are,<br />

therefore, more prone to security vulnerabilities and threats. The following picture demonstrates a<br />

system with a weak private network:<br />

190

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!