We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now

x

I have a Windows 2008 Server with multiple IPs on same nic.

Medium Priority
2,710 Views
Last Modified: 2013-12-05
I have a Windows 2008 Server with multiple IPs on same nic. The IP I placed in the IP settings, isn't showing as the primary ip. It's seems to list the IPs in order. Is there a way to set the order?

Here are the IPs and the order that I want.
xxx.xxx.0.16 - primary
xxx.xxx.0.15 - secondary
xxx.xxx.0.17 - secondary

When I do a - whatismyip - it comes back with xxx.xxx.0.15 when it should be .16

It worked how I needed it on windows 2000 server. Is it possible to do the same on Windows 2008 server?
Comment
Watch Question

Commented:
If you have multiple IPs on a single NIC in the same subnet (which it looks like you do), they will each be routed to the internet (and whatismyip) with the same metric.  To see the metrics use: "route print" from a command line.

You can change these metrics using "ROUTE ADD networkid MASK networksubnetmask networkinterface metric x -p"; so in your case, you would want .16 to be your least costly way:
route add 0.0.0.0 mask 0.0.0.0 x.x.x.16 metric 5 -p

BTW - What is the last octect of your default gateway?

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Author

Commented:
Yes - I have multiple IPs on a single NIC in the same subnet.

Below is my route table.

Also, when adding a ROUTE ADD, how do I keep it on reboots?

Thanks for your response.

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      xxx.xxx.0.1     xxx.xxx.0.15    266
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      xxx.xxx.0.0    255.255.255.0         On-link      xxx.xxx.0.15    266
     xxx.xxx.0.15  255.255.255.255         On-link      xxx.xxx.0.15    266
     xxx.xxx.0.16  255.255.255.255         On-link      xxx.xxx.0.15    266
     xxx.xxx.0.17  255.255.255.255         On-link      xxx.xxx.0.15    266
    xxx.xxx.0.255  255.255.255.255         On-link      xxx.xxx.0.15    266
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      xxx.xxx.0.15    266
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      xxx.xxx.0.15    266
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0      xxx.xxx.0.1  Default
===========================================================================

Author

Commented:
Raised the point value to 500, still needing help.
Commented:
To make the routes persisten after reboots, you would use the route add ... -p
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.