Shulou(Shulou.com)06/03 Report--

Hello, everyone. I haven't posted a blog for some time. I'm really sorry. No more superfluous words, let's get back to business.

Two days ago, a client encountered a thorny problem and asked me for help. Now I would like to share this problem and how to deal with it with you. I hope it will be helpful to you.

Environment information: exchange 2010 sp3 (total 2 servers: 1 CAS\ HUB, 1 MBX), no high availability

Problem description: outlook client connection is normal, OWA access is normal, and receiving mail is normal; sending mail (including: sending to yourself, between intranet users, and intranet users to external users) shows that it is sent successfully, there is no queue, and the sender does not receive a bounce, but the recipient does not receive the email.

Process:

Through the phenomenon of the problem, check the rules of exchange 2010 to confirm whether the rules misconfigured by the user have discarded all the emails sent. By checking that there are no rules.

Check the event log of the exchange 2010 frontend server and find an event with an event ID of 1022, as shown below:

3. Use the command Get-TransportConfig | fl InternalSMTPServers to view the internal SMTP server list and find it is empty, as shown below:

4. Add the internal SMTP server address with the following command: set-TransportConfig-InternalSMTPServers 192.168.99.111

5. So far, 1022 of the incidents have been solved, but the problem remains.

Based on the problem phenomenon (all the messages sent through OWA are in the draft box and not in the queue), it is determined that there should be a problem when the exchange 2010 backend MBX submitted the mail to the frontend HUB. By viewing the event log of the exchange 2010 backend server, we found that the event: 1099 error event, as shown below:

Through this event to verify my judgment is correct.

To solve this problem, I added the HUB transport role to the exchange 2010 backend MBX. After the addition, I found that all the emails had been sent out and the recipients had received them. At this point, the problem has been basically solved.

In order to solve this problem completely, I removed and re-added the HUB role on the front end of exchange 2010, and the problem was solved.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.