I have a host which stops responding to ping temporarily. But after several seconds or minutes, it continues responding. I would not like to get notifications on these temporary failures. How can the program check the host several times with a delay and then notify me about the failure if all the attempts are failed?
A: Turn on background pinging and checkmark needed monitoring methods (ICMP ping and/or TCP port checking). Then add alerts for servers or hosts of your choice. To do this please click the device and select "Monitoring Settings..." in the context menu (or press Ctrl+F2).
A: If you are the administrator of the network, you can set quite small interval as little as 1-2 minutes (nobody will hurt you for that). But if you are just a regular user we recommend using larger intervals up to 5-10 minutes. Other network users or the system administrator might not like that you ping their computers too often.
IMPORTANT! When checking TCP ports, please keep in mind that Windows XP SP2 and Vista do not allow the program to create more than 10 outgoing unclosed connections within a 10-second period, i.e. some TCP port check failures may be caused by that restriction. For example, errors (inaccurate data or failure to respond) may occur if you've got 100 hosts on the map, and the TCP port check interval is set to less than 100 seconds for each host. Please keep in mind this peculiarity and set the TCP port check interval with a reserve. The above told does not apply to ICMP; pinging is allowed in any rates and amounts.
A: When adding computers to the map, enter the computers' textual addresses (computer's network name or DNS name) in the "Host Address" property. Thus, before the host is checked, its textual address will be converted into an IP address first, and only after that the host will undergo the checks.
When adding computers to the map through scanning network neighborhood, the program will automatically add the computers' names to the address fields, and you won't have to take any extra actions.When adding computers through scanning an IP range, the found hostnames will be converted from IP addresses automatically. On the final step 4 of the Network Map Creation Wizard, choose to use DNS names for host addresses.
Q: I have a host which stops responding to ping temporarily. But after several seconds or minutes, it continues responding. I would not like to get notifications on these temporary failures. How can the program check the host several times with a delay and then notify me about the failure if all the attempts are failed?
A: Yes, this is possible. On the window where you select the monitoring check type (the Step 1 of 3 of the Monitoring Settings Wizard), there are the Attempts and Delay parameters. Raise the Attempts setting and configure a proper Delay to avoid the false alerts.
A: Use the dependent monitoring checks. The dependency is configured on the Step 2 of the Monitoring Settings Wizard. When you click Add, you will be able to select a monitoring check from the list of available checks (your current check being edited will depend on this check). Make the remote hosts checks being dependent on the gateway's check. When the gateway is down, the program will not send notifications on the dependent checks' failures.
A: To configure the scheduled downtime, bring up the "Monitoring settings..." window using the host's context menu and select the "Scheduled downtime" tab. You can also disable and enable checks temporarily using checkboxes near the checks on the "Checks" tab.
A: Please read the WMI troubleshooting guide topic in the help system. Check whether you have a proper Windows version for the remote WMI execution and check the security settings.
A: It seems that the program cannot connect to the remote PC thanks to the authorization problems or some specific security Windows settings. To fix the issue:
1) In the "Service state", "Process existence", "File/folder existence", "File size", "Disk space", "MS SQL Server" (with Windows authorization) check properties, enable the "Authorization required" option and type login and password of a user that has admin rights on the remote computer.
2) When getting the remote information on the "System Information" window, connect to that PC with correct username and password.
3) Check the network access model on the remote PC and switch to "Classic" (regular) it in the Windows security settings if necessary. The remote computer should have the Classic access model selected. If you use a domain, the Classic model will be selected by default (otherwise, the Guest model will be used). How to check or change the access model on your PC:
4) Please also check the following:
5) Disable UAC (User Account Control) on remote computers with Windows 7 or above.
6) Do not use accounts with empty passwords for the remote authorization.
A: The error code 40 means that the data value cannot be gathered or SNMP agent is not started ("SNMP service fails or does not start"). The SNMP service needs to be started on the host or you need to provide the correct SNMP community string (password).
A: Probably, the Windows Firewall is blocking the SNMP protocol on your and on the remote PC.
You can try disabling the Firewall and see if this helps. If the Firewall is blocking SNMP, you can add the SNMP service on the remote PC to the Exceptions
in the Windows Firewall settings. To do this, open the "Control Panel" -> "Windows Firewall". Move to the Exceptions tab. Click "Add Program" -> "Browse...". In the "Filename" field, enter the SNMP service path. For example, it can be C:\WINDOWS\System32\snmp.exe. You can see the correct path in the SNMP service properties.
On your local PC, you should also add our program c:\Program files\10-Strike LANState (Pro)\LANState.exe to the Exception list of your Firewall.
1. In the "E-mail" section of the program settings, configure SMTP server's address (for example, smtp.gmail.com), port (25 by default), login and password for sending e-mails. You also need to provide a subject line and sender's e-mail address. Some ISPs block the TCP port 25 so you cannot send e-mails using the standard SMTP port. In this case, you need to ask your e-mail provider (check their web site) whether they have alternative ports for connecting to their SMTP server (for example, 2525).
2. Select a device on map, bring up the list of network monitoring checks (Ctrl+F2). Select a check, click "Edit". Click "Next>>" until the Step 3 is displayed. Select the "Show message on passed (and/or failed) check" option, and then select the "Send e-mail message" option. Specify the e-mail address.
For sending SMS alerts, you need to do almost the same. Our program sends SMS via e-mail. The most of mobile operators have e-mail-to-SMS gateways. Ask your operator about it or search the Internet for "email SMS gateways".
1. In the "SMS" section of the program settings, configure your operator's SMS gateway's address (for example, sms.mygsmop.com). Enter your country code in the "Prefix" field. Select the "Phone number in e-mail subject" if your operator's gateway requires this.
2. Configure your SMTP settings as described above for sending outgoing e-mails.
3. Select a device on map, bring up the list of network monitoring checks (Ctrl+F2). Select a check, click "Edit". Click "Next>>" until the Step 3 is displayed. Select the "Show message on passed (and/or failed) check" option, and then select the "Send SMS message" option. Specify your mobile phone's number without the country code. It will be added automatically from the program SMS settings (the Prefix).
A: Many free mail services like GMail additionally protect your mailbox from access through external applications, since most often it is through them that attackers hack into accounts. In order to be able to send mail through external applications that you trust, you need to include them in the list of allowed ones or generate a special password for them in your account settings. Each mail service has its own protection algorithm, so you need to find a description in the help about how to add an external application to the list of trusted ones. Here are links to help topics for several popular free email services:
Q:The program fails sending SMS while the correct COM port is specified in settings. How to fix this?
A: When the modem or phone drivers are installed, it is often happens that several virtual COM ports are added to the system. Not all of them allow working with the device. Try to specify another opened COM port. Please also note that not all modems support the AT commands necessary for sending SMS.
Q: The program does not send SMS on alerts but the test messages are sent out fine. Why?
A: Most likely, the issue is caused by the message length (too big). The program supports splitting long messages to several SMS but sometimes it fails to send long messages. If this happens, please try to remove the %T substitution key from the message text. It inserts the detailed information on the failure and can cause the described issues. Create a short text that is clear to you so you would understand what happens when you receive it. This will decrease the number of SMS messages sent, improve the program performance, and minimize amount of money spent on sending SMS.
The program has two settings affecting the message text. The first one is the global message text setting. It affects the format of all alert messages including the screen, log, and email messages. It can be configured in the program settings. We do not recommend using it for solving this issue. The second setting is the local one. You can configure the message text for every alert type for every monitoring check. To do this, click the Message button in the Monitoring Setting Wizard near the necessary type of alert (it is SMS in our case) and enable the "Use custom text" option.
A: Please check the following items:
1) Your and a remote PC you are trying to shutdown should have the "Remote Procedure Call (RPC)" service running.
2) Check that the remote PC is online. Ping the PC or run another check.
3) The NetBios protocol should be enabled in the Firewall on both computers (ports 139 and 445).
4) If everything above is okay, you will probably need to switch the network access model in the Windows security settings on that remote PC to "Guest".
How to check or change the access model on your PC:
Warning! The Guest access model decreases the security level of the system. Please learn more about this issue before enabling the guest access model.
A: The monitoring database and stats are stored in the following folder
C:\ProgramData\10-Strike\LANState (Pro)\ (for Windows Vista, 7, etc.) or
C:\Documents and Settings\All Users\Application Data\10-Strike\LANState (Pro)\ (for Windows XP).
The database folder has the following directory structure:
A: 1. First of all, you need to connect an APC Smart UPS to your local network or to a server via USB, install drivers, run the SNMP service, and specify the Community string.
2. Add a new UPS device in the program and create several checks of the "SNMP" type with the following OIDs:
Specify valid thresholds for the successful check results. For example, the incoming voltage range is 190-250V. In this case, the program will generate an alert and notify you if the incoming voltage is lower than 190V or higher than 250V.
A: Click the main menu "File | Create" (or press Ctrl+N). A new clear network map will be created. Then you need to add hosts to this map. You can do this in the following ways. 1) Press F3 to scan your network neighborhood if you use Microsoft Windows network. This method is quite fast if your network is set up properly. 2) Or click the main menu "Service | Scan IP address range" if you use IP network, or you need to get all the hosts from big or buggy network. 3) You can add needed hosts manually. Right-click the map and select "Add host" from the context menu. Fill in all the necessary parameters and click "OK".
A: This is due to Windows limitations on number of allowed simultaneous outgoing half-open TCP connections in Windows XP SP2(x86,x64)/SP3, 2003 Server SP1(x86)/SP2(x86,x64), Vista without SP(x86,x64) and with SP1(x86,x64). Learn more about this issue...
A: To draw connection lines between the computers, you will need manageable switches with SNMP enabled. When scanning a range of IP addresses, SNMP agents are to be included in the range being scanned, proper community (passwords) are to be specified, and the option "Scan SNMP" is to be selected. LANState must be allowed in your firewall. If you do not have such switches or, if SNMP is disabled, you will have to draw the links manually. This is not as scary and time consuming as it seems, you need to spend only several minutes. For more information, please read: Building Network Diagram. To detect networked printers, NetBios must be properly configured (and allowed in your firewall).
The necessary condition for detecting and drawing the connection links is the MAC address detection for the scanned hosts. If MAC addresses are not detected by the program or the switch MAC address is detected instead of the hosts' addresses, you need to specify or replace them with correct MAC addresses. You can do this manually or import from a file.
If your switch supports the SNMP protocol but you get no links after the scan, please perform the following steps:
1) Please start the Network Scanning Wizard.
2) Add an IP address range your network devices belong to. Please check that the "Search SNMP devices..." option is selected and community strings are correctly entered on the Step 2 of the Scanning Wizard.
3) If you know IP addresses and community strings of your switches, select the "Retrieve a connection table from switches" setting and fill in the list of switches.
4) Check whether your switches appear in the table of found hosts in Step 3, and if they have the "SNMP agent present" option in the corresponding column.
5) Most likely, the program could not get access to the SNMP Bridge MIB (OID .126.96.36.199.188.8.131.52.3.1.1, ...) in your switch. Try to access this data using another SNMP tool (for example, snmpget).
6) Save the scanning results to a file (click the "Report" button and save the results to the Scan_Results_table.csv file) and send it to our technical support staff via e-mail. Do not forget to specify the switch model and manufacturer.
7) If you can get a full dump of the switch's MIB tree, please send it to us and be sure to include the scanning report. We need to analyze the data that your router outputs via SNMP. This will help us to detect the problem and add support for your switch model to our program.
See the next question for more details on getting SNMP dump...
A: First of all, you need to scan your network, find SNMP agents, and prepare the results file named Scan_Results_table.csv as it is described in the previous question.
If you use LANState standard (not Pro), you have to use a 3rd party utility like snmpwalk (please read the next topic). If you use LANState Pro, please perform the following steps:
1) Select the "SNMP | Switch Connection Table" menu item.
2) Click Add and enter the switch's IP address and its Community (Read-only). Click "OK". Then click "Detect".
3) After forming the connection table, click "Save to File". Save the report (Switch_Connection_table.csv).
4) Add your switch to the map manually (click "Host | Add" and enter the switch's IP address).
5) Select the created device and select the "SNMP | SNMP Information" menu item.
6) In the "SNMP read community string" field, enter the community string for accessing the switch.
7) Go to the "Dump" tab and click "Get information".
8) Wait while the table will be filled. Click "Save Report". Save the report (SNMPInfoReport_ipaddr.csv).
Please send all the three files to us: 1) Scan_Results_table.csv, 2) Switch_Connection_table.csv, 3) SNMPInfoReport_ipaddr.csv.
A: How to Save MIB Tree Dumps from Your Switches Using the SNMPWALK.EXE Utility:
The SNMPWALK utility allows you to get a full dump of a SNMP device's MIB tree. The utility operates in the read-only mode and does not make any changes to the device's configuration. You can download SNMPWALK from many Internet sites. For example, you can download SNMPWALK here.
Please do not send MIB dumps made by other utilities to us.
How to save the MIB tree dump using SNMPWALK:
1) Unpack the program's archive to any folder. The archive contains some other SNMP utilities, but we will need the snmpwalk.exe file only.
2) Please run a command shell (cmd.exe) and change your current directory to a folder that contains the SNMPWALK files.
3) Type and run a command in the following format:
snmpwalk -v 1 -One -c comm_string ip_address iso > device_name.txt
comm_string = community string of the switch
ip_address = IP address of the switch
device_name.txt - filename for saving the dump. It would be helpful if you add the switch's model and IP address to the filename.
snmpwalk -v 1 -c public -One 192.168.1.100 iso > cisco-2950_192_168_1_100.txt
Please note (for Cisco switches):
You need to save a separate dump for each VLAN configured on the switch.
For example, a Cisco 3550 switch has three VLANs configured: 1, 5, and 150. You will need to run the snmpwalk command three times.
snmpwalk -v 1 -c public -One 192.168.1.100 iso > cisco-3550_192_168_1_100.txt
snmpwalk -v 1 -c public@5 -One 192.168.1.100 iso > firstname.lastname@example.org
snmpwalk -v 1 -c public@150 -One 192.168.1.100> email@example.com
You can get the "cannot find module" error message during the utility operation. This is because the entire package has not been installed. Please ignore this message.
Please do not forget to use the -One and iso output options.
If the switch supports SNMPv2 and SNMP BULK requests, you can use the following command:
snmpbulkwalk -v 2c -One -c comm_string ip_address iso > snmpWalk_ip_address.txt
snmpbulkwalk -v 2c -One -c public 192.168.1.100 iso > cisco-3550_192_168_1_100.txt
4) All the saved dump files will be stored in the utility's folder. Please pack the saved files into a zip archive and send it to us.
A: The program can draw connection lines between your computers only if the SNMP protocol is enabled on your switches.
1) First, you need to know the IP address range your switch belongs to or the switch's exact IP address.
How to find a switch on your network?
You can find a switch on your network using the snmpscan.exe utility (you can find it on the Internet). This is a free console application. But if the SNMP protocol is disabled on your switch, the program might not help you.
You can also try to search for switches by scanning a wide range of IP addresses with the program and looking at the results table. Find the "Network Adapter's Manufacturer" column and search for famous switch manufacturers (Cisco, HP, DLink, ...).
2) You need to know the community string of the switch (password). By default, it is "public".
3) The SNMP agent should be enabled in your switch.
How to enable the SNMP agent?
If you know IP address of your switch, you can try to open its web interface using a web browser (for example, http://192.168.1.1), enter a correct login and password, and change the SNMP settings. Turn on the SNMP agent on the SNMP settings web page. You can also configure a community string for SNMP access.
A: Your hubs should support the SNMP protocol. You can find this out by searching the Internet by the hub name and model. If you fail to learn about the SNMP support on your hub model, you can send your hub name and model to us and ask about SNMP. Usually, hubs do not support SNMP. You need to have managed switches (Cisco, HP, DLink, Dell, etc.) on your network in order to draw connection links properly.
A: The perfect choice of search parameters depends on your network configuration, availability and functioning of the necessary protocols. In particular, to detect hosts in a local area network with bandwidth of 100 Mbps and higher, sufficient will be 2 ping packets and 100-500 ms response. In the case with TCP ports, it is worth noticing that the greater number of ports you specify on the list, the longer the application will search for hosts in the network. The best way to go around this is to set 2-3 most common ports through which the application can find Windows stations and servers; those include 139, 135, 21 and 80th (NetBIOS, DCOM, FTP, HTTP).
Searching for network printers is a different story. This procedure takes quite a bit of time, and therefore it should not be run if you are SURE that there are no such printers in your network. Otherwise, you would have to wait for the completion of that procedure. The completion will be indicated by the appearance of the network scanning progress bar in the network scanning wizard window. The reason why the procedure is so slow is because it searches for network printers BEFORE launching the primary scanning procedure (which is performed with a large number of threads running simultaneously, unlike with searching for printers).
This is also true for obtaining additional information on hosts through NetBIOS. If the NetBIOS protocol is disabled in your network, no such information can be retrieved, and the application will spend quite a bit of time on that attempt (hence the feeling that the application is “frozen”). Searching for network switches is done in the multithreaded mode. However, if you specify a large number of possible community string values, that will also slow down the scanning process. Hence, if you have set the scanning parameters, and the application is scanning too slow or, even worse, completely "frozen" – go ahead and disable some of those parameters (first, disable network printer search and then disable obtaining additional information through NetBIOS) and try launching the scanning procedure again.
A: Since most hosts in modern networks are protected with by firewalls, pinging those hosts regularly may not work out (if ICMP echo replies are disabled). In such cases, checking by opening a TCP connection to a specific port of the host may help out. For example, it is common for local area networks to set up FTP services on users' computers. In this case, we can check availability of hosts by attempting to connect to their TCP port 21 (FTP), port 139 (NetBios), or port 135 (DCOM).
A: Please read the feature comparison.
A: Right-click on the "My Computer" icon on your desktop and then select "Manage". Then, on the menu at the top, select "Action – Connect to Remote Computer" and select the remote computer, which you want our software to collect data from, and then click OK. If the console has connected successfully, and you can manage the remote computer, you do have the administrator privileges.
A: Please download archive with missing DLL files and unpack the files into your Windows System32 folder.
A: Executable files cannot be run using the web map's context menu in the most of web browsers except Microsoft Internet Explorer. In order to run files using the web map menu in it, you will need configure Internet Explorer's security settings.
A: If you are using Internet Explorer, this can happen due to the enabled compatibility mode. Please disable it and refresh the web page..
A: Please read the help topic about the web UI configuration: Web interface configuration.
A: 1. This can happen if a new MIB file cannot be compiled thanks to the following reasons:
2. Dependent MIB files were not added before the problem MIB file to the program. You can find the list of dependent files in the IMPORTS section in the MIB file.
You can send problem MIB files to our technical support email address so we could understand the reason of the problem and help you.
A: Here's the list of necessary actions to perform:
1. Install the program to a new computer and register it (enter the license key). Close the program.
2. Copy the following folders' content from your old computer to the corresponding folders on the new PC:
3. Copy the map files (*.lsm) if you stored it in a custom location. The default location is c:\Users\user\Documents\10-Strike\LANState Pro\Maps\
4. Run the program on the new PC. If your maps are not loaded automatically, please open the files manually.
The program also stores some settings in the registry but these settings are not principal (window sizes and coordinates, etc.)
A: If your firewall is configured properly, the program will send messages. However, the remote computers may fail to receive and display them. In Service Pack 2 for Windows XP (and also is in Windows Vista), the Messenger service, responsible for receiving and displaying messages sent over the network, is not running by default. If you need to exchange messages, and if you are positive that your security will not suffer because of that, enable that service manually.
Newer versions of Windows do not support the Messenger service at all.
Please send your questions to our support team.