Microsoft KB Archive/946096

= You cannot use the user principal name (UPN) to connect the Windows-based Live Meeting 2007 client to a meeting that is hosted by Communications Server 2007 =

Article ID: 946096

Article Last Modified on 12/17/2007

-

APPLIES TO


 * Microsoft Office Live Meeting 2007

-



SYMPTOMS
You use the user principal name (UPN) to log on to the Windows-based Microsoft Office Live Meeting 2007 client. When you try to use the Windows-based Live Meeting 2007 client to connect to a meeting that is hosted by Microsoft Office Communications Server 2007, you are repeatedly prompted for the user name and for the password. In this situation, if you enter the Security Accounts Manager (SAM) account name, you are connected to the meeting.

For example, this problem occurs if the Windows-based Live Meeting 2007 client is configured as follows:
 * UPN: @alpineskihouse.com
 * SAM Account Name: fabrikam\ _alpineskihouse
 * Default Active Directory domain: Fabrikam.com



CAUSE
This problem occurs because the UPN does not match the fully qualified domain name (FQDN) of the default Active Directory domain.



RESOLUTION
To resolve this problem, install the Windows-based Live Meeting 2007 client update package that is dated December 17, 2007. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

943085 Description of the Windows-based Live Meeting 2007 client update package: December 17, 2007

Note Before you install this update package, make sure that Communications Server 2007 uses only NTLM authentication.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
This hotfix is included in release 8.0.6362.28 of the Windows-based Live Meeting 2007 client. This release replaces the previous release of the Windows-based Live Meeting 2007 client.

Keywords: kbpubtypekc kbexpertiseinter kbqfe kbfix kbbug KB946096

-

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

© Microsoft Corporation. All rights reserved.