We are in the process of configuring a windows 2008 server, which will host an apache application and an IIS application, under different DNS names. The simplest approach we could think of was to apply two separate IP addresses, bind one to the apache instance, and bind one to the IIS instance (using the netsh ip listen command).
To do this we have teamed the networks cards (Broadcom 5709 in a Dell R610 server) together using the BACS3 suite - all good so far. Next we added the static IP for the server, then added an additional IP address to the card. All seems to be fine.
THEN - all of a sudden other sites are unable to connect to the second IP address, then the primary one drops as well. Strangely, if I am connected to the server through RDP I can continue to access the machine without issue, but the machine then reports "no internet access" and i am unable to ping anything (even the default router). This problem disappears after a reboot, but then comes back again shortly after.
If i change the secondary Ip address everything works again, then stops working again shortly after!
I suspect this is down to some sort of weird routing issue (latest network drivers and management software from Broadcom already tried - as has a replacement mainboard from Dell!) - but can't fathom out why we have a similar setup elsewhere (two servers with teamed nics, running multiple IP addresses, but with MS Load balancing) - and these work faultlessly?