451 4.7.0 Temporary Server error. Please try again later. PRX5 Resolving instances

451 4.7.0 Temporary Server error. Please try again later. PRX5 Resolving instances

It was sunny this morning and the weather was fine! Suddenly I received a call from a client saying that their company's Exchange 2013 Outlook POP3 all did not work properly, pop-up user and password verification box, repeatedly entered the password or directly determined that it does not work.

After the communication learned that there was also a similar failure, the service was pop stopped, the start is good, and recently did not make any changes. After knowing the situation, I telnet to the server. The Exchange service is started normally, and there is nothing unusual.

So I on my own computer quickly configured a pop way, to verify the user name and password here error, repeatedly entered the password or directly determined that there is no role, and the customer described the same, such as

650) this.width=650; "title=" 2.png "style=" height:593px;width:703px; "alt=" Wkiom1r6lzahbrqwaangcort6ew631.jpg "src= "Http://s3.51cto.com/wyfs02/M00/54/2A/wKiom1R6lZahBrqWAANgCoRt6Ew631.jpg" width= "786" height= "657"/>

What do we do next, restart the server? This is the next worst-case, may be restarted under the temporary can solve your problem, but the reason has not been found, back again and again this problem, how to deal with it?

Anyway, first Telnet test, see if there are any errors, error prompts such as: 451 4.7.0 temporary server error. Please try again later. PRX5

The Telnet test format is as follows:

Telnet mail.xxx.com 25

EHLO xxx or is helo,[esmtp way fill ehlo xxx,smtp Way Fill helo, I fill ehlo xxx,xxx any write here ]

Mail from:[email protected][Sender address]

RCPT To:[email protected][recipient address]

data[start to write mail]

Subject:ceshi POP3 send and receive[message header]

Ceshi POP3 send and receive[message body]

. [Message End identifier]

If normal, the message is queued to the sending queue.

exit[send out mail, exit]

650) this.width=650; "title=" 1.png "style=" height:462px;width:702px; "alt=" Wkiol1r6lygs95ytaaja7eup7kq424.jpg "src= "Http://s3.51cto.com/wyfs02/M00/54/28/wKioL1R6lyGS95ytAAJa7EUp7KQ424.jpg" width= "686" height= "469"/>

Step 1, Google under the cause of the error, to find a solution to the problem.

Reference 1,

https://social.technet.microsoft.com/forums/exchange/en-us/fc26dac5-d4e2-49da-903d-361ea8b85388/451-470- Temporary-server-error-please-try-again-later-prx5

I talked to a MS support rep today and they confirmed the same problem, except to resolve it we had to add the local serve R ' s IP to our Hosts file:

192.168.1.5 Server
192.168.1.5 server.domain.local

Restart "Microsoft Frontend Transport" and "Microsoft Exchange Transport" Services

The support agent is stated that he's seen this and a few cases now. All of which is when the Exchange server front and back-ends reside on the same box. Sounds a Exchange bug to me.

Reference 2,

Http://blog.5dmail.net/user1/1/2014414174021.html

"Problem description"
Exchange Server 2013 cannot receive messages that are sent externally. The sender return message shows remote host said:451 4.7.0 temporary server error. Please try again later. PRX2

"Cause analysis"

The problem with Exchange Server 2013 is that the multi-outer role is installed together. including domain control, and Exchange 2013 mailbox and Client Access role, and because the client server hosted in the room, equipped with two network cards, respectively, configure an intranet IP and public IP, the cause of failure mainly occurs in two network cards using different DNS caused.

Step 2, modify the local C:\Windows\System32\drivers\etc\ Hosts file, add local records for the Exchange 2013 server, and save.

650) this.width=650; "title=" 3.png "style=" height:480px;width:702px; "alt=" Wkiol1r6mnbymhmiaamdm3vascq396.jpg "src= "Http://s3.51cto.com/wyfs02/M02/54/28/wKioL1R6mnbymHMIAAMdM3vAsCQ396.jpg" width= "755" height= "489"/>

Step 3, check the Exchange server and the AD domain server, check that the DNS is pointing inward, without pointing to the external records.

Step 4, restart The Microsoft Frontend Transport (Microsoft Exchange Front end Transport) and Microsoft Exchange Transport (Microsoft Exchange transport) "Two services

650) this.width=650; "title=" 4.jpg "style=" HEIGHT:568PX;FLOAT:NONE;WIDTH:704PX; "alt=" Wkiol1r6myajcj0baanarl7ncvw003.jpg "src=" http://s3.51cto.com/wyfs02/M00/54/28/ Wkiol1r6myajcj0baanarl7ncvw003.jpg "width=" "height=" 790 "/>

Step 5, if you restart Microsoft Frontend Transport (Microsoft Exchange Transfer), the transport service stopped, can't get up, restart the server, no, we open the Task Manager, Find the MSExchangeTransport.exe End task, and restart the transport service as well.

650) this.width=650; "title=" 5.jpg "style=" HEIGHT:552PX;FLOAT:NONE;WIDTH:707PX; "alt=" Wkiom1r6mqssmhdxaaolbh9qzhk850.jpg "src=" http://s3.51cto.com/wyfs02/M00/54/2A/ Wkiom1r6mqssmhdxaaolbh9qzhk850.jpg "width=" "height=" 887 "/>

Step 6, after processing, we test to do a telnet test, the specific method refer to the description of the previous section of the article, the message was sent successfully.

650) this.width=650; "title=" 7.jpg "style=" HEIGHT:492PX;FLOAT:NONE;WIDTH:704PX; "alt=" Wkiom1r6nhptkfnbaahvhii2dzu360.jpg "src=" http://s3.51cto.com/wyfs02/M01/54/2A/ Wkiom1r6nhptkfnbaahvhii2dzu360.jpg "width=" 682 "height=" 494 "/>

Step 7, in the open Outlook, has been able to test successfully, send and receive is also normal, no password box prompt, fault resolution. Thank you all the patience of friends to watch, thank you!

650) this.width=650; "title=" 9.png "style=" height:706px;float:none;width:708px; "alt=" Wkiol1r6npvt6vaqaaiokpnxjpk054.jpg "src=" http://s3.51cto.com/wyfs02/M02/54/29/ Wkiol1r6npvt6vaqaaiokpnxjpk054.jpg "width=" 785 "height=" 657 "/>

This article is from the "Zhou Ping Microsoft Technology Exchange Platform" blog, please be sure to keep this source http://yuntcloud.blog.51cto.com/1173839/1584670

451 4.7.0 Temporary Server error. Please try again later. PRX5 Resolving instances