You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Learn how to determine the public IP address and port number range of virtual machines in a lab so information maybe added to firewall rules.
4
4
author: emaher
5
5
@@ -10,78 +10,23 @@ ms.service: lab-services
10
10
---
11
11
# Firewall settings for Azure Lab Services
12
12
13
-
Each school will set up their own network in a way that best fits their needs. Sometimes that includes setting firewall rules that block Remote Desktop (rdp) or Secure Shell (ssh) connections to machines outside their own network. Because Azure Lab Services runs in the public cloud, some extra configuration maybe needed to allow students to access their VM when connecting from the campus network.
13
+
Each organization or school will set up their own network in a way that best fits their needs. Sometimes that includes setting firewall rules that block Remote Desktop Protocol (rdp) or Secure Shell (ssh) connections to machines outside their own network. Because Azure Lab Services runs in the public cloud, some extra configuration maybe needed to allow students to access their VM when connecting from the campus network.
14
14
15
-
Each lab uses single public IP address and multiple ports. All VMs, both the template VM and student VMs, will use this public IP address. The public IP address will not change for the life of lab. However, each VM will have a different port number. The port numbers range from 49152 to 65535. The combination of public IP address and port number is used to connect teacher and students to the correct VM. This article will cover how to find the specific public ip address used by a lab. That information can be used to update inbound and outbound firewall rules so students can access their VMs.
15
+
Each lab uses single public IP address and multiple ports. All VMs, both the template VM and student VMs, will use this public IP address. The public IP address will not change for the life of lab. However, each VM will have a different port number. The port numbers range from 49152 to 65535. The combination of public IP address and port number is used to connect instructor and students to the correct VM. This article will cover how to find the specific public IP address used by a lab. That information can be used to update inbound and outbound firewall rules so students can access their VMs.
16
16
17
17
>[!IMPORTANT]
18
-
>Each lab will have a different public IP address. These steps will be required for every lab you want to access from within your school's network.
18
+
>Each lab will have a different public IP address.
19
19
20
-
## Get a lab's hostname
20
+
## Find public IP for a lab
21
21
22
-
To get the public IP address of a lab, we'll first need to get the lab’s hostname. For a Linux VM, the ssh connection information can be used. For a Windows VM, rdp file information can be used. A lab’s template VM and all user Lab VMs will share a public IP address.
22
+
The public IP addresses for each lab are listed in the **All labs** blade of the Lab Services lab account. For directions how to find the **All labs** blade, see [how to manage labs in a lab account](how-to-manage-lab-accounts.md#view-and-manage-labs-in-the-lab-account).
VM host names are everything after the '@' sign. The host name will follow the pattern `{vm-name}-ml-lab-{guid}.{location}.cloudapp.azure.com:{port-number}`. In the above example, `ml-lab-00000000-0000-0000-0000-000000000000.eastus2.cloudapp.azure.com` is the host name.
40
-
41
-
### Get a lab's hostname for Windows VM
42
-
43
-
We will cover how to get the hostname for the template VM. However, Remote Desktop connection details from either can be used.
44
-
45
-
- Go to the [template tile](use-dashboard.md#template-tile).
46
-
- Start the VM if it is stopped.
47
-
- Click the **Customize template** button.
48
-
- Open your Downloads folder.
49
-
- Right-click the {vm-name}.rdp file. Choose **Open With** -> **Notepad**.
50
-
- Copy the full address value.
51
-
52
-
The rdp file will have contents that look something like the following.
53
-
54
-
```text
55
-
full address:s:ml-lab-00000000-0000-0000-0000-000000000000.eastus2.azure.com:12345
56
-
prompt for credentials:i:1
57
-
username:s:~\UserName
58
-
```
59
-
60
-
The host name will follow the pattern `{vm-name}-ml-lab-{guid}.{location}.cloudapp.azure.com:{port-number}`. In the above example, the host name is `ml-lab-00000000-0000-0000-0000-000000000000.eastus2.azure.com`.
61
-
62
-
## Get a lab's public ip address
63
-
64
-
Next, we need to use the lab's hostname to get the lab's public ip address. The host name is everything after the @. There are many tools that can accomplish this task. We will cover how to us nslookup. The nslookup tool comes pre-installed installed on Windows, macOS, and Linux.
65
-
66
-
Type the following command into your command-line window. Make sure to replace example hostname with your lab’s hostname.
Note the IPV4 address that matches the hostname for the VM. In our example, the public IP address is 111.111.111.111.
27
+
>[!NOTE]
28
+
>You won’t see the public IP address if the template machine for your lab isn’t published yet.
84
29
85
30
## Conclusion
86
31
87
-
Now we know the public IP address for the lab. Inbound and outbound rules can be created for the school's firewall for the public ip address and the port range 49152-65535. Now, students can access their VMs without the school network firewall blocking access.
32
+
Now we know the public IP address for the lab. Inbound and outbound rules can be created for the organization's firewall for the public ip address and the port range 49152-65535. Once the rules are updated, students can access their VMs without the network firewall blocking access.
0 commit comments