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: articles/vpn-gateway/vpn-gateway-vpn-faq.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,8 +38,8 @@ No. However, costs for any additional public IPs are charged accordingly. See [I
38
38
39
39
The following cross-premises virtual network gateway connections are supported:
40
40
41
-
***Site-to-site**: VPN connection over IPsec (IKEv1 and IKEv2). This type of connection requires a VPN device or Windows Server Routing and Remote Access. For more information, see [Create a site-to-site VPN connection in the Azure portal](./tutorial-site-to-site-portal.md).
42
-
***Point-to-site**: VPN connection over Secure Socket Tunneling Protocol (SSTP) or IKEv2. This connection doesn't require a VPN device. For more information, see [Configure server settings for point-to-site VPN Gateway certificate authentication](vpn-gateway-howto-point-to-site-resource-manager-portal.md).
41
+
***Site-to-site (S2S)**: VPN connection over IPsec (IKEv1 and IKEv2). This type of connection requires a VPN device or Windows Server Routing and Remote Access. For more information, see [Create a site-to-site VPN connection in the Azure portal](./tutorial-site-to-site-portal.md).
42
+
***Point-to-site (P2S)**: VPN connection over Secure Socket Tunneling Protocol (SSTP) or IKEv2. This connection doesn't require a VPN device. For more information, see [Configure server settings for point-to-site VPN Gateway certificate authentication](vpn-gateway-howto-point-to-site-resource-manager-portal.md).
43
43
***Network-to-network**: This type of connection is the same as a site-to-site configuration. A connection between virtual networks is a VPN connection over IPsec (IKEv1 and IKEv2). It doesn't require a VPN device. For more information, see the [Configure a network-to-network VPN gateway connection](vpn-gateway-howto-vnet-vnet-resource-manager-portal.md).
44
44
***Azure ExpressRoute**: ExpressRoute is a private connection to Azure from your wide area network, not a VPN connection over the public internet. For more information, see the [ExpressRoute technical overview](../expressroute/expressroute-introduction.md) and the [ExpressRoute FAQ](../expressroute/expressroute-faqs.md).
45
45
@@ -177,7 +177,7 @@ For the classic deployment model:
177
177
178
178
### Can I use NAT-T on my VPN connections?
179
179
180
-
Yes, NAT traversal (NAT-T) is supported. Azure VPN Gateway does *not* perform any NAT-like functionality on the inner packets to or from the IPsec tunnels. In this configuration, ensure that the on-premises device initiates the IPSec tunnel.
180
+
Yes, network address translation traversal (NAT-T) is supported. Azure VPN Gateway does *not* perform any NAT-like functionality on the inner packets to or from the IPsec tunnels. In this configuration, ensure that the on-premises device initiates the IPSec tunnel.
181
181
182
182
### Can I set up my own VPN server in Azure and use it to connect to my on-premises network?
183
183
@@ -366,15 +366,15 @@ Yes. See [Configure forced tunneling](vpn-gateway-about-forced-tunneling.md).
366
366
367
367
### If my virtual machine is in a virtual network and I have a cross-premises connection, how should I connect to the VM?
368
368
369
-
You have a few options. If you have RDP enabled for your VM, you can connect to your virtual machine by using the private IP address. In that case, you would specify the private IP address and the port that you want to connect to (typically 3389). You'll need to configure the port on your virtual machine for the traffic.
369
+
If you have Remote Desktop Protocol (RDP) enabled for your VM, you can connect to your virtual machine by using the private IP address. In that case, you specify the private IP address and the port that you want to connect to (typically 3389). You need to configure the port on your virtual machine for the traffic.
370
370
371
-
You can also connect to your virtual machine by private IP address from another virtual machine that's located on the same virtual network. You can't RDP to your virtual machine by using the private IP address if you're connecting from a location outside of your virtual network. For example, if you have a point-to-site virtual network configured and you don't establish a connection from your computer, you can't connect to the virtual machine by private IP address.
371
+
You can also connect to your virtual machine by private IP address from another virtual machine that's located on the same virtual network. You can't RDP to your virtual machine by using the private IP address if you're connecting from a location outside your virtual network. For example, if you have a point-to-site virtual network configured and you don't establish a connection from your computer, you can't connect to the virtual machine by private IP address.
372
372
373
373
### If my virtual machine is in a virtual network with cross-premises connectivity, does all the traffic from my VM go through that connection?
374
374
375
-
No. Only the traffic that has a destination IP that is contained in the virtual network Local Network IP address ranges that you specified goes through the virtual network gateway.
375
+
No. Only the traffic that has a destination IP that's contained in the virtual network's local network IP address ranges that you specified goes through the virtual network gateway.
376
376
377
-
Traffic has a destination IP located within the virtual network stays within the virtual network. Other traffic is sent through the load balancer to the public networks, or if forced tunneling is used, sent through the VPN gateway.
377
+
Traffic that has a destination IP located within the virtual network stays within the virtual network. Other traffic is sent through the load balancer to the public networks. Or if you use forced tunneling, the traffic is sent through the VPN gateway.
378
378
379
379
### How do I troubleshoot an RDP connection to a VM
Copy file name to clipboardExpand all lines: includes/vpn-gateway-configure-vpn-device-rm-include.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ The following links provide more configuration information:
28
28
29
29
- For cryptographic requirements, see [About cryptographic requirements and Azure VPN gateways](../articles/vpn-gateway/vpn-gateway-about-compliance-crypto.md).
30
30
31
-
- For information about parameter information that you need to complete your configuration, see [Default IPsec/IKE parameters](../articles/vpn-gateway/vpn-gateway-about-vpn-devices.md#ipsec). The information includes IKE version, Diffie-Hellman group, authentication method, encryption and hashing algorithms, security association lifetime, Perfect Forward Secrecy, and Dead Peer Detection (DPD).
31
+
- For information about parameter information that you need to complete your configuration, see [Default IPsec/IKE parameters](../articles/vpn-gateway/vpn-gateway-about-vpn-devices.md#ipsec). The information includes IKE version, Diffie-Hellman (DH) group, authentication method, encryption and hashing algorithms, security association (SA) lifetime, Perfect Forward Secrecy (PFS), and Dead Peer Detection (DPD).
32
32
33
33
- For IPsec/IKE policy configuration steps, see [Configure custom IPsec/IKE connection policies for S2S VPN and VNet-to-VNet](../articles/vpn-gateway/vpn-gateway-ipsecikepolicy-rm-powershell.md).
Copy file name to clipboardExpand all lines: includes/vpn-gateway-connect-vm-troubleshoot-include.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,11 +13,11 @@ If you're having trouble connecting to a virtual machine over your VPN connectio
13
13
14
14
* Verify that your VPN connection is successful.
15
15
* Verify that you're connecting to the private IP address for the VM.
16
-
* If you can connect to the VM using the private IP address, but not the computer name, verify that you have configured DNS properly. For more information about how name resolution works for VMs, see [Name Resolution for VMs](../articles/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md).
16
+
* If you can connect to the VM by using the private IP address but not the computer name, verify that you configured DNS properly. For more information about how name resolution works for VMs, see [Name resolution for resources in Azure virtual networks](../articles/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md).
17
17
18
-
When you connect over Point-to-Site, check the following additional items:
18
+
When you connect over point-to-site, check the following additional items:
19
19
20
-
* Use 'ipconfig' to check the IPv4 address assigned to the Ethernet adapter on the computer from which you're connecting. If the IP address is within the address range of the virtual network that you're connecting to, or within the address range of your VPNClientAddressPool, this is referred to as an overlapping address space. When your address space overlaps in this way, the network traffic doesn't reach Azure, it stays on the local network.
21
-
* Verify that the VPN client configuration package was generated after the DNS server IP addresses were specified for the virtual network. If you updated the DNS server IP addresses, generate and install a new VPN client configuration package.
20
+
* Use `ipconfig` to check the IPv4 address assigned to the Ethernet adapter on the computer from which you're connecting. If the IP address is within the address range of the virtual network that you're connecting to, or within the address range of your VPN client address pool, it's an overlapping address space. When your address space overlaps in this way, the network traffic doesn't reach Azure. It stays on the local network.
21
+
* Verify that the VPN client configuration package was generated after you specified the DNS server IP addresses for the virtual network. If you updated the DNS server IP addresses, generate and install a new VPN client configuration package.
22
22
23
-
For more information about troubleshooting an RDP connection, see [Troubleshoot Remote Desktop connections to a VM](/troubleshoot/azure/virtual-machines/troubleshoot-rdp-connection).
23
+
For more information about troubleshooting an RDP connection, see [Troubleshoot Remote Desktop connections to a VM](/troubleshoot/azure/virtual-machines/troubleshoot-rdp-connection).
Copy file name to clipboardExpand all lines: includes/vpn-gateway-customer-controlled-gateway-maintenance-faq.md
+23-23Lines changed: 23 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,57 +9,57 @@ ms.topic: include
9
9
10
10
---
11
11
12
-
### Which services are included in the Maintenance Configuration scope of Network Gateways?
12
+
### Which services are included in maintenance configuration for the Network Gateways scope?
13
13
14
-
The Network Gateways scope includes gateway resources in Networking services. There are four types of resources in the Network Gateways scope:
14
+
The Network Gateways scope includes gateway resources in networking services. There are four types of resources in the Network Gateways scope:
15
15
16
-
* Virtual network gateway in the ExpressRoute service.
17
-
* Virtual network gateway in the VPN Gateway service.
18
-
* VPN gateway (Site-to-Site) in the Virtual WAN service.
19
-
* ExpressRoute gateway in the Virtual WAN service.
16
+
* Virtual network gateway in the ExpressRoute service
17
+
* Virtual network gateway in the VPN Gateway service
18
+
* VPN gateway (site-to-site) in the Azure Virtual WAN service
19
+
* ExpressRoute gateway in the Virtual WAN service
20
20
21
-
### Which maintenance is supported or not supported by customer-controlled maintenance?
21
+
### Which maintenance does customer-controlled maintenance support?
22
22
23
-
Azure services go through periodic maintenance updates to improve functionality, reliability, performance, and security. Once you configure a maintenance window for your resources, Guest OS and Service maintenance are performed during that window. Host updates, beyond the host updates (TOR, Power etc.) and critical security updates, aren't covered by the customer-controlled maintenance.
23
+
Azure services go through periodic maintenance updates to improve functionality, reliability, performance, and security. After you configure a maintenance window for your resources, guest OS and service maintenance are performed during that window. Customer-controlled maintenance doesn't cover updates beyond the host updates (for example, TOR and power) and critical security updates.
24
24
25
25
### Can I get advanced notification of the maintenance?
26
26
27
-
At this time, advanced notification can't be enabled for the maintenance of Network Gateway resources.
27
+
At this time, you can't get advanced notification for the maintenance of network gateway resources.
28
28
29
29
### Can I configure a maintenance window shorter than five hours?
30
30
31
-
At this time, you need to configure a minimum of a fivehour window in your preferred time zone.
31
+
At this time, you need to configure a minimum of a five-hour window in your preferred time zone.
32
32
33
-
### Can I configure a maintenance window other than Daily schedule?
33
+
### Can I configure a maintenance window other than a daily schedule?
34
34
35
35
At this time, you need to configure a daily maintenance window.
36
36
37
-
### Are there cases where I can’t control certain updates?
37
+
### Are there cases where I can't control certain updates?
38
38
39
-
Customer-controlled maintenance supports Guest OS and Service updates. These updates account for most of the maintenance items that cause concern for the customers. Some other types of updates, including Host updates, are outside of the scope of customer-controlled maintenance.
39
+
Customer-controlled maintenance supports guest OS and service updates. These updates account for most of the maintenance items that cause concern for customers. Some other types of updates, including host updates, are outside the scope of customer-controlled maintenance.
40
40
41
-
Additionally, if there's a high-severity security issue that might endanger our customers, Azure might need to override customer control of the maintenance window and push the change. These are rare occurrences that would only be used in extreme cases.
41
+
If a high-severity security issue might endanger customers, Azure might need to override customer control of the maintenance window and push a change. These changes are rare occurrences that we use only in in extreme cases.
42
42
43
-
### Do Maintenance Configuration resources need to be in the same region as the gateway resource?
43
+
### Do maintenance configuration resources need to be in the same region as the gateway resource?
44
44
45
-
Yes
45
+
Yes.
46
46
47
-
### Which gateway SKUs can be configured to use customer-controlled maintenance?
47
+
### Which gateway SKUs can I configure to use customer-controlled maintenance?
48
48
49
49
All gateway SKUs (except the Basic SKU for VPN Gateway) can be configured to use customer-controlled maintenance.
50
50
51
-
### How long does it take for maintenance configuration policy to become effective after it gets assigned to the gateway resource?
51
+
### How long does it take for a maintenance configuration policy to become effective after it's assigned to the gateway resource?
52
52
53
53
It might take up to 24 hours for Network Gateways to follow the maintenance schedule after the maintenance policy is associated with the gateway resource.
54
54
55
-
### Are there any limitations on using customer-controlled maintenance based on the Basic SKU Public IP address?
55
+
### Are there any limitations on using customer-controlled maintenance based on the Basic SKU public IP address?
56
56
57
-
Yes. Gateway resources that use a Basic SKU Public IP address will only be able to have service updates following the customer-controlled maintenance schedule. For these gateways, Guest OS maintenance does NOT follow the customer-controlled maintenance schedule due to infrastructure limitations.
57
+
Yes. Gateway resources that use a Basic SKU public IP address can have service updates only after the customer-controlled maintenance schedule. For these gateways, guest OS maintenance does *not* follow the customer-controlled maintenance schedule because of infrastructure limitations.
58
58
59
59
### How should I plan maintenance windows when using VPN and ExpressRoute in a coexistence scenario?
60
60
61
-
When working with VPN and ExpressRoute in a coexistence scenario or whenever you have resources acting as backups, we recommend setting up separate maintenance windows. This approach ensures that maintenance doesn't affect your backup resources at the same time.
61
+
When you work with VPN and ExpressRoute in a coexistence scenario or whenever you have resources that act as backups, we recommend setting up separate maintenance windows. This approach ensures that maintenance doesn't affect your backup resources at the same time.
62
62
63
-
### I've scheduled a maintenance window for a future date for one of my resources. Will maintenance activities be paused on this resource until then?
63
+
### I scheduled a maintenance window for a future date for one of my resources. Are maintenance activities paused on this resource until then?
64
64
65
-
No, maintenance activities won't be paused on your resource during the period before the scheduled maintenance window. For the days not covered in your maintenance schedule, maintenance continues as usual on the resource.
65
+
No, maintenance activities aren't paused on your resource during the period before the scheduled maintenance window. For the days not covered in your maintenance schedule, maintenance continues as usual on the resource.
0 commit comments