jayakarteek opened a new pull request #2213: CLOUDSTACK-10023: Windows VMs with 
Multiple Nics fail to access internet
URL: https://github.com/apache/cloudstack/pull/2213
 
 
   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 ACS)
   Try to access internet
   EXPECTED BEHAVIOR
   ==================
   Windows VM should be able to access internet
   ACTUAL BEHAVIOR
   ==================
   Windows VM is not able to access internet
   
   
   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).  
   
   You may want to make Windows to select certain gateway always, we can change 
interface metrics:
    
   Go to your Network adapter properties
   Select Internet Protocol v4.
   Click the Advanced button on General tab.
   Uncheck Automatic metric.
   Enter a number higher than 10 to the Interface metric field.
   
   The default automatic metric for interfaces is 10. The lower the metric, the 
higher the preference to use it. So, we have to enter metric higher than 10 for 
the interfaces you 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.
   
   Window stand point the above mentioned issue can be resolved by setting 
metric for NICs inside guest OS
   
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to