OS/2 eZine - http://www.os2ezine.com
July 16, 2002
John Bijnens is a CAM/CAM engineer in the KHLim - Dep. IWT which is some kind of technical university in Belgium. He gives training in Pro/E and also writes CNC postprocessors (all development is done on OS/2.)

If you have a comment about the content of this article, please feel free to vent in the OS/2 eZine discussion forums.

There is also a Printer Friendly version of this page.

Previous Article
Next Article

Do you have an OS/2 product or service you'd like to advertise?


How often have you wished there was a convenient way to examine which IP addresses are active in your network and to monitor how long they have been up? There is a very handy software package that allows you to do just that: LanScan. It is freeware written by a Russian programmer Oleg Zhukov.


The latest version is 2.5.1. You can download it from: en.ecomstation.ru/lanscan/. There are two flavors of LanScan, namely LanScan and LanScan4. LanScan is for use on Warp 4 (or higher) and TCP/IP stack 4.1 (or higher.) LanScan4 is for use on Warp 4 (or higher) and TCP/IP stack 4.0.

Installation is very straightforward. After you have downloaded the package you need, depending on what TCP/IP stack you are using, create a directory e.g. \LanScan and unzip the package into this directory. Now start the installation script (install4.cmd if your using TCP/IP 4.0 or install.cmd if you're using TCP/IP 4.1 or higher.) The installation script creates a program object for LanScan on your desktop.


After you have started LanScan you get a window that is similar to the one you see below. It gives you an overview of the IP addresses assigned to the NICs in your computer.

You can configure it to scan using ICMP Echo Request (PING) packets or using ARP requests. The latter can only be used to scan LANs which your computer is connected to. The configuration options can be found under the File menu.

If you select the option Set ARP the following dialog window appears.

[Click to view full size.]

You can now enter the IP-address of one of your NICs. In this example I've entered You can limit the range that will be scanned by specifying an interval (e.g. - If you don't specify an interval, the full range will be scanned. By selecting a specific IP interface you can limit the scan to the selected NICs. If you want, you can have LanScan also try to determine the NetBIOS name that is assigned to a scanned NIC (provided it is configured to run NetBeui.) Now press OK and start the scan by pressing RUN. You now get a window similar to the one below.

LanScan can be fully configured:

  • what timeouts you allow for ARP requests and for PING requests.
  • scan with a specified time interval (the AutoRun interval) and save the results in a log file.


If you have let LanScan run during a certain period, you can create a graphical overview of the time IP addresses were up using an extra software package LanList.

To install LanList unzip it in the LanScan directory and copy all the files from the directory 'Binary' to the directory of LanScan.exe

To run LanList enter the command:

LanListP.cmd C (if you have specified to use the common log.)
LanListP.cmd S (if you have specified to use seperate logs.)

The result of LanList is LanList.htm which when opened in a browser should give you the graphical overview.

I wasn't able to get LanList running. I got a crash every time with an error message saying calloc error.

Previous Article
Next Article

Copyright (C) 2002. All Rights Reserved.