您好,
我以往遇到这个问题是才用这个方法
Well I just solved the issue and it was one of the following (sorry it isn't specific, i just threw all that I could try at this point)
I disabled all filtering on the SMTP instance on the old box - took off IMF, blocklist, eveything. Also disabled max number of connections/recipients.
Under the message delivery options I disabled all such items for message/content filtering that I could and I also unchecked the box that blocks all messages to user not listed in AD.
Restarted the virtual SMTP connector on the old box and it the queue on the new box was empty by the time i ran the ExTA again! PF instances are now clear!
http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/2c90e6dd-c631-447a-904e-bbf97167fe36/
检测方法是:
telnet 对方服务器的 25
检查到对方的网络连接状况
使用命令发送邮件到对方服务器
尝试重启hub 服务,
尝试联系对方看看是否有阻隔
相关方法也请参考:
Intra Org communication between HUB servers is always encrypted
and the “X-AnonymousTLS” command is used. To establish the “X-AnonymousTLS", the
public keys from certificates is used to encrypt the session. .Do
you changed the exchange certificate before the problem happens ?
1. Please enable the logging for IntraOrgConnectorProtocolL
in Server A:
Set-TransportServer –Identity ServerA -IntraOrgConnectorProtocolLoggingLevel
verbose
2. Send a message from server A to server B. Locate the log
at c:\program files\exchange server\v14\transportRoles\logs\Protocollog\smtpsend. Please check if there is any error. Please also zip the log file and send it to me at v-genli{at}microsoft.com.
http://social.technet.microsoft.com/Forums/en-US/exchangesvrsecuremessaginglegacy/thread/6bbea3ef-28b5-4faa-a622-c1abe4a1a3c3/
1) checked the Network card property, it should be
perfect (eg. Primary DNS server)
2) Checked the Network card Binding order, connected
NIC card should be on top.
3) Checked the NDS server , it should be able to resolved
the External remotes domains MX records.
4) Disable
the TCP chimney from CMD
Netsh
int ip set chimney DISABLED
5) Restart the Transport & Mail submission service.
http://social.technet.microsoft.com/forums/en-US/exchangesvrsecuremessaginglegacy/thread/f3065a52-fa86-42e1-acf4-192e570e1f7a