Article ID: 245621 - View products that this article applies to.
This article was previously published under Q245621
This article has been archived. It is offered "as is" and will no longer be updated.
When you start NetMeeting clients on computers that are not running Windows 2000 and you try to connect to an Internet Locator Service (ILS) server running on a computer running Windows 2000 Server, the clients may not be able to log on to the ILS server or retrieve a directory listing from the server.
Conversely, when you start the NetMeeting client on a Windows 2000 system and try to connect to an ILS server that is running on an NT 4 Server, you may not be able to log on to the ILS server or retrieve a directory listing from the server.
This issue can occur because the ILS server is using a different port for connections.
To resolve this issue, you can configure the ILS server to use port 389.
NOTE: The following command should not be used on a Windows 2000 domain controller participating in Active Directory replication or on a computer running Exchange server.
To configure the ILS server to use port 389, use the ILSCFG command line utility. At a command prompt, type the following command:
ILSCFG server_name /port desired_portNOTE: Earlier versions of NetMeeting may be able to get a directory listing from the Windows 2000 ILS server by appending :1002 to the server name.
Prior to Windows 2000, an ILS server would use port 389 for NetMeeting clients. When you configure an ILS server on a computer running Windows 2000, the ILS server uses port 1002. NetMeeting clients running on a computer running Windows 2000 is able to connect to this ILS server, but any NetMeeting client running on a computer running Windows NT 4.0, Windows 98, or Windows 95 may not be able to connect to the ILS server.
Windows 2000 domain controllers open port 389 for Active Directory traffic. Exchange Servers open port 389 for Lightweight Directory Access Protocol (LDAP) traffic.