two nics, one ip

Is there a way to have two separate network interface cards have some
sort of failover redundancy with one ip address (two nics with one ip,
say 192.168.1.3, both cards pointing to that, or some implementation of
redundancy)?

This is on a brand new Windows 2003 Enterprise Server Edition.

Oh,

Some more information: The two interfaces are going to different
switches, and they are Intel Gigabit nics.

--
David Lee

(E-Mail Removed) wrote:
> Is there a way to have two separate network interface cards have some
> sort of failover redundancy with one ip address (two nics with one ip,
> say 192.168.1.3, both cards pointing to that, or some implementation of
> redundancy)?
>
> This is on a brand new Windows 2003 Enterprise Server Edition.

Hi David,

As I'm sure you've seen, trying to use the same IP address on two interfaces
within the same server will result in an error. If you have two servers,
you can set them up as a cluster using Terminal Services and assign them
both to the same virtual server IP address. You can find more information
about clustering here:
http://www.microsoft.com/downloads/d...DisplayLang=en

Alternatively, you can look into VRRP which works with some switches, or
Cisco's HSRP protocol.

I hope this helps.

--
Greg Lindsay [MSFT]
(E-Mail Removed)

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ps.com...
> Oh,
>
> Some more information: The two interfaces are going to different
> switches, and they are Intel Gigabit nics.
>
> --
> David Lee
>
> (E-Mail Removed) wrote:
>> Is there a way to have two separate network interface cards have some
>> sort of failover redundancy with one ip address (two nics with one ip,
>> say 192.168.1.3, both cards pointing to that, or some implementation of
>> redundancy)?
>>
>> This is on a brand new Windows 2003 Enterprise Server Edition.
>

Greg:

Wow....your reply had absolutely no connection to this question.

You really really really have to try to answer as poorly as that.

David:

What you are talking about is best solved by using nic "Teams". This will be
a hardware based solution, IE your NICS need to be made to support teaming.
Think of it like RAID 1 for your nics. There are lots of brands out there
that do it so I am sure you can find what you need now that you know it
exists.

The standard config for our companys server farms is to have at least one
nic team per server sharing one virtual IP. Each nic is attatched to a
seperate physical infractructure with seperate power systems and generators
and feeds to teamed routers that connect to a minimum of two diffrent kinds
of wan links which are all aggragated for maximum performance.

--
Manny Borges
MCSE NT4-2003 (+ Security)
MCT, Certified Cheese Master

There are 10 kinds of people in the world. Those who do understand binary
and those who don't.
"Greg Lindsay [MSFT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi David,
>
> As I'm sure you've seen, trying to use the same IP address on two
> interfaces within the same server will result in an error. If you have
> two servers, you can set them up as a cluster using Terminal Services and
> assign them both to the same virtual server IP address. You can find more
> information about clustering here:
> http://www.microsoft.com/downloads/d...DisplayLang=en
>
> Alternatively, you can look into VRRP which works with some switches, or
> Cisco's HSRP protocol.
>
> I hope this helps.
>
> --
> Greg Lindsay [MSFT]
> (E-Mail Removed)
>
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
>
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) ps.com...
>> Oh,
>>
>> Some more information: The two interfaces are going to different
>> switches, and they are Intel Gigabit nics.
>>
>> --
>> David Lee
>>
>> (E-Mail Removed) wrote:
>>> Is there a way to have two separate network interface cards have some
>>> sort of failover redundancy with one ip address (two nics with one ip,
>>> say 192.168.1.3, both cards pointing to that, or some implementation of
>>> redundancy)?
>>>
>>> This is on a brand new Windows 2003 Enterprise Server Edition.
>>
>
>

(E-Mail Removed) wrote:
> Oh,
>
> Some more information: The two interfaces are going to different
> switches, and they are Intel Gigabit nics.

Are these two switches on separate network segments?

Right Click on My Network Places, choose properties from the pop up menu,
hold the Ctrl key select the two NICs, Right click, select Bridge
Connections from the list, Right click on the Network Bridge, choose
properties, configure the bridge with the 192.168.1.3 IP address. The
network bridge should be connected to two physical Networks and should not
face each other.

http://www.microsoft.com/resources/d....mspx?mfr=true

>
>
> (E-Mail Removed) wrote:
>> Is there a way to have two separate network interface cards have some
>> sort of failover redundancy with one ip address (two nics with one
>> ip, say 192.168.1.3, both cards pointing to that, or some
>> implementation of redundancy)?


If you are wanting redundancy, you need NIC teaming or a hardware bridge.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

Thanks for the information.

I'll try the options out to see which one will fit the bill for the
server.

--
David Lee

Kevin D. Goodknecht Sr. [MVP] wrote:
> (E-Mail Removed) wrote:
> > Oh,
> >
> > Some more information: The two interfaces are going to different
> > switches, and they are Intel Gigabit nics.
>
> Are these two switches on separate network segments?
>
> Right Click on My Network Places, choose properties from the pop up menu,
> hold the Ctrl key select the two NICs, Right click, select Bridge
> Connections from the list, Right click on the Network Bridge, choose
> properties, configure the bridge with the 192.168.1.3 IP address. The
> network bridge should be connected to two physical Networks and should not
> face each other.
>
> http://www.microsoft.com/resources/d....mspx?mfr=true
>
> >
> >
> > (E-Mail Removed) wrote:
> >> Is there a way to have two separate network interface cards have some
> >> sort of failover redundancy with one ip address (two nics with one
> >> ip, say 192.168.1.3, both cards pointing to that, or some
> >> implementation of redundancy)?
>
>
> If you are wanting redundancy, you need NIC teaming or a hardware bridge.
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> https://secure.lsaol.com/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================

Manny,

Thanks for the information about teaming. However, I disagree that my
answer was off topic. VRRP is another form of redundant pathing that may
also work with his existing hardware, and has the advantage of recovery in
case of a switch failure. It may not be ideal if load balancing is desired,
but that's where you may wish to implement other solutions such as
clustering. When you say that you have "teamed routers" I think you are
referring to VRRP.

--
Greg Lindsay [MSFT]
(E-Mail Removed)

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

"Manny Borges" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Greg:
>
> Wow....your reply had absolutely no connection to this question.
>
> You really really really have to try to answer as poorly as that.
>
> David:
>
> What you are talking about is best solved by using nic "Teams". This will
> be a hardware based solution, IE your NICS need to be made to support
> teaming. Think of it like RAID 1 for your nics. There are lots of brands
> out there that do it so I am sure you can find what you need now that you
> know it exists.
>
> The standard config for our companys server farms is to have at least one
> nic team per server sharing one virtual IP. Each nic is attatched to a
> seperate physical infractructure with seperate power systems and
> generators and feeds to teamed routers that connect to a minimum of two
> diffrent kinds of wan links which are all aggragated for maximum
> performance.
>
> --
> Manny Borges
> MCSE NT4-2003 (+ Security)
> MCT, Certified Cheese Master
>
> There are 10 kinds of people in the world. Those who do understand binary
> and those who don't.
> "Greg Lindsay [MSFT]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi David,
>>
>> As I'm sure you've seen, trying to use the same IP address on two
>> interfaces within the same server will result in an error. If you have
>> two servers, you can set them up as a cluster using Terminal Services and
>> assign them both to the same virtual server IP address. You can find
>> more information about clustering here:
>> http://www.microsoft.com/downloads/d...DisplayLang=en
>>
>> Alternatively, you can look into VRRP which works with some switches, or
>> Cisco's HSRP protocol.
>>
>> I hope this helps.
>>
>> --
>> Greg Lindsay [MSFT]
>> (E-Mail Removed)
>>
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>>
>> <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed) ps.com...
>>> Oh,
>>>
>>> Some more information: The two interfaces are going to different
>>> switches, and they are Intel Gigabit nics.
>>>
>>> --
>>> David Lee
>>>
>>> (E-Mail Removed) wrote:
>>>> Is there a way to have two separate network interface cards have some
>>>> sort of failover redundancy with one ip address (two nics with one ip,
>>>> say 192.168.1.3, both cards pointing to that, or some implementation of
>>>> redundancy)?
>>>>
>>>> This is on a brand new Windows 2003 Enterprise Server Edition.
>>>
>>
>>
>
>

Greg - have a look at GLBP if you are interested in VRRP type solutions that
include load balancing.

"Greg Lindsay [MSFT]" <(E-Mail Removed)> wrote in message
news:u$(E-Mail Removed)...
> Manny,
>
> Thanks for the information about teaming. However, I disagree that my
> answer was off topic. VRRP is another form of redundant pathing that may
> also work with his existing hardware, and has the advantage of recovery in
> case of a switch failure. It may not be ideal if load balancing is
> desired, but that's where you may wish to implement other solutions such
> as clustering. When you say that you have "teamed routers" I think you
> are referring to VRRP.
>
> --
> Greg Lindsay [MSFT]
> (E-Mail Removed)
>
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
>
> "Manny Borges" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Greg:
>>
>> Wow....your reply had absolutely no connection to this question.
>>
>> You really really really have to try to answer as poorly as that.
>>
>> David:
>>
>> What you are talking about is best solved by using nic "Teams". This will
>> be a hardware based solution, IE your NICS need to be made to support
>> teaming. Think of it like RAID 1 for your nics. There are lots of brands
>> out there that do it so I am sure you can find what you need now that you
>> know it exists.
>>
>> The standard config for our companys server farms is to have at least one
>> nic team per server sharing one virtual IP. Each nic is attatched to a
>> seperate physical infractructure with seperate power systems and
>> generators and feeds to teamed routers that connect to a minimum of two
>> diffrent kinds of wan links which are all aggragated for maximum
>> performance.
>>
>> --
>> Manny Borges
>> MCSE NT4-2003 (+ Security)
>> MCT, Certified Cheese Master
>>
>> There are 10 kinds of people in the world. Those who do understand binary
>> and those who don't.
>> "Greg Lindsay [MSFT]" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Hi David,
>>>
>>> As I'm sure you've seen, trying to use the same IP address on two
>>> interfaces within the same server will result in an error. If you have
>>> two servers, you can set them up as a cluster using Terminal Services
>>> and assign them both to the same virtual server IP address. You can
>>> find more information about clustering here:
>>> http://www.microsoft.com/downloads/d...DisplayLang=en
>>>
>>> Alternatively, you can look into VRRP which works with some switches, or
>>> Cisco's HSRP protocol.
>>>
>>> I hope this helps.
>>>
>>> --
>>> Greg Lindsay [MSFT]
>>> (E-Mail Removed)
>>>
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers no rights.
>>>
>>> <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed) ps.com...
>>>> Oh,
>>>>
>>>> Some more information: The two interfaces are going to different
>>>> switches, and they are Intel Gigabit nics.
>>>>
>>>> --
>>>> David Lee
>>>>
>>>> (E-Mail Removed) wrote:
>>>>> Is there a way to have two separate network interface cards have some
>>>>> sort of failover redundancy with one ip address (two nics with one ip,
>>>>> say 192.168.1.3, both cards pointing to that, or some implementation
>>>>> of
>>>>> redundancy)?
>>>>>
>>>>> This is on a brand new Windows 2003 Enterprise Server Edition.
>>>>
>>>
>>>
>>
>>
>
>