hi Tom ,
I found the board you were talking about and later in his post Sean says the following :
e-mail from Sean House [MS]:
"Well, you're not going to find any more information out there because BDA is unsupported in Server 2003 unless ISA Server 2004 is installed... ISA '04 should release later this year, at which time the BDA configuration will be done seamlessly by ISA for you...
The thread that you refer to below contains all of the information that you need to get BDA working, though keep in mind again that it is NOT supported yet... So, to answer your question, you can ignore this message IFF you get a subsequent message in the event log that says that the BDA configuration is ok... I don't recall the event ID off-hand... Otherwise, it means that your BDA settings are misconfigured...
Use the "wlbs bdateam" command to check the status of your BDA team - make sure that no errors are reported and that the team is "Active"... The meaning of the parameters are as follows:
TeamID - just an identifier to group NICs together... Make sure that the same GUID is used for all NICs on a given machine that should be "cooperating" to provide BDA...
ReverseHash - tells NLB whether to use forward (normal) or reverse hashing on incoming traffic on the given NIC... In order for traffic to flow between two NICs clustered with NLB, one of them must be configured to use forward hashing, while the other uses reverse hashing...
Master - one NIC from each group of "cooperating" NICs must be chosen to be the master... Only one master per team, and the choice is pretty much arbitrary... However, the SAME NIC (from the same cluster) must be designated as such on ALL machines in the cluster... So, in effect, you're choosing a master CLUSTER, not a master INTERFACE..."
And another one:
"BDA will work with some ISA '00 configurations, but not all of them, and
as I mentioned, none of them will be supported by MS... For example, if
your ISA configuration causes connections to be NAT'd in the kernel (not
sure what "mode" this is in ISA), then it simply won't work... In ISA
'04, we've addressed that problem...
In short, if you have it setup, and it seems to work, then go with it...
If you start to see issues, then you'll have to drop back to a single
cluster configuration that is supported by NLB and ISA '00...
So I read that Isa 2K4 will natively support NLB better and also (finally) document NLB.
We will wait for ISA2K4 RTM and use NLB when it's available.
UseISAAddressInPublishing=1 doesn't solve the problem : NLB can't be used even if there's only 1 server in the cluster ( thus preventing packets sending to the wrong node , since there's only 1 node )
The advice from Microsoft is :
Don't mess with NLB coz they don't have it working yet. If you do , you will get problems. ISA 2004 Final will natively support NLB clustering on Windows 2003 and provide the needed documentation to achieve a working ISA2k4/NLB cluster.