Troubleshooting Exchange Issues

Cannot create a new mailbox

SYMPTOMS: 1. You successfully create a new mailbox on your Exchange Server, and then the Exchange Recipient Update Service updates the object. However, when you use the alias of the new mailbox to resolve the mailbox in Microsoft Outlook, Outlook cannot resolve the name, and you may receive the an error message that is similar to the following: The name could not be resolved. The name could not be matched to a name in the address list.
2. You create a new user with mailbox. However, the mailbox does not appear when you look for it in the global address list.

CAUSE: This issue may be caused 1) if you specify the incorrect Exchange Server in the domain Recipient Update Service settings; 2) if you specify no Exchange Server at all.

Common Exchange Connectivity Issues
1. Host Name Resolution - make sure DNS is running, and Exchange A and MX records present;
2. Protocol issues - the user has permission; appropriate protocol service are started.
3. Firewall blocks transmission - use telnet to check the status.
For step by step troubleshooting receiving/sending email, visit this page:http://www.howtonetworking.com/server/testsmtp1.htm.


5.5.4 (Non Delivery Reports)
5.5.4 (Non Delivery Reports) are usually an invalid address.
All POP3/IMAP4 clients such as Outlook Express works while MAPI clients such as Outlook doesn't
Cause: POP3/IMAP4 is disabled.
All MAPI clients such as Outlook works while POP3/IMAP4 clients such as Outlook Express doesn't
Cause: MAPI is disabled.
Can't start NNTP and IMAP services under Exchange System Manger
Resolution: start them under Computer Manager.
Event ID 2103 - Global Catalog Servers Not Responding
Symptoms: After you install Exchange 2000/2003 successfully, the Microsoft Exchange System Attendant service may not start, and you may receive the following Event ID: 2103 - All Global Catalog Servers in use are not responding:  There is no Recipient Update Service created in the domain where you installed Exchange 2000 or Exchange 2003.
Cause: This issue occurs because no global catalog server can be found in a domain which has been "domain prepped" by the Exchange 2000/2003 Setup program. For the consultants, refer to case 0304JH.
Exchange Troubleshooting Tools
1. Diagnostics Logging,; 2. vent Viewer; 3. Services Logs; 4. Dump Files; 5. Performance Monitor; 6. Network Monitor; 7. Messaging logs.
No one can send email to ameritech.net
Symptoms: you can receive the mails from ameritech.net and sbcglobal.net while you can receive mails from both companies.
Cause: 1. DNS issue.
2. DNSBL.
For consultants, refer to case 112804GD
The entries under Public Folder are not synchronize
Symptom: after moving the Public Folders from Exchange 2000 to Exchange 2003 server, the users can see the Public Folder but the entries or sub-folders under each folder.
Cause: The Replication under Public Folder Properties is setup as Never Run.
For the consultants, refer to case 111004RL.
You do not have the permission to send on behalf of the specific user
Cause: You haven't grant Send on behalf permission.
For the consultants, refer to case 111004CC
Set limit for message with attachment
To size limits for messages with attachment, you have many options. You can customize the settings for the global settings, organization, a specific connector, a specific virtual server, and an individual user.
For the consultants, refer to 091504EX
Troubleshoot SMTP communication problems.
If you have problems sending email over SMTP, you may test the SMTP connectivity by using Telnet on the sending server to connect to port 25 on the destination server.
The system cannot find the path specified
Symptom: If you look in IIS admin console, you may see red X's on the Exchange folder.
Resolution: Restart the Web service.