You upgrade the global catalog to Microsoft Windows Server
you use Microsoft Outlook 2000 or an earlier version to resolve aliases
by clicking Check Names
, you receive an error message that
is similar to the following:
The name could not be
resolved. Network problems are preventing connection to the Microsoft Exchange
Server computer. Contact your system administrator if this condition persists.
Alternatively, when you use Outlook 2000 or an earlier version to connect to a server that is running Microsoft Exchange
Server, you receive an error message that is similar to the
Exchange Server is unavailable.
This issue occurs because the Windows Server 2003 security
templates are more secure than the Microsoft Windows 2000 security templates.
To resolve the issue, follow these steps:
- On the global catalog that was upgraded to Windows
Server 2003, click Start, point to All
Programs, point to Administrative Tools, and then
click Domain Controller Security Policy.
- Expand Local Policies, and then click
- Set the policies as listed in the following table.
Collapse this tableExpand this table
|Network access: Allow anonymous SID/Name
|Network access: Do not allow anonymous enumeration of SAM
|Network access: Let Everyone permissions apply to
|Network security: Do not store LAN Manager hash value on
next password change||Disabled|
|Network security: LAN Manager authentication
level||Send LM & NTLM response|
- Close the Domain Controller Security
- Click Start, click Run,
type gpupdate /force, and then click
- On the Exchange server, click Start, click
Run, type services.msc, and then click
- Locate the Microsoft Exchange System
Attendant service, click Restart Service on the toolbar, and then close the Services console.
Article ID: 903295 - Last Review: September 3, 2013 - Revision: 2.0
- Microsoft Exchange Server 2003 Enterprise Edition
- Microsoft Exchange Server 2003 Standard Edition
- Microsoft Exchange 2000 Server Standard Edition
|kbexchdirectory kbprb KB903295|