- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- Windows NLB service and teaming
Windows Server 2003
1820129
Members
3075
Online
109619
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2006 01:41 AM
03-06-2006 01:41 AM
Windows NLB service and teaming
is there a recommended best practice when using windows load balancing service on a blade server with 2 nics as it relates to the teaming of the 2 nics? can they/should they be teamed and have the teamed virtual adapter act as the single nic and set it to "multicast" cluster operation mode? or is it better, or maybe necessary, to use one nic for the NLB set in Unicast mode, and use the other nic for communication between nlb cluster nodes (which communication is not possible otherwise when you use unicast mode on a singel nic because all nodes then share the same virtual mac address)?? any info?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2006 10:37 PM
09-13-2006 10:37 PM
Re: Windows NLB service and teaming
A good discussion here:
http://russkaufmann.spaces.live.com/blog/cns!9628511B4C1D269C!407.entry
Keep it simple is a "best practice" when it comes to NLB.
Dedicating one NIC to NLB management is a good idea.
Cheers,
Rune
http://russkaufmann.spaces.live.com/blog/cns!9628511B4C1D269C!407.entry
Keep it simple is a "best practice" when it comes to NLB.
Dedicating one NIC to NLB management is a good idea.
Cheers,
Rune
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP