The problems that you or your Instant Messaging users encounter typically relate to server and channel access. These questions relate to problems you might be experiencing:
The reason installation of Instant Messaging fails is that you must have Domain Administrator rights when you install Instant Messaging on the host computer. These rights give you the ability to modify Active Directory or create and modify registry entries.
Important You may have installed Instant Messaging without Messaging and Collaboration in the Windows 2000 site. The result is an invalid SMTP address, which causes attempts to enable users to fail.
The following conditions can contribute to problems when enabling Windows 2000 users:
When Instant Messaging clients fail to log on to their respective home server, several error codes may be logged within the Internet Information Service (IIS) logging directory:
Instant Messaging logon address does not match the Instant Messaging virtual server's host header.
The user is not Instant Messaging-enabled.
The user exists in a different domain name space.
The user doesn't have an existing Windows 2000 user account.
Instant Messaging virtual server is not created.
The W3svc service is not started.
Network interference is present.
The domain or user policy is not set to use HTTP Digest authentication.
The domain or user policy is not set to use Integrated Windows authentication.
The password or alias is incorrect.
The user's password is incorrect and/or the user must reset the password after applying HTTP Digest authentication for the domain or user.
Note To authenticate its users, Instant Messaging uses the same password as Windows 2000 Server. You reset user passwords from the Active Directory Users and Computers snap-in. For specific instructions, refer to your Windows 2000 online documentation. However, if you are using Integrated Windows authentication, you won't need to apply a domain password policy.
The Instant Messaging virtual server is stopped.