You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "sudharma jain (JIRA)" <ji...@apache.org> on 2015/12/02 05:31:10 UTC

[jira] [Created] (CLOUDSTACK-9098) Windows VMs fail to access internet

sudharma jain created CLOUDSTACK-9098:
-----------------------------------------

             Summary: Windows VMs fail to access internet
                 Key: CLOUDSTACK-9098
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9098
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
            Reporter: sudharma jain


If we deploy a Windows 2008 R2 64 bit server with 2 nics; default gateway is shown for both the NICs.
Now, based on my findings Windows will experience issue if we have multiple default gateway assigned as explained in "Multiple Default Gateways Can Cause Connectivity Problems" ([https://support.microsoft.com/en-us/kb/159168]).

REPRO STEPS
==================
Create a Windows VM with Multiple NICs
Ensure that only one of the NICs can actually access internet (set that as default NIC in CCP)
Try to access internet

The fix can be made using interface metric. The default automatic metric for interfaces is 10 or 20. The lower the metric, the higher the preference to use it. So, we have to enter metric higher than 10/20 for the interfaces we don't want to use. This is because if Windows has multiple interfaces connected to several networks that use DHCP, it installs default gateways for all those interfaces. By default, Windows sets the metric of the default gateways to the same, effectively leading to random selection of default gateway.
So from Window stand point the above mentioned issue can be resolved by setting metric for NICs inside guest OS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)