• No results found

Biznet GIO Cloud Connecting VM via Windows Remote Desktop

N/A
N/A
Protected

Academic year: 2021

Share "Biznet GIO Cloud Connecting VM via Windows Remote Desktop"

Copied!
7
0
0

Loading.... (view fulltext now)

Full text

(1)

Biznet GIO Cloud

Connecting VM via Windows

Remote Desktop

(2)

Biznet GIO Cloud — Connecting to your VM via Windows Remote Desktop

Introduction

Connecting to your newly created Windows Virtual Machine (VM) via the Windows Remote Desktop client is easy but you will need to make some configuration changes in Portal first. This document will guide you through the necessary processes to configure the VM.

Once launched your VM will not be accessible via a Remote Desktop Client. This is because Biznet GIO Cloud Compute deploys a firewall between your VM and the Internet with deny rules as default.

Prerequisites

 Your VM has been deployed on an “isolated” network (this is the standard network which is auto provisioned).

 Your isolated network has an external IP Address (an IP Address is automatically assigned to your default isolated network). Any additional isolated networks will not have a IP Address and one will need to be acquired separately.

 You VM is running a Windows Operating System.

Enabling RDP

From the Home screen select [Manage Resources], [Cloud]

Select the [Instance] tab

From the left hand navigation select the VM you want to enable / check that it is enabled for RDP. In this example we have selected a machine we had previously called “test”.

(3)

Biznet GIO Cloud — Connecting to your VM via Windows Remote Desktop

© Biznet GIO all right reserved 3 of 7

On the initial Configuration Tasks screen, ensure “Remote Desktop” is enabled. Alternatively, if it is enabled and you require different settings continue to the next step.

To enable or change the default setting, click on [Enable Remote Desktop], and enable/adjust the settings from this screen.

Ensure one of the “Allow connections” is enabled, depending on your security requirements.

Select [OK]

Log out of the VM and close the terminal window, and return to the Cloud Compute Portal.

(4)

Biznet GIO Cloud — Connecting to your VM via Windows Remote Desktop

Identifying your IP Address

Now that we have established the VM will accept a RDP session we need to set up the firewall rules to allow Internet access to the VM itself. This configuration changes are managed through the Portal.

Select the virtual machine from the list to which you want to gain access from the Internet. In this example we have selected a machine we had previously called “test”.

For your selected virtual machines, the screen will show the machines attributes. Select the [NICs]

tab to show the details of the network your VM is attached to.

You will notice the type of network is identified.

Make a note of the [Network ID].

This is the internal ID for the network that your VM is

attached to. Each network has a unique ID.

From the [Manage Resources] tabs select the [IP Address] tab

Displayed on the left hand navigation will be all the IP Addresses associated with your Account (Master User and Power User will see all).

Remember every User will have an IP Address and every location you have deployed a VM will also have an IP Address so there may be many displayed.

Scroll through the list of IP Addresses until you find the one with the [Associated Network ID] that matches the [Network ID] you identified and noted earlier.

(5)

© Biznet GIO all right reserved 5 of 7

Biznet GIO Cloud — Connecting to your VM via Windows Remote Desktop

Setting up the firewall rules

Now that you have identified the IP Address associated with the network your VM resides on select the [Firewall] tab.

This tab allows you to create the firewalls rules associated with your network.

These are the Ingress rules for your network. Egress rules can be found on the Network tab (rather than IP address tab) but are not required to set up an RDP session.

For the purposes of this guide we are going to demonstrate how to create a standard rule for TCP/IP traffic using port 3389 (the port used by Windows Remote Desktop) - this will allow traffic through to Remote Desktop on our virtual machine.

[Source CIDR] Enter the source network of the devices you would like to have access to your VM. In this example we want it available to everyone on the Internet so we enter 0.0.0.0/0 to increase security you can be more specific and lock it down to your own office / home network

[Protocol] Using the drop down box select the required protocol. In this case we want the default TCP

[Start Port] Enter “3389”. This is the first port in the range you wish the firewall to allow [End Port] Enter “3389”. This is the last port in the range you wish the firewall to allow

If ICMP is selected as a Protocol enter “-1” in both the [Type] and the [Code]

boxes that will appear. This will allow the Security & Network Appliance to respond to ICMP requests.

(6)

Biznet GIO Cloud — Connecting to your VM via Windows Remote Desktop

Once the firewall ruleset has been entered click on the “+” button to add the rule, once the rule has been added, you see it displayed as follows:

To remove a rule simply select the button against the appropriate rule.

Select the [Port Forwarding] tab. This will allow you to define which port on the VM we want to use.

[Public Port] enter the IP port incoming traffic will be arriving on. This should be within the range you specified in Step 11

[Private Port] enter the IP port that will be used by the virtual machine for this traffic. This could be a different port from that specified in the [Public Port] box, if so the port will be natted

[Protocol] specify the protocol used by the target server for this traffic type. This should match the settings in Step 11

[Virtual Machine] select the target virtual machine from the drop down list

Once the port forwarding rule has been entered click on the “+” button to add the rule, once the rule has been added you this will be listed as follows.

To remove a rule simply select the button against the appropriate rule.

Locate the IP Address of your VM (demonstrated earlier), this will be the IP Address you use to access your VM.

(7)

Biznet GIO Cloud — Connecting to your VM via Windows Remote Desktop

© Biznet GIO all right reserved 7 of 7

Remote Desktop Connection

From your computer (Microsoft Operating system in this example), run the Remote Desktop Connection client.

Search for “Remote Desktop Connection” or execute “%windir%\system32\mstsc.exe“ from the Start, Run, command prompt.

Enter the IP Address of your VM, and the user name (default user name is Administrator)

When you connect enter the password which was generated when you created the VM.

You are now accessing your VM over the Internet using Windows Remote Desktop.

References

Related documents

In addition to the two virtual sessions that are available in Windows 2000 Terminal Services Remote Administration mode, an administrator can also remotely connect to the real

In the Remote Desktop Connection dialog box, type the computer name of computer name of your office computer, which you wrote down earlier4. Click the

• When using the URL method to install the firewall protection service to a computer running a Windows desktop operating system via a remote desktop connection, the remote

The Helpdesk support of VPN/Remote Desktop is strictly limited to confirming that the VPN systems are up and running.. The Helpdesk does not offer installation assistance on

to connect to, followed by a colon, then the RDP port number. For hosts using the default Windows RDP configuration, this is always 3389. If you have changed this value, adjust

Remote Desktop uses Windows RDP (Remote Desktop Protocol) and can only be used to access Host PCs running Windows Server 2003/2008, XP Professional,

Disconnecting from the Remote Desktop 187 Connecting via Windows Home Server Web Site Remote Access 187. Configuring Users for Remote

To manually unlock an account you must logon as another administrator user (preferably one without remote desktop access).. Click on the individual user and uncheck the