I have a windows server 2008 R2 SP1. I have multiple internal ip addresses that get routed to it for various ssl certificates on different sites. It works something like this. Pretend 1.1.1.1 addresses are external ips (viewable to the world) and 2.2.2.2 are internal ips those get routed to. Within my network settings I have multiple internal ips in the properties of a the network i.e. 2.2.2.1 2.2.2.2 2.2.2.3 2.2.2.4 To the outside world the websites sitting on those ips would be showing external ips 1.1.1.1 routes to 2.2.2.1; 1.1.1.2 routes to 2.2.2.2 etc. The issue I'm having is the default internal ip address for this machine is 2.2.2.1. We have another server that hosts databases and allows the ip 2.2.2.1 access to them. I have added multiple ips and this is working fine. However, now I tried adding one more and I get a mysql connection error. It's saying that the internal ip 2.2.2.5 does not have permissions to connect. What I'm wondering is why the newest ip is taking precedence over the 2.2.2.1 address. Any ideas on how I can force this machine to use the 2.2.2.1 ip address as the ip to default too?- Michael

Hi Michael, According to your description, you want to use a specific IP 2.2.2.1 to connect mysql session with multi-homed network adapter. First, I would like to explain that multi-homed source IP address selection order has several rules. That means that connecting to your mysql server from definite source IP address is not random. According to the selection rule, ip 2.2.2.5 priors to ip 2.2.2.1. So you could add other ip address (like 2.2.2.6) to replace 2.2.2.5. Source IP address selection on a Multi-Homed Windows Computer http://blogs.technet.com/b/networking/archive/2009/04/24/source-ip-address-selection-on-a-multi-homed-windows-computer.aspx Another way, mysql could bind ip address with application. While I am not sure whether ip 2.2.2.1 works as a mysql server/client role. You could refer to the below articles. http://dev.mysql.com/doc/refman/5.0/en/server-options.html http://www.linuxforums.org/forum/servers/152285-mysql-bind-address-my-cnf.html Regards, Rick Tan

It turns out this has been a problem for a lot of people. I reached out to my server guy and here is a fix 1. Install this hotfix and reboot. http://support.microsoft.com/kb/2386184/ 2. Follow the excerpt from this post to setup the IPs that won't be used for outbound communication. http://social.technet.microsoft.com/Forums/en-US/winserverPN/thread/02c3f5d7-ae2d-48d5-b408-62530b628940 · Jim, Yes the hotfix works for us, but it is not as clean as just applying the patch. Once the hotfix was applied and we restarted the server, we had to remove all the IP addresses from the NIC except the primary IP address, and then add the web site IP addresses one at a time using the Netsh command outlined in the hotfix documentation. Then when you add the bindings for the specific IP to the IIS7 site, you need to enter the IP address in the dropdown box. It does not show up in the dropdown list anymore. Once you restart the "World Wide Web Publishing Service" everything started to operate correctly. So, the fix works for us. Dave - Michael