USE ILS TO SNIFF OUT USERS WITH DYNAMIC IP ADDRESSES
Many people have trouble locating one another in the world of dynamically assigned IP addresses. They want to use Internet conferencing technology, but they can't keep track of their own IP addresses, much less someone else's. To help solve this problem, Microsoft created Internet Locator Service (ILS), a directory service that lets users register their dynamic IP addresses on a central server so that other users can find the addresses easily. Users who have access to an ILS directory can search for and establish conferencing connections with other users.
ILS stores user information, including IP addresses, in a virtual database on your server. Applications can use HTTP (via Internet Information Server--IIS--Active Server PagesASPscripts), Lightweight Directory Access Protocol (LDAP), and User Location Protocol (ULP) to query and update the ILS database. ILS supports ULP, so NetMeeting 1.0 and Intel Internet Phone applications work with the service, but Microsoft plans to eventually phase out ULP and make LDAP the standard ILS protocol. Figure 1, page 182, shows how the ILS components work together.
If you've used Microsoft NetMeeting, you might be familiar with ILS. You've probably seen the public ILS servers that Microsoft and Four11 provide for connecting with other people. These servers are free, but they're problematic if you're using them to communicate with corporate clients. Public ILS servers typically service thousands of users during peak periods, and some users include obscenities in their user information. This situation doesn't create an ideal environment for professional communications.
In a business, how can you take advantage of ILS? You can do so by running your own ILS server for company employees and clients.
Set Up the Search
Suppose your company wants employees and clients to collaborate through Internet conferencing software. You can set up a standard ILS configuration so that NetMeeting users can find and connect with one another. In addition, you can provide an HTML-based interface so that users can browse a Web page to find out whether a particular person is online. If the person is online, users can click a link to automatically start NetMeeting and connect with that person.
The first step in setting up an ILS server is installing the ILS software (available free from Microsoft at http://www.microsoft.com/netmeeting) on an IIS server. ILS requires at least 16MB of RAM (32MB on Alpha systems) and consumes 25MB of hard disk space. ILS is compatible with IIS 3.0 and IIS 4.0. The basic ILS setup is straightforward; I recommend accepting the default settings.
When you complete the ILS setup, verify that your ILS's HTTP installation works correctly by selecting the Verify Installation link from the ILS start page. (You can connect directly to the installation verification program at http://machinename/ILS/Verify/Verify.htm.) Follow the verification program's steps. If you have trouble performing the verification program's tests, consult the "Troubleshooting Setup" section of the ILS documentation.
When your verification of the HTTP installation executes without error, load NetMeeting 2.x to make sure that the LDAP interface functions correctly. In NetMeeting, select Options from the Tools menu, then select Calling in NetMeeting to change the software's default server setting to the DNS name (preferably) or IP address of your ILS server. If your ILS server processes LDAP requests correctly, you can connect to your server and see yourself listed in the user directory. You might need to refresh the directory for your information to appear.
If you want to support NetMeeting 1.0 or Intel Internet Phone clients, you also need to test your system's ULP support. Open a ULP application and verify that it can connect to the ILS server. If you don't want to support ULP, you can remove support for the protocol by opening the LDAP Service Properties box in IIS's Internet Service Manager (ISM) and clearing the Enable ULP Interface check box on the ILS Server tab, as Screen 1 shows.
You can adjust other LDAP service settings in the ISM, including how long records remain in the ILS database (the Client Time to Live parameter). ILS stores user information in a virtual database in your server's RAM, so to prevent the service from weighing down your server, you must make sure unnecessary entries don't take up database space. When a NetMeeting client connects to an ILS server, the server lets the client know its Client Time to Live parameter, so the client software periodically refreshes its data on the server. ILS purges from the database all clients that don't refresh their entries before their Client Time to Live expires. The default Client Time to Live parameter is 20 minutes. Not only does the Client Time to Live parameter save RAM space, but it is beneficial if the server crashes. Because your clients refresh their database information periodically, they can completely rebuild a lost database within the ILS server's Client Time to Live period. The ISM also lets you adjust the maximum number of records the database can hold.
If you're going to use ILS only internally, you don't need to consider firewall reconfiguration when you set up your ILS server. Just make a DNS name for your ILS server. (For information about adding DNS Resource Records, see Spyros Sakellariadis, "Integrating and Administering DNS," September 1996.)
Prev. page
[1]
2
next page 
