Article ID: 256285
This article was previously published under Q256285
This article has been archived. It is offered "as is" and will no longer be updated.
Site Server 3.0 can be configured to act as an Internet Locator Server (ILS) server running on either Microsoft Windows NT 4.0 or Microsoft Windows 2000 Servers. Using Site Server 3.0 as an ILS server allows NetMeeting clients to connect and collaborate. Without specifying a port number, the NetMeeting client and Site Server 3.0 default to listen on port 389, regardless of whether Site Server is installed on Windows NT 4.0 or Windows 2000 Server. Please see the "More Information" section of this article for information on how to configure Site Server 3.0 as an ILS Server.
In Windows 2000 Server, the Site Server ILS Service is a built-in ILS server, to which NetMeeting clients can connect. Unlike Site Server 3.0 configured as an ILS server, the Site Server ILS Service defaults to listen on port 1002. To the administrator, this means that in order for a NetMeeting client to connect to the Site Server ILS Service, the client must either be version 3.01 (which automatically listens on port 1002), or an older version that specifies port 1002.
It is possible to have Site Server configured as an ILS server, and the Site Server ILS Service installed on the same Windows 2000 Server-based computer. However, a NetMeeting client that is earlier than version 3.01 defaults to the ILS Server listening on port 389. A NetMeeting client that is version 3.01 or later defaults to port 1002, and if that ILS server is unavailable, it will rollback to the previous port of 389. This can present some confusion when a client connects to the server name, DNS address, or IP address. Depending on the version of the NetMeeting client, two different users may connect to a different ILS server.
For more information, please see the following Microsoft Web site:
Site Server 3.0 Installation Guide