Virtual Network, Azure Connect, DNS, and VM

Question

Several small questions here:

After I created a Win2012 VM, within my Virtual Networks, I wonder then how to enable this VM to use Azure Connect? I have Azure Connect on my desktop.

So Virtual Networks is for group-to-group talking, but unless my network admin config his VPN server accordingly, this won't happen, is that correct? Then I only left Azure Connect to play with?

When I created my Virtual Network, I followed the How-To page to create a DNS, then it seems that my VM can't figure out any domain name, so what does this creating a DNS means? Is that I need to take that IP and config my VM as a DNS server as well, or something else?

If I want multiple VM within a Region/DataCentre to 'see' each other, what tool/feature I need?

If I want multiple VM cross Region/DataCentre to 'see' each other, what I need?

What about multiple VM all able to 'talk' to my desktop?

Best,

dong

Answer 1

Azure Connect is for VM-to-VM connectivity, where virtual networks are for site-to-site connectivity.

See also https://www.windowsazure.com/en-us/home/features/networking/

There is a list of supported VPN devices for cross-premises connectivity with virtual networks. See About VPN Devices for Virtual Network for more information.

By default, with no virtual network configured, a virtual machine will use Azure's internal DNS. However when you create a VM in a virtual network you created, the VM is given an IP address from the range you specified in the virtual network as well as whatever DNS server you specified, if any.

Note that VMs by default all have a public endpoint that allows you to connect via RDP (Windows) or SSH (Linux), and you can create your own endpoints on VMs to open up other TCP or UDP ports.

See also:

• Create a Virtual Network in Windows Azure
• Create a Virtual Network for Cross-Premises Connectivity
• Add a Virtual Machine to a Virtual Network
• Establish a Site-to-Site VPN Connection
• About VPN Devices for Virtual Network
• Windows Azure Virtual Network
• Windows Azure Name Resolution Overview
• About Configuring a Virtual Network in the Management Portal
• About Affinity Groups for Virtual Network

Thanks,
Craig

Answer 2

Hi, Craig,

Sorry I need to ask again

1, How do I enable Azure Connect on my Windows VM created with the preview?

2, How to set up File Share on 2012VM so that I could map drive to it from my laptop?

Thanks very much!

Best,

dong

Answer 3

Hi Dong,

You can use the Windows Azure portal (the portal in production and not preview) to manage connect. You will have to manually deploy the Agent in the VM.

You can configure a Server 2012 as a file server by enabling the file server role. If you want to access it from the internet, please open up port 445. This opens up your file server to the internet and there is no authentication offered by default.

Thanks,

Ganesh

Answer 4

Thanks for this reply.

In case anyone want to install Azure Connect on Server 2012, you might need to read this:

http://blog.kloud.com.au/2012/06/17/windows-azure-connect-compatibility-on-windows-82012-release-preview/

My further question down the line: if I need to do this to many nodes, any chance not by hand?

Best,

dong

Answer 5

Hi Dong,

You can use the Windows Azure portal (the portal in production and not preview) to manage connect. You will have to manually deploy the Agent in the VM.

You can configure a Server 2012 as a file server by enabling the file server role. If you want to access it from the internet, please open up port 445. This opens up your file server to the internet and there is no authentication offered by default.

Thanks,

Ganesh

Hello, since you refer to the production portal, where Azure Virtual Machines is not available, I understand the is not posible to use Azure Connect with Azure Virtual Machines, correct? I understand it is posible with the VM role, but it's not clear if it's posible with Azure Virtual Machines. Can anyone clarify this please?

---

Microsoft Peru

Answer 6

Hi Marcel,

I hope I can explain the case to you

1. You create VM for You in PReview Portal

2. THen You get activation token (and install command) from Production Portal

3. THen You Remotely log in to Your VM and install Endpoint

4. NOw in Production Portal You can add Your endpoint into group Your Laptop belongs

Henn

PS! Question for "big round" - is there a plan to add Connections into Preview Portal

---

Henn Sarv