Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 35 Source: WLBS

NLB Cluster : Cluster mode cannot be enabled due to parameter errors. All traffic will be passed through to TCP/IP. Restart cluster operations after fixing the problem by running "wlbs reload" followed by "wlbs start".
T787810 says that one should look for additional Network Load Balancing (NLB) events that indicate errors reading from the registry or other configuration problems. After fixing these errors, run nlb reload' followed by 'nlb start'.
As per Microsoft: "This event is probably logged because of incorrectly configured settings that are being read from the registry: in particular, IP addresses, IP subnet masks, or MAC addresses. Until this problem is corrected, this host will remain stopped and will not join the cluster". See MSW2KDB for additional information about this event.
NLB is not configured properly. In my specific case, I had NLB configure on a SBS 2003 Server, this caused exchange and a lot of other services to fail. Removed NLB from the Network connection properties and this solved my problem.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.