Troubleshooting 'NLB is not configured in this Server' error
The following conditions must be met before you can proceed to troubleshoot WMI nodes:
1. The node should have been successfully added via WMI.
2. WMI should be working properly on the remote server.
Using wbemtest.exe to troubleshoot WMI:
1. Open wbemtest.exe, usually located at C:\Windows\System32\wbem\wbemtest.exe
2. From the Applications Manager server, open wbemtest.exe and click Connect.
3. In the Namespace field enter: \\RemoteServerIpAddress\root\MicrosoftNLBxa
4. Provide the required credentials then Click Connect.
If 'Invalid Namespace' error appears, then NLB feature is not installed in that Server. So, install the NLB feature from Server Manager, then configure the NLB Cluster.
5. Once it is connected, click Query. The Query dialog will appear.
6. Run a Query for specific information:
select Name from MicrosoftNLB_Node
If the test was successful and you're still not able to get the NLB details in the Applications Manager web console, then follow the steps. given below:
1. Navigate to <AppManagerHome>\working\conf\application\scripts\ directory in command prompt and execute the below script and enter administrator credentials:
cscript serverNLB.vbs <RemoteHost> <UserName> <Password> > serverNlb.txt
2. Send the serverNlb.txt file to appmanager-support@manageengine.com along with the support information file of Applications Manager.
How we monitor/get the Microsoft NLB Nodes state and its configuration?
To find Node Status:
We run a serverNlb.vbs in WMI mode to get the state of the corresponding NLB Node.
Here is a sample output:
Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
CONF_NLB_STATE:1008
Here 1008 represents the status code.
Status Codes :
0 REMOTE Node is remote. The StatusCode value cannot be retrieved
1005 STOPPED Cluster operations have stopped on at least one node
1006 CONVERGING The cluster is converging
1007 CONVERGED The cluster has converged successfully
1008 DEFAULT The specified node has converged as the default host
1009 DRAINING One or more nodes are draining
1013 SUSPENDED Cluster operations have been suspended on one or more nodes
To find Configuration information:
The same script will also return the configuration information of the current node.
Here is a sample output:
Here is a sample output:
Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
CONF_NLB_DEDICATED_IP:192.168.140.11
CONF_NLB_SUBNET_MASK:255.255.255.0
CONF_NLB_PRIORITY:1
CONF_NLB_PORTS:3
CONF_NLB_CLUSTER_NAME:com.nlb.test
CONF_NLB_CLUSTER_IP:192.168.140.10
CONF_NLB_CLUSTER_SUBNET_MASK:255.255.255.0
CONF_NLB_CLUSTER_MAC:aa-aa-aa-aa-aa-aa
CONF_NLB_CLUSTER_GUID:AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA
How to check whether Microsoft NLB is configured in my Windows Server?
1. Ensure that your Windows server version is greater than or equal to 2008. Otherwise NLB is not supported.
2. Type wbemtest in the start menu to open the 'Windows Management Instrumentation Tester'. Use the namespace MicrosoftNLB to connect. If you get an Invalid namespace message, then NLB is not configured in your server. If it gets connected,then Applications Manager will automatically collect the required information.
How can I monitor/add Microsoft NLB enabled Server in Applications Manager?
Add the corresponding server as a windows server in Applications Manager in WMI Mode.
New to ADSelfService Plus?
Related Articles
Troubleshooting Bad Request and Internal Server error
Bad Request & Internal Server error When the server of URL cannot understand the request it has received it responds with a Bad request or a malformed syntax error message. If there is an error in processing the request received by the server, it ...Troubleshooting Server error responses
Server error responses Internal Server Error, Bad Gateway, Service Unavailable and Gateway Timeout are the most common server error messages. Seeing any one among these errors generally indicates an issue with the URL's server. Troubleshooting for ...Troubleshooting 'NLB is not configured in this Server' issue
The following conditions must be met before you can proceed to troubleshoot NLB nodes: 1. The node has successfully been added via WMI. 2.WMI is working properly on the remote server. Using wbemtest.exe to troubleshoot WMI: 1. Open wbemtest.exe, ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...How to check whether Microsoft NLB is configured or not in my Windows Server?
First, verify that your Windows server version must be 2008 and above to support NLB. Otherwise, NLB is not supported Then type wbemtest in the start menu to open the 'Windows Management Instrumentation Tester'. Use the namespace 'MicrosoftNLB' to ...