Azure VM cannot connect to the second network adapter of an Azure VM in same virtual network

Configurare noua (How To)



Azure VM cannot connect to the second network adapter of an Azure VM in same virtual network

Step 1: Make sure that the second network adapter is enabled to talk outside the subnet. By default, secondary network adapters (also known as network interface cards, or network adapters) are not configured to have a default gateway. Therefore, the traffic flow on the secondary adapter will be limited to the same subnet.

IP configures

If users want to enable secondary network adapters to talk outside their own subnet, they must add an entry to the routing table to configure the gateway. To do this, follow these steps:

  1. On the VM that has the second network adapter configured, open a Command Prompt window as an administrator.
  2. Run the following command to add the entry in routing table:

    Windows Command Prompt Copy:

    Route add mask -p <Gateway IP>

    For example, if the second IP address is, the gateway IP should be You have to run the following command:

    Windows Command Prompt Copy:

    Route add mask -p
  3. Run route print. If the entry is added successfully, you will see an entry that resembles the following:IP route

Now, try to connect to secondary network adapter. If the connection is still unsuccessful, go to next step.

Step 2: Check NSG settings for the network adapters

For both the primary and secondary network adapters, check the default Inbound port rules (Allow VNet Inbound, Allow Load Balancer) to inbound on both network adapters. You should also make sure that there are no matching blocking rules that have a lower-priority rule above them.

Screenshot shows the Networking settings for a virtual machine where you can see Allow V net Inbound and Allow V net OutBound.

Step 3: Run a connectivity check to the secondary network adapter
  1. Run a connectivity check to the secondary network adapter.
  2. Run a connectivity check across the environment to make sure that the process works end to end.

The following is an example response:

ConnectionStatus : Unreachable
AvgLatencyInMs   : 
MinLatencyInMs   : 
MaxLatencyInMs   : 
ProbesSent       : 100
ProbesFailed     : 100
Hops             : [
                       "Type": "Source",
                       "Id": "c5222ea0-3213-4f85-a642-cee63217c2f3",
                       "Address": "",
                       "ResourceId": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGrou
                       "NextHopIds": [
                       "Issues": []
                       "Type": "VirtualAppliance",
                       "Id": "9283a9f0-cc5e-4239-8f5e-ae0f3c19fbaa",
                       "Address": "",
                       "ResourceId": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGrou
                       "NextHopIds": [
                       "Issues": []
Step 4: Refer the table under Step 5, and follow these steps to resolve the issues.

Azure VM cannot connect to the internet

Step 1: Check whether the network adapter is in a failed state.

Follow these steps to check the state of the NIC:

  1. Log in to the Resource Explorer portal.
  2. In the left pane, select Subscriptions.
  3. In the left pane, select the resource group that the affected network adapter or VM belongs to.
  4. Go to the Microsoft Network.
  5. Select the Network Interfaces option.
  6. Select the affected network interface.
  7. Select the Read/Write option at the top of the portal.
  8. Select the Edit option.NIC1

     Note: After you select the Edit option, the “Get” option changes to a Put option.


  9. Select the affected network interface, and then select the Put option.

     Note: After you make this selection, the ProvisioningState is displayed as Updating. The same result is shown on the regular Azure Resource Manager portal. If the operation is completed successfully, the ProvisioningState value changes to Succeeded, as shown.

  10. Refresh your portal. The network adapter should be in a success state.
Step 2: Follow Step 4 to run a connectivity check.
Step 3: Refer the table under Step 5, and follow the steps to resolve the issues.

Tip solutie



(4 din 6 persoane apreciaza acest articol)

Despre Autor

Leave A Comment?