If the private network is configured correctly, its relevant Cloud Servers can communicate via their respective private IPs. In the same way by connecting to any Cloud Server on your network, it is possible to access all the others via their respective IPs. This allows you to have a single point of access for all Cloud Servers in a private network: by configuring a single Cloud Server for the Internet connection (and then with a Public IP) you can reach any Cloud Server of the private network.
Furthermore once you are connected to a Cloud Server you can manage all the other Cloud Servers which are connected to the same private network via RDP access
for Windows Servers (or SSH
for Linux Servers). Another example: between Windows Cloud Servers it is possible to access all the disk resources of all the servers of the network, simply by going to Start > Run > and typing
based on the disk that you wish to access.
If the operation is not successful remember to check that you have enabled the sharing of disks.
A very simple and effective way system for checking the network is configured properly and/or checking that the connection between the Cloud Server is still active, is to ask simple
- On a Windows Cloud Server go to Start > Run and type "cmd" and press Enter. An msdos window will open in which you have to type
ping 192.168.0.110 and press enter, where the IP that follows the ping command is the IP of the server of the network with which you want to communicate. If the request goes well a report of the packets sent and received will be displayed, otherwise you will receive a "request expired" message
- On a Linux Cloud Server type
ping -c1 192.168.0.20 and press enter, where the IP that follows the ping command is the IP of the server of the network with which you want to communicate, and the -c1 option means that an attempt will be made. If the request goes well a report of the packets sent and received will be different from 0.