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
Copy file name to clipboardExpand all lines: includes/virtual-network-multiple-ip-addresses-os-config.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,19 +29,19 @@ Connect and sign in to a VM you created with multiple private IP addresses. You
29
29
***Subnet mask**: Set based on your subnet. For example, if the subnet is a /24 subnet then the subnet mask is 255.255.255.0.
30
30
***Default gateway**: The first IP address in the subnet. If your subnet is 10.0.0.0/24, then the gateway IP address is 10.0.0.1.
31
31
* Select **Use the following DNS server addresses** and enter the following values:
32
-
***Preferred DNS server**: If you are not using your own DNS server, enter 168.63.129.16. If you are using your own DNS server, enter the IP address for your server. (For Alternate DNS Server you can pick any free public DNS server address.)
32
+
***Preferred DNS server**: If you aren't using your own DNS server, enter 168.63.129.16. If you're using your own DNS server, enter the IP address for your server. (For Alternate DNS Server you can pick any free public DNS server address.)
33
33
* Select the **Advanced** button and add additional IP addresses. Add each of the secondary private IP addresses, that you added to the Azure network interface in a previous step, to the Windows network interface that is assigned the primary IP address assigned to the Azure network interface.
34
34
35
-
You should never manually assign the public IP address assigned to an Azure virtual machine within the virtual machine's operating system. When you manually set the IP address within the operating system, ensure that it is the same address as the private IP address assigned to the Azure [network interface](../articles/virtual-network/ip-services/virtual-network-network-interface-addresses.md#change-ip-address-settings), or you can lose connectivity to the virtual machine. Learn more about [private IP address](../articles/virtual-network/ip-services/virtual-network-network-interface-addresses.md#private) settings. You should never assign an Azure public IP address within the operating system.
35
+
You should never manually assign the public IP address assigned to an Azure virtual machine within the virtual machine's operating system. When you manually set the IP address within the operating system, ensure that it's the same address as the private IP address assigned to the Azure [network interface](../articles/virtual-network/ip-services/virtual-network-network-interface-addresses.md#change-ip-address-settings), or you can lose connectivity to the virtual machine. Learn more about [private IP address](../articles/virtual-network/ip-services/virtual-network-network-interface-addresses.md#private) settings. You should never assign an Azure public IP address within the operating system.
36
36
37
-
*Click**OK** to close out the TCP/IP settings and then **OK** again to close the adapter settings. Your RDP connection is re-established.
37
+
*Select**OK** to close out the TCP/IP settings and then **OK** again to close the adapter settings. Your RDP connection is re-established.
38
38
39
39
6. From a command prompt, type *ipconfig /all*. Verify all IP addresses you added are shown and DHCP is turned off.
40
40
7. Configure Windows to use the private IP address of the primary IP configuration in Azure as the primary IP address for Windows. See [No Internet access from Azure Windows VM that has multiple IP addresses](https://support.microsoft.com/help/4040882/no-internet-access-from-azure-windows-vm-that-has-multiple-ip-addresse) for details.
41
41
42
42
#### Validation (Windows Server)
43
43
44
-
To ensure you are able to connect to the internet from your secondary IP configuration via the public IP associated it, once you have added it correctly using steps above, use the following command (replacing 10.0.0.7 with the secondary, private IP address):
44
+
To ensure you're able to connect to the internet from your secondary IP configuration via the public IP associated it, once you've added it correctly using steps above, use the following command (replacing 10.0.0.7 with the secondary, private IP address):
45
45
46
46
```bash
47
47
ping -S 10.0.0.7 outlook.com
@@ -60,7 +60,7 @@ ping -S 10.0.0.7 outlook.com
60
60
We recommend looking at the latest documentation for your Linux distribution.
61
61
62
62
1. Open a terminal window.
63
-
2. Make sure you are the root user. If you are not, enter the following command:
63
+
2. Make sure you're the root user. If you aren't, enter the following command:
64
64
65
65
```bash
66
66
sudo -i
@@ -118,7 +118,7 @@ We recommend looking at the latest documentation for your Linux distribution.
118
118
119
119
#### Validation (Ubuntu 14/16)
120
120
121
-
To ensure you are able to connect to the internet from your secondary IP configuration via the public IP associated it, use the following command:
121
+
To ensure you're able to connect to the internet from your secondary IP configuration via the public IP associated it, use the following command:
122
122
123
123
```bash
124
124
ping -I 10.0.0.5 outlook.com
@@ -151,7 +151,7 @@ ip route add default via 10.0.0.1 dev eth2 table custom
151
151
Ubuntu 18.04 and above have changed to `netplan` for OS network management. We recommend looking at the latest documentation for your Linux distribution.
152
152
153
153
1. Open a terminal window.
154
-
2. Make sure you are the root user. If you are not, enter the following command:
154
+
2. Make sure you're the root user. If you are not, enter the following command:
155
155
156
156
```bash
157
157
sudo -i
@@ -222,7 +222,7 @@ Ubuntu 18.04 and above have changed to `netplan` for OS network management. We r
222
222
223
223
#### Validation (Ubuntu 18.04+)
224
224
225
-
To ensure you are able to connect to the internet from your secondary IP configuration via the public IP associated it, use the following command:
225
+
To ensure you're able to connect to the internet from your secondary IP configuration via the public IP associated it, use the following command:
226
226
227
227
```bash
228
228
ping -I 10.0.0.5 outlook.com
@@ -253,13 +253,13 @@ ip route add default via 10.0.0.1 dev eth2 table custom
253
253
<summary>Expand</summary>
254
254
255
255
1. Open a terminal window.
256
-
2. Make sure you are the root user. If you are not, enter the following command:
256
+
2. Make sure you're the root user. If you are not, enter the following command:
257
257
258
258
```bash
259
259
sudo -i
260
260
```
261
261
262
-
3. Enter your password and follow instructions as prompted. Once you are the root user, navigate to the network scripts folder with the following command:
262
+
3. Enter your password and follow instructions as prompted. Once you're the root user, navigate to the network scripts folder with the following command:
263
263
264
264
```bash
265
265
cd /etc/sysconfig/network-scripts
@@ -312,7 +312,7 @@ ip route add default via 10.0.0.1 dev eth2 table custom
312
312
313
313
#### Validation (Red Hat, CentOS, and others)
314
314
315
-
To ensure you are able to connect to the internet from your secondary IP configuration via the public IP associated it, use the following command:
315
+
To ensure you're able to connect to the internet from your secondary IP configuration via the public IP associated it, use the following command:
316
316
317
317
```bash
318
318
ping -I 10.0.0.5 outlook.com
@@ -343,7 +343,7 @@ ip route add default via 10.0.0.1 dev eth2 table custom
343
343
<summary>Expand</summary>
344
344
345
345
1. Open a terminal window.
346
-
1. Make sure you are the root user. If you are not, enter the following command:
346
+
1. Make sure you're the root user. If you are not, enter the following command:
0 commit comments