Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/172422

From BetaArchive Wiki
Knowledge Base


Troubleshooting Internet Location Server Connectivity

Article ID: 172422

Article Last Modified on 9/30/2003



APPLIES TO

  • Microsoft Commercial Internet System 1.0 Service Pack 2



This article was previously published under Q172422


SUMMARY

Microsoft NetMeeting connects to the Microsoft Internet Location Server (ILS) via the User Locator Protocol (ULP) from the Ulserver.dll file. Ulserver.dll is placed in the /Scripts virtual folder by default.

MORE INFORMATION

To connect Microsoft NetMeeting to your server, perform the following steps:

  1. Start Microsoft NetMeeting.
  2. On the Tools menu, click Options.
  3. Click the My Information tab.
  4. In the User Location Service name box, type the name of your ILS server, and then click OK.
  5. Go to the Call section of NetMeeting and verify that "Log off from directory service" is listed. If the word "Logon" is displayed, this means that you are not yet logged on. If NetMeeting does not give an error, you are logged on.

    If you get an error message, use the following procedure to determine the cause of the logon error:


    1. Search for Ulserver.dll on your hard disk drive. There should be only one copy, and it should be located in your /Scripts directory (although it can be located anywhere that the WWW server can execute it).
    2. Confirm that the virtual directory containing Ulserver.dll has execute permissions set.
    3. Ensure that the Lightweight Directory Access Protocol (LDAP) service is running and check for any warnings from LDAPSVC in the Windows NT Event Viewer.
    4. Execute the following query from a Web browser: where <Servername> is the name of the Web server with ILS installed, and <Scripts> is the virtual directory containing Ulserver.dll. This should return a Web page listing all users currently logged on to the server specified in the query.


Keywords: KB172422