US/CAN: 1-800-467-8464 INTL: 1-214-467-8464
September 7, 2011

Virtual Networking, and Instance.com Part I

Instance.com offers the advanced networking features that you require. From simple to use direct-IP networking to more advanced virtual networking with load balancing and firewall features you use to can create a network infrastructure suited to your needs, not to those of the provider. You can also create a combination of both types of network offerings as well as traditional dedicated services to create a hybrid environment leveraging the benefits of each technology.

In this article, and later entries, I will show you how you can configure the Instance.com networking capabilities to best meet the needs of your application or environment.

Virtual Networking:

This is the preferred network configuration within the Instance.com product. Choosing this network configuration gives you scalability, security, and lower costs. Through the use of the virtual router and private RFC 1918 IP space you can create high performing secure environments from 1 to any number of servers.

Virtual Networking (1 IP Address)

 

 

 

 

 

 

 

 

By using a single public IP address you can direct traffic to the required server(s) by mapping the proper external port to the internal port hosting the services. If you have two servers hosting a service on the same port, you can create a port-forward mapping two distinct external ports, to the port hosting the service on the servers behind the virtual router.

Consider the following example. You have two Windows application servers that you wish to manage via Remote Desktop. As you may know Windows runs the Remote Desktop Service on port 3389. If you have two servers, and only 1 public IP, how do you connect to them? Simple, you map two unique public ports (33891 and 33892 in this case) to the corresponding internal ports of each server.  Choose the IP you wish to create the mappings on, and then create the port forwards. Your base IP will always be labeled [source nat]

Creating a Port Forward Within the Portal

Now how do you connect to these servers using the non-standard ports? Tell your client to use the new port, Microsoft’s Terminal Service Client in this example, by entering the following.

Remote Desktop Non-Standard Port

 

 

 

 

 

You can configure most clients to use non-standard ports, generally by appending a colon and then the new port at the end of the address. This allows you to use less IP’s which is both cheaper and in a lot of a cases easier to manage. That, and you’ll being doing the Internet as a whole justice by doing your part in conserving rapidly depleting IPv4 space.

 

Sometimes you just can’t change the port a service runs on which is typical of public web servers where you can’t provide a unique URL such as http://my.developement.site:8080 or for mail servers, Name Servers, and any other service where the public client expects a standard port. Given this requirement the Instance.com product allows you to acquire additional IP addresses as needed to meet these requirements.

 

Next up is Virtual Networking  with 2 or more Public IP’s, Direct Public IP Networking, Virtual and Direct networking Hybrid, and Hybrid Hosting by connecting to Dedicated Servers.

Until then!

Posted By: cshaffer

Categories: All, Techonology

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>