Microsoft KB Archive/195385

= NetMeeting Client Cannot Connect to the Dynamic Directory =

Article ID: 195385

Article Last Modified on 7/13/2001

-

APPLIES TO


 * Microsoft Site Server 3.0 Standard Edition

-



This article was previously published under Q195385



SYMPTOMS
After you install Site Server, the NetMeeting client cannot connect to the Dynamic Directory.



RESOLUTION
Set the LDAP port to 389 and enable NetMeeting support.



MORE INFORMATION
The best approach to this problem is to create a new Membership instance and set the TCP Port to 389. This port can be specified during the Membership Creation Wizard:
 * 1) In the Site Server Microsoft Management Console (MMC), select the Personalization and Membership (P&M) snap-in.
 * 2) Select New.
 * 3) In the Site Server MMC, select the P&M snap-in.
 * 4) Right-click the LDAP instance.
 * 5) Click the Dynamic Directory tab.
 * 6) Select the "Enable NetMeeting 1.0 Support" to enable it, and then click OK.

NOTE: There is no change on the NetMeeting client itself.

Changing an existing Membership instance:
 * 1) In the Site Server MMC, select the P&M snap-in.
 * 2) Right-click the Membership instance.
 * 3) Change the TCP Port to 389 and click OK.
 * 4) Right-click the LDAP instance.
 * 5) Change the TCP Port to 389.
 * 6) Click the Dynamic Directory tab.
 * 7) Select the "Enable NetMeeting 1.0 Support" to enable it, and then click OK.
 * 8) Right-click the Direct Mailer.
 * 9) Change the TCP Port to 389 and click OK.

The ADS path and Schema Class Object path of the AUO Provider (for example, LDAP://servername:port/o=directoryname/ou=admin/cn=schema/cn=member) using this service must be changed as well to reflect the new port setting.

Keywords: kbprb kbpending KB195385

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.