Ahmad M. Matar

Ahmad M. Matar's profileAhmad M. MatarBlog

Tools

Help

Blog

August 10

Exchange Server 2000/2003/2007 - Error Code 5.1.4

Problem:

1. When you try to send a message, you receive a non-delivery report (NDR) that includes an "ambiguous recipient" error message or a Simple Mail Transfer Protocol (SMTP) delivery status notification code 5.1.4.

2. You receive the following message when you add a proxy address to a user account:

This e-mail address already exists in this organization. ID no. c10312e7 Microsoft Active Directory - Exchange Extension.

An event ID message similar to one of the the following messages is logged in the Application Event log when you add a proxy address to a user account:

Event ID: 9514
Event Type: Warning
Event Source: MSExchangeIS
Description:
Two objects in the Directory have the same proxy
/DC=COM/DC=[DomainName]/CN=[ContainerName1]/CN=[Object1] and
/DC=COM/DC=[DomainName]/CN=[ContainerName2]/CN=[Object2]

-or-

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID:9549
Description:
An ambiguous SMTP proxy user1@domain.com was found on 0x2 mailboxes in the DS. The store cannot map this SMTP proxy to a unique Mailbox GUID.

Cause:

This issue may occur if another account exists that has the same e-mail address.

Solution:

Use Active Directory Users and Computers MMC

	1. Start Active Directory Users and Computers Microsoft Management Console (MMC).
	2. Right-click the root-level domain, and then click Find.
	3. In the Find box, click Custom Search, click user in the Field box, and then click Proxy Addresses.
	4. Enter a condition and a value to search for, for example, starts with and SMTP:user@.
	5. Click Find Now.

Then Use ADSIEDIT to Remove duplicate Proxy Address.

8:34 AM | Add a comment | Permalink | Blog it | Microsoft Exchange Server

August 01

Microsoft ISA Firewall Service stopped and can't start after enabling integrated NLB

Problem:

After enabling the integrated NLB in ISA server 2006, the Firewall services must be restarted to take effect; so the firewall service will stop and can't start on both ISA servers.

Cause:

1. Network Adapters drivers (NIC on which you enable NLB) are not updated to the latest version.

2. Symantec Antivirus Software.

Solution:

1. Uncheck the Network Load Balancing option from the properties of the network card on each ISA server (if it is checked).

2. Disable Network Load Balancing Settings from ISA server 2006 management console.

3. Run [RemoveAllNLBSettings.cmd] on both ISA servers to clear NLB settings, Stop firewall service, and Start firewall service.

[This tool can be downloaded from this link: http://www.microsoft.com/downloads/details.aspx?familyid=0cfc0231-2000-488f-a879-de00087f7a46&displaylang=en].

4. Uninstall Symantec Antivirus for both ISA servers.

5. Update NIC drivers for both ISA servers.

6. Create integrated NLB on ISA servers.

7. Install Symantec Antivirus on both ISA servers.

6:34 PM | Add a comment | Permalink | Blog it | Microsoft ISA Server 2006

Profile

Occupation

Systems Engineer

Location

Jordan - Amman

MCSE 2003
MCTS: Windows Server 2008 Network Infrastructure, Configuration
MCTS: Windows Server 2008 Application Platform, Configuration
MCTS: Windows Server 2008 Active Directory, Configuration
MCTS: Microsoft Office Sharepoint Server 2007, Configuration
MCTS: Microsoft Exchange Server 2007, Configuration
MCITP: Enterprise Messaging Administrator
Citrix Certified Administrator (CCA v3.0 / CCA V4.0)
Citrix Ceritified Enterprise Administrator (CCEA v3.0)

View profile details