Go Back   TechArena Community > Technical Support > Computer Help > Windows Server > Windows Server Help
Become a Member!
Forgot your username/password?
Tags Active Topics RSS Search Mark Forums Read

Sponsored Links



NLB Misconfigured Error

Windows Server Help


Reply
 
Thread Tools Search this Thread
  #1  
Old 12-05-2005
Randy B
 
Posts: n/a
NLB Misconfigured Error

I have tried setting up NLB between two IIS 6 (W2k3 + SP1) servers on a
second NIC but I keep getting an "Interface misconfigured" error (Primary
cluster IP address(192.168.0.15) not added to TCPIP properties). I have
reviewed all of the documentation available but I am at a loss. Does anyone
have any ideas for me?

Each server has two NICs, the first has a statiic IP with NLB disabled, the
second has a static IP with NLB enabled. When I create a new cluster and add
the second NIC to the cluster for either host I get the error. I have both
added the IP address to the second NIC manually and have had NLBMGR do it
automatically; both methods return the error. I also get a message in the
TCPIP properties window telling me about additional default gateways and
disjoint networks, but I only have one gateway entered.

Thanks for any help...


Reply With Quote
  #2  
Old 12-05-2005
Mike Rosado [MSFT]
 
Posts: n/a
RE: NLB Misconfigured Error

Hi Randy,

These are the steps and documents to ensure that the Network Load Balance
(NLB) is setup correctly.

First, configure NLB on one NIC of the Node. Physical connection of this
NIC is very important. If you are using a Layer 3 switch you will need to
plug the NIC into a hub then uplink the hub to the L3 switch. If you are
using a Layer 2 switch you can plug the NIC directly into a port on the hub.

There is a registry setting called MaskSourceMac that needs to correspond
to the physical connection of the NLB NIC. If you are plugged directly
into the L2 switch you will need to set MSM=1. If you are using a hub that
is up linked to the switch set MSM=0 (see KB193602 below)

If you want traffic to come into the NLB NIC then all subsequent traffic to
go out of the second (non-NLB) NIC, set the binding order and metric of the
NLB NIC to 2. As a result, you will need to set the binding order and
metric for the second (non-NLB) NIC to 1.

The Default Gateway, in a two NIC scenario, is a key setting. If you check
IPCONFIG and you notice that the Default Gateway is set on both NICs and is
a different IP address, this will cause problems. We recommend you pick
one Default Gateway and set it on the second NIC (non-NLB) NIC, leaving the
Default Gateway setting on the NLB NIC blank.

RELATED KNOWLEDGE BASE ARTICLES(S):
291959 "RPC Server Is Unavailable" Error Message When You Connect to NLB
http://support.microsoft.com/?id=291959

812870 Network Load Balancing Cluster Node Does Not Successfully Converge
http://support.microsoft.com/?id=812870

323431 How To Set Up TCP/IP for Network Load Balancing in Windows Server
2003
http://support.microsoft.com/?id=323431

323437 How To Configure Network Load Balancing Parameters in Windows Server
2003
http://support.microsoft.com/?id=323437

193602 Configuration options for WLBS hosts connected to layer 2 switches
http://support.microsoft.com/?id=193602

Network Load Balancing : Configuration Best Practices for Windows 2000 and
Windows Server 2003
http://www.microsoft.com/technet/pro.../technologies/
clustering/nlbbp.mspx

NLB Troubleshooting Overview for Windows? Server 2003
http://www.microsoft.com/downloads/d...999-AEEB-40CF-
867B-AF68742FFFDC&displaylang=en


--------------------
Hope this helps,
Mike Rosado
Windows 2000 MCSE + MCDBA
Microsoft Enterprise Platform Support
Windows NT/2000/2003 Cluster Technologies

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
<http://www.microsoft.com/info/cpyright.htm>

-----Original Message-----
> From: <RandyB@discussions.microsoft.com>
> Subject: NLB Misconfigured Error
> Date: Wed, 11 May 2005 13:18:04 -0700
>
> I have tried setting up NLB between two IIS 6 (W2k3 + SP1) servers on a
> second NIC but I keep getting an "Interface misconfigured" error (Primary
> cluster IP address(192.168.0.15) not added to TCPIP properties). I have
> reviewed all of the documentation available but I am at a loss. Does

anyone
> have any ideas for me?
>
> Each server has two NICs, the first has a statiic IP with NLB disabled,

the
> second has a static IP with NLB enabled. When I create a new cluster and

add
> the second NIC to the cluster for either host I get the error. I have

both
> added the IP address to the second NIC manually and have had NLBMGR do it
> automatically; both methods return the error. I also get a message in

the
> TCPIP properties window telling me about additional default gateways and
> disjoint networks, but I only have one gateway entered.
>
> Thanks for any help...
>
>


Reply With Quote
  #3  
Old 17-05-2005
Randy B
 
Posts: n/a
RE: NLB Misconfigured Error

Thanks for the help. One of the servers had the NLB NIC above the non-NLB in
provider order, but that was the only thing different from what you gave me.
It turns out that for some reason the cluster didn't like the IP address I
was using. I was doing this:

192.168.0.13 Srv1 LAN1 non-NLB
192.168.0.14 Srv2 LAN1 non-NLB
192.168.0.15 Cluster
192.168.0.16 Srv1 LAN2 NLB dedicated
192.168.0.17 Srv2 LAN2 NLB dedicated

I moved the cluster address to 192.168.0.20 and they converged immediately.
I don't know why, there is nothing on 15. Go figure. If you have a good
explanation for why this was so I would be interested to hear it.

Thanks again,
Randy

"Mike Rosado [MSFT]" wrote:

> Hi Randy,
>
> These are the steps and documents to ensure that the Network Load Balance
> (NLB) is setup correctly.
>
> First, configure NLB on one NIC of the Node. Physical connection of this
> NIC is very important. If you are using a Layer 3 switch you will need to
> plug the NIC into a hub then uplink the hub to the L3 switch. If you are
> using a Layer 2 switch you can plug the NIC directly into a port on the hub.
>
> There is a registry setting called MaskSourceMac that needs to correspond
> to the physical connection of the NLB NIC. If you are plugged directly
> into the L2 switch you will need to set MSM=1. If you are using a hub that
> is up linked to the switch set MSM=0 (see KB193602 below)
>
> If you want traffic to come into the NLB NIC then all subsequent traffic to
> go out of the second (non-NLB) NIC, set the binding order and metric of the
> NLB NIC to 2. As a result, you will need to set the binding order and
> metric for the second (non-NLB) NIC to 1.
>
> The Default Gateway, in a two NIC scenario, is a key setting. If you check
> IPCONFIG and you notice that the Default Gateway is set on both NICs and is
> a different IP address, this will cause problems. We recommend you pick
> one Default Gateway and set it on the second NIC (non-NLB) NIC, leaving the
> Default Gateway setting on the NLB NIC blank.
>
> RELATED KNOWLEDGE BASE ARTICLES(S):
> 291959 "RPC Server Is Unavailable" Error Message When You Connect to NLB
> http://support.microsoft.com/?id=291959
>
> 812870 Network Load Balancing Cluster Node Does Not Successfully Converge
> http://support.microsoft.com/?id=812870
>
> 323431 How To Set Up TCP/IP for Network Load Balancing in Windows Server
> 2003
> http://support.microsoft.com/?id=323431
>
> 323437 How To Configure Network Load Balancing Parameters in Windows Server
> 2003
> http://support.microsoft.com/?id=323437
>
> 193602 Configuration options for WLBS hosts connected to layer 2 switches
> http://support.microsoft.com/?id=193602
>
> Network Load Balancing : Configuration Best Practices for Windows 2000 and
> Windows Server 2003
> http://www.microsoft.com/technet/pro.../technologies/
> clustering/nlbbp.mspx
>
> NLB Troubleshooting Overview for Windows® Server 2003
> http://www.microsoft.com/downloads/d...999-AEEB-40CF-
> 867B-AF68742FFFDC&displaylang=en
>
>
> --------------------
> Hope this helps,
> Mike Rosado
> Windows 2000 MCSE + MCDBA
> Microsoft Enterprise Platform Support
> Windows NT/2000/2003 Cluster Technologies
>
> ====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> <http://www.microsoft.com/info/cpyright.htm>
>
> -----Original Message-----
> > From: <RandyB@discussions.microsoft.com>
> > Subject: NLB Misconfigured Error
> > Date: Wed, 11 May 2005 13:18:04 -0700
> >
> > I have tried setting up NLB between two IIS 6 (W2k3 + SP1) servers on a
> > second NIC but I keep getting an "Interface misconfigured" error (Primary
> > cluster IP address(192.168.0.15) not added to TCPIP properties). I have
> > reviewed all of the documentation available but I am at a loss. Does

> anyone
> > have any ideas for me?
> >
> > Each server has two NICs, the first has a statiic IP with NLB disabled,

> the
> > second has a static IP with NLB enabled. When I create a new cluster and

> add
> > the second NIC to the cluster for either host I get the error. I have

> both
> > added the IP address to the second NIC manually and have had NLBMGR do it
> > automatically; both methods return the error. I also get a message in

> the
> > TCPIP properties window telling me about additional default gateways and
> > disjoint networks, but I only have one gateway entered.
> >
> > Thanks for any help...
> >
> >

>
>

Reply With Quote
Reply

  TechArena Community > Technical Support > Computer Help > Windows Server > Windows Server Help
Tags: ,



Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "NLB Misconfigured Error"
Thread Thread Starter Forum Replies Last Post
error “shmget (lowmem) error: Unknown error 999” on linux -Wamil- Operating Systems 6 12-11-2010 11:37 PM
Misconfigured screen Yaropolk Customize Desktop 2 08-12-2008 05:50 PM
Server Error: 451, Socket Error: 10053, Error Number: 0x800CCC0F Eigenberg Windows XP Support 3 03-06-2008 04:13 PM
Misconfigured AD Miltongomes Active Directory 3 15-12-2006 11:11 AM


All times are GMT +5.5. The time now is 07:41 AM.