Source IP address selection on a Multi-Homed Windows Computer

re: Source IP address selection on a Multi-Homed Windows Computer

Mike Crowley — Fri, 17 Dec 2010 20:19:06 GMT

What impact does binding order have on any/all of this?

re: Source IP address selection on a Multi-Homed Windows Computer

gümrük müşavirliği — Thu, 04 Feb 2010 15:25:53 GMT

thank you very good very good article

re: Source IP address selection on a Multi-Homed Windows Computer

web-tasarım — Sun, 29 Nov 2009 21:36:58 GMT

Introducing such a topic you'd like to congratulate you've let us know.

re: Source IP address selection on a Multi-Homed Windows Computer

Softlion — Thu, 03 Sep 2009 09:52:16 GMT

Thank you very much for this good article.

It finally explains nicely how this hell works on Windows and why Win2K8 behave correctly while Win3K does not in my configuration !

Thanks again for taking time writing this stuf !

Would like to see the same stuf for IIS6/7 : what source IP it does use for outbound connections and in which case ?

re: Source IP address selection on a Multi-Homed Windows Computer

web tasarim — Thu, 27 Aug 2009 01:17:32 GMT

on this matter Thank you for sharing with us such a thing

re: Source IP address selection on a Multi-Homed Windows Computer

güvenlik sistemleri — Tue, 11 Aug 2009 11:39:17 GMT

was truly telling about your site I thank you very much ongoing follow

re: Source IP address selection on a Multi-Homed Windows Computer

Damian Crosby — Fri, 15 May 2009 15:06:40 GMT

On Windows 2008 What happens in a scenario where we are using a loppback adapter to host a VIP (/32 address on the client - 10.173.48.58)that is being advertised out of both physical interfaces via RIP?

When the calling application binds to the VIP as its prefered source IP are you saying that the traffic will look for routes only applicable for the interface the VIP is bound to? That would suggest that the trafic will blackhole as there will be no logical route off of the server for this interface

Example config

Loopback Ethernet adapter1

IP Address. . . . . . . . . . . . : 10.173.48.58

Ethernet adapter2

IP Address. . . . . . . . . . . . : 10.171.34.107

Default Gateway . . . . . . . . . : 10.171.34.97

Ethernet adapter3

IP Address. . . . . . . . . . . . : 10.171.33.107

Default Gateway . . . . . . . . . : 10.171.33.97

re: Source IP address selection on a Multi-Homed Windows Computer

Damian Crosby — Tue, 12 May 2009 17:28:21 GMT

What would happen if you had a loopback adapter installed that had another IP assigned to it and you were to use that IP as the source. For example a /32 address assigned to the loopback that was being advertised out of both interfaces using RIP to provide resiliancy using networking protocols.

Example:

Source supplied in the call:10.0.0.10

Target IP:192.168.1.5

Route Table:

Nic 1 - 192.168.1.10/32

Nic 2 - 192.168.1.11/32

re: Source IP address selection on a Multi-Homed Windows Computer

Michael Dragone — Sun, 26 Apr 2009 20:12:11 GMT

Interesting. Very handy information to have around.

Microsoft Enterprise Networking Team : Source IP address selection … « Networking

Sat, 25 Apr 2009 01:31:11 GMT

PingBack from http://rapasasolutions01.com/26/microsoft-enterprise-networking-team-source-ip-address-selection/