1 / 63

70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration. Chapter 12 Troubleshooting Connectivity. Objectives. Understand the tools available for troubleshooting transport issues and when they should be used Understand nondelivery reports and NDR codes

reed
Download Presentation

70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration Chapter 12 Troubleshooting Connectivity

  2. Objectives • Understand the tools available for troubleshooting transport issues and when they should be used • Understand nondelivery reports and NDR codes • Understand the types of issues that can contribute to transport errors 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  3. Troubleshooting Connectivity • Message flow issues range from simple to complex • Typical issue: improper configuration of e-mail systems • Resolved by verifying configuration settings • Complex issues require use of diagnostic tools • Nondelivery reports (NDRs): provide data used in analysis of message flow issues 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  4. Tools for Troubleshooting • Tools for troubleshooting e-mail issues: • Windows Server 2003 event log • SMTP protocol log • SMTP and X.400 QueueViewer • Diagnostics logging • Message tracking 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  5. Diagnostics Logging • Diagnostics logging is enabled on the transport server • Use Diagnostics Logging tab of server's Properties dialog box • Impact of increasing logging levels: • Expand content written to application log • More transport-related events can be viewed • More data used in diagnosis of transport issues • Guideline for increasing event-logging level: • Choose category associated with problem type • Example of action taken for problem type • Problems: address resolution or distribution list expansion • Response: increase Categorizer category logging level 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  6. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  7. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  8. Diagnostics Logging (continued) • Four levels of diagnostic logging: • None: default level of diagnostics logging • One entry for events with logging level of zero • Minimum: writes summary entries in the event logs • One entry for events with logging level of 1 or lower • Identifies general nature of problem • Medium: writes summary/detailed entries in event logs • Entries for events with a logging level of 3 or lower • Identifies source of problem and resolution information • Maximum: provides complete audit trail of every action • Entries for event with logging level of five or lower • Server performance affected severely 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  9. Activity 12-1: Configuring Transport Diagnostics Logging • Time Required: 10 to 20 minutes • Objective: Configure diagnostics logging on a server • Description: Configure diagnostics logging separately for each Exchange 2003 server in the organization. Configure diagnostics logging only on the back-end server. Look at how the diagnostics logging is enabled on the MSExchangeTransport service. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  10. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  11. Event Logging • Windows event logs capture events generated by diagnostics logging • Important Windows event logs: • Application log: key events recorded by Exchange Services • System event log: clues to cause of transport problems • Information in Event Properties dialog box • Source: application, service, or component logging event • Category: category of event, also describes related action 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  12. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  13. Event Logging (continued) • Information in Event Properties dialog box (continued) • Event ID: an identifier for the specific event • User: the user account logged on when event occurred • Computer: name of the computer where event occurred • Description: text description of the event • Data: any data or error code output created by the event 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  14. Queue Viewer • Queues: hold messages pending routing and delivery • Queue Viewer: window on queues and message contents • Link queues: • Created if multiple messages bound for one destination • Accessible only when messages are waiting to be routed • Transport queues: SMTP, X.400, MAPI • Transports using MAPI queues • Mail between MAPI clients and heterogeneous messaging systems; e.g., Lotus Notes 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  15. Queue Viewer (continued) • Transports using X.400 queues • Used with MTA • MTA provides addressing and routing information • Relies on X.400 transfer stack (like virtual server) • Transports using SMTP queues • Temporary holding area for internal/external mail • Messages remain in queues until delivery is complete • Deduce problems from queue in which message is stuck 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  16. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  17. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  18. Activity 12-2: Accessing the Queue Viewer • Time Required: 5 to 10 minutes • Objective: Access the Queue Viewer within Exchange System Manager • Description: Access the Queue Viewer within Exchange System Manager on the back-end server 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  19. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  20. Queue Viewer (continued) • Messages do not typically remain in queues • If Queue Viewer updates display, a problem is likely • Information in Queues node of System Manager: • Summary of available queues for selected node • Connection state pivots to critical information • Connection state tells you state of queue • Found in State column or by noting icon used for queue 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  21. Queue Viewer (continued) • Connection state values: • Active: allows message transport out of link Queue • Ready: allows message transport out of transport queue • Scheduled: server awaiting scheduled connection time • Frozen: no messages can be processed for routing • Retry: server waiting retry after connection attempt fails • Remote: server awaiting remote command to dequeue • Warning: either not available or an error occurred 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  22. Queue Viewer (continued) • Troubleshooting connectivity issues: • Freeze messages entering queue • Analyze diagnostic data provided by Queue Viewer 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  23. Queue Viewer (continued) • Information provided by Queue Viewer: • Time oldest message submitted • Time next connection retry • Total message size (KB) • Number of messages • Additional queue information • Remote server connectivity issues • Inability to find destination via DNS • Find Messages selection tool • Specify search criteria: sender, receiver, message state • Specify number of messages to return 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  24. Activity 12-3: Freezing and Unfreezing Queues • Time Required: 5 to 10 minutes • Objective: Freeze a queue using the Queue Viewer • Description: Freeze a queue using the Queue Viewer on the back-end server 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  25. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  26. Activity 12-4: Using Find Within the Queue Viewer • Time Required: 10 to 20 minutes • Objective: Use the Find feature to find messages in Queue Viewer • Description: Use Find feature within the Queue Viewer. Freeze Messages pending submission queue, use Microsoft Outlook to send yourself a message, and then make use of the Find feature within the Queue Viewer to view the message. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  27. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  28. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  29. Protocol Logging • Protocol logging: tracks conversations between virtual servers and external clients or hosts • Use protocol logging to identify SMTP/HTTP issues • Whether client can connect to a specified virtual server • Issues sending/receiving protocol commands or data • Time to send information between client and server • Length of time to establish a connection • Time to end/receive command between server and client • What errors may have occurred (Windows or protocol) • Authentication issues while connecting to the server • Specify tracking properties when enabling logging 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  30. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  31. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  32. Protocol Logging (continued) • Fields of unsupported attributes are marked with "0" (zero) or "-" (dash) • Avoid using protocol logging for connectivity issues • Protocol logging is process and resource intensive • Protocol logging recorded in one of four formats • W3C Extended Log File Format • NCSA Common Log File Format • ODBC Logging • Microsoft IIS Log File Format • Protocol log files written to subdirectory of %SystemRoot%\System32\Logfiles 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  33. Activity 12-5: Enabling Protocol Logging • Time Required: 5 to 10 minutes • Objective: Enable SMTP protocol logging on an Exchange Server 2003 SMTP virtual server • Description: Enable protocol logging on the default SMTP virtual server on your back-end server. You enable protocol logging on each virtual server separately; however, in this activity, you enable protocol logging on the default SMTP virtual server only. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  34. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  35. Message Tracking • Message tracking logs contain message details • Time the message was sent and/or received • Sender and recipient information • Message size • Header information • Individually enable message tracking on each server • Message Tracking Center allows fine-tuned message search • Two options to tailor logging to environment: • Extended logging (bridgehead servers) • Standard logging (mailbox servers) 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  36. Activity 12-6: Enabling Message Tracking • Time Required: 10 to 20 minutes • Objective: Enable message tracking on an Exchange 2003 server • Description: Enable message tracking on your front-end server. On servers that process large quantities of mail, the tracking logs grow quickly, so you must ensure you have enough space in place to handle the anticipated volumes. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  37. Message Tracking (continued) • Message log files take same form as protocol log files • Log files written as tab-delimited text • Log files header records three elements: • Information identifying file as a message tracking log file • Version of Exchange System Attendant that created file • Tab-delimited list of fields contained in body of log file • Log files may be viewed in a text editor • Log files may be imported into word processors 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  38. Activity 12-7: Using the Message Tracking Center • Time Required: 10 to 20 minutes • Objective: Use the Message Tracking Center in Exchange System Manager • Description: Use the Message Tracking Center in Exchange System Manager to track a message. In this activity, you send a message to yourself, and then track that message using the Message Tracking Center. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  39. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  40. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  41. Message Tracking (continued) • New categories available as part of message history: • Messages categorized and queued for routing • Messages routed and queued for local delivery • Messages routed and queued for remote delivery • Messages queued for categorization • Messages queued for local delivery retry • Messages queued for routing retry • Tracking new information improves troubleshooting process 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  42. WinRoute • WinRoute: an Exchange Server 2003 tool • Extracts current routing information used by Exchange • How WinRoute works: • Connects to Exchange Server 2003 on port 691 • Extracts link state information for organization • Extracted information in the form of GUIDS • GUIDS identify connectors, bridgehead servers, etc. • GUID information matched to Active Directory objects • Presents link state information in a readable format 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  43. Activity 12-8: Using WinRoute • Time Required: 10 to 20 minutes • Objective: Use WinRoute to view information about the current Exchange Server 2003 routing environment • Description: View the current Exchange Server 2003 routing information through WinRoute. You learn how to use the utility and the information within it. First, download and install the tool on your back-end server in C:\Temp\WinRoute. To download WinRoute, visit the URL: http://www.microsoft.com/exchange/ 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  44. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  45. WinRoute (continued) • Interface contains three windows • Middle pane is most useful for routing issues • Contains all address spaces known to server • Contains associated costs, restrictions, connector source routing group, administrative group • Investigating routing issues through middle pane • Identify connector used to transport message • Match recipient's address to connector address • Identify costs if more than 1 connector delivers message • Clarify which route the message will take (lowest cost) • Cost not an issue if connectors share same address space 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  46. WinRoute (continued) • Top (tree view) pane in WinRoute interface • Hierarchical representation of organization routing table • Organization in top pane broken into two nodes • General Info node • Routing engine version • Digest number • Administrative Groups nodes • Include routing groups (with connector information) • Bottom (raw routing data table pane) in WinRoute • Contains information in format used by Exchange • Presented for information purposes only 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  47. Telnet • Telnet: terminal emulation program • Telnet troubleshooting capabilities: • Verifies if SMTP is installed and configured properly • Directly type SMTP commands to deliver messages • Verifies that server is available over the Internet • Resolves issues with connectivity behind firewalls • Resolves issues regarding mail flow 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  48. Activity 12-9: Using Telnet to Test SMTP Connectivity • Time Required: 10 to 20 minutes • Objective: Use Telnet to test connectivity with a remote server • Description: Use the Telnet utility to connect to your Exchange 2003 server to test that you can send an SMTP message to a recipient within your Exchange Server 2003 organization. This activity tests SMTP connectivity between the two computers within your workgroup. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  49. Nondelivery Reports • Delivery status notification (DSN): reports mail delivery problems • DSNs divided into three categories: • Messages indicating success • Messages indicating a persistent, transient failure • Messages indicating a permanent failure • Last two DSNs are known as nondelivery reports (NDRs) • They both indicate some kind of failure • Example of NDR: destination server not found in DNS 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

  50. 70-284 MCSE Guide to Microsoft Exchange Server 2003 Administration

More Related