Windows Server 2008 Primary IP Address

We have a W2K8 server with 7 IP addresses on the same subnet for the purpose
of hosting multiple SSL websites, and this number may increase in future.

The server's "primary" address should be .1 with additional addresses going
up to .12 and we are finding that outbound connections from the server (SNMP,
HTTP etc) are using the .12 address. Presumably if we add .13, outbound
connections could start using this address, causing a nightmare for firewall
configuration and IP-address-based access control to web services.

Is there any way to fix the address used as the "primary" address for
outbound connections from the server?

Stuart Newton wrote:
> We have a W2K8 server with 7 IP addresses on the same subnet for the purpose
> of hosting multiple SSL websites, and this number may increase in future.
>
> The server's "primary" address should be .1 with additional addresses going
> up to .12 and we are finding that outbound connections from the server (SNMP,
> HTTP etc) are using the .12 address. Presumably if we add .13, outbound
> connections could start using this address, causing a nightmare for firewall
> configuration and IP-address-based access control to web services.
>
> Is there any way to fix the address used as the "primary" address for
> outbound connections from the server?

I run a number of 2008 web servers with multiple IP's for the same
reasons as you (multiple SSL sites) and have never come across this
issue. Our servers also use consecutive numbering, but not necessarily
from .1 upwards. The one I've just checked starts at .51 and has 6 IP's
(up to .57), but outbound traffic is always on .51. I've just confirmed
this by browsing to whatsmyip.org. from that server.

I'm afraid I cannot think what you've done differently, as I have never
seen the behaviour you describe.

Are all the IP's on one NIC?

If at all possible I would suggest you remove all but one IP from the
server and then try again.

Alister

"Stuart Newton" <Stuart (E-Mail Removed)> wrote in message
news:7597A23E-0673-48BA-A03E-(E-Mail Removed)...
> We have a W2K8 server with 7 IP addresses on the same subnet for the
> purpose
> of hosting multiple SSL websites, and this number may increase in future.
>
> The server's "primary" address should be .1 with additional addresses
> going
> up to .12 and we are finding that outbound connections from the server
> (SNMP,
> HTTP etc) are using the .12 address. Presumably if we add .13, outbound
> connections could start using this address, causing a nightmare for
> firewall
> configuration and IP-address-based access control to web services.
>
> Is there any way to fix the address used as the "primary" address for
> outbound connections from the server?


As Alister mentioned, I haven't seen this, either. Curious, is routing
enabled on this machine (such as RRAS)? Run an ipconfig /all. Does it show
IP routing enabled?

Post the ipconfig /all, as well as a "route print." Not promising anything,
but it's one place to start looking and see if anything's misconfigured.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

"Stuart Newton" wrote:

> We have a W2K8 server with 7 IP addresses on the same subnet for the purpose
> of hosting multiple SSL websites, and this number may increase in future.
>
> The server's "primary" address should be .1 with additional addresses going
> up to .12 and we are finding that outbound connections from the server (SNMP,
> HTTP etc) are using the .12 address. Presumably if we add .13, outbound
> connections could start using this address, causing a nightmare for firewall
> configuration and IP-address-based access control to web services.
>
> Is there any way to fix the address used as the "primary" address for
> outbound connections from the server?

I too have a similar problem.
I have 4 servers, all 2008 Web edition, each with multiple IP's for SSL and
each of which never use the primary IP address for outbound connections.
What I have found is that they use the first IP on the address of the
alternative IP's for outbound traffic so for me this works as a work around
that I can assign this in our firewall for outbound traffic. Not sure if
that is of any help to you?

Sean