Ticket: UM failed submit mail to HUB

-

 

Troubleshoot: UM voice mails not submitted to Hub Transport

UMService EventID 1082 "The Unified Messaging server was unable to submit messages to a Hub Transport"

Authentication failure

UM Voicemail delivery fails - SMTP error TargetUnknown

on UM

Event Type:    Warning
Event Source:    MSExchange Unified Messaging
Event Category:    Disk
Event ID:    1185
Date:        11/24/2010
Time:        3:22:41 PM
User:        N/A
Computer:    OCS-UM
Description:
The Unified Messaging server was unable to submit a message to Hub Transport server "EXCH-CAS" because the following error occurred: 意外的 SMTP 伺服器回應。預期: 235，實際: 454，整個回應: 454 4.7.0 Temporary authentication failure

 

Event Type:    Error
Event Source:    MSExchange Unified Messaging
Event Category:    Services
Event ID:    1082
Date:        11/24/2010
Time:        3:19:10 PM
User:        N/A
Computer:    OCS-UM
Description:
The Unified Messaging server was unable to submit messages to a Hub Transport server because there is no Hub Transport server available to process the request with UM header file "C:\Program Files\Microsoft\Exchange Server\UnifiedMessaging\voicemail\012d51df-7bd6-4b15-a073-b1a1f9d5249c.txt". Make sure that there is a Hub Transport server located in the same Active Directory site as the UM server. In addition, make sure that the Microsoft Exchange Transport service is started on the Hub Transport server.

.

On HUB

Event Type:    Warning
Event Source:    MSExchangeTransport
Event Category:    SmtpReceive
Event ID:    1035
Date:        11/25/2010
Time:        10:58:26 AM
User:        N/A
Computer:    EXCH-CAS
Description:
Inbound authentication failed with error IllegalMessage for Receive connector Default EXCH-CAS. The authentication mechanism is ExchangeAuth. The source IP address of the client who tried to authenticate to Microsoft Exchange is [192.168.10.154].

 

Setspn.exe 工具

C:\Program Files (x86)\Resource Kit>setspn -L bqt-ca07
Registered ServicePrincipalNames for CN=BQT-CA07,CN=Computers,DC=msft,DC=corp,DC
=com:
    POP/BQT-CA07.msft.corp.com
    POP/BQT-CA07
    exchangeRFR/BQT-CA07
    exchangeRFR/BQT-CA07.msft.corp.com
    exchangeMDB/BQT-CA07
    exchangeMDB/BQT-CA07.msft.corp.com
    SMTP/BQT-CA07.msft.corp.com
    SMTP/BQT-CA07
    WSMAN/BQT-CA07
    WSMAN/BQT-CA07.msft.corp.com
    IMAP/BQT-CA07.msft.corp.com
    IMAP/BQT-CA07
    POP3/BQT-CA07
    POP3/BQT-CA07.msft.corp.com
    IMAP4/BQT-CA07.msft.corp.com
    IMAP4/BQT-CA07
    SmtpSvc/BQT-CA07.msft.corp.com
    HOST/BQT-CA07.msft.corp.com
    SmtpSvc/BQT-CA07
    HOST/BQT-CA07

 

Final root cause

Event Type:    Warning
Event Source:    LSASRV
Event Category:    SPNEGO (Negotiator)
Event ID:    40960
Date:        10/29/2010
Time:        1:00:57 AM
User:        N/A
Computer:    EXCH-CAS
Description:
The Security System detected an authentication error for the server DNS/dc.msft.corp  The failure code from authentication protocol Kerberos was "網域主控站的時間與備份網域控制站或成員伺服器上的時間相差太大。
(0xc0000133)".

EXPS EXCHANGEAUTH GSSAPI NTLM

這是 Exchange 2007 的新增參數。這是在 X-ANONYMOUSTLS 之後宣告的預設接收連接器服務延伸。

X-EXPS GSSAPI NTLM LOGIN、X-EXPS=LOGIN

X-EXPS 命令是 Exchange 的專屬命令。此命令與 AUTH 類似，因為它會指定執行 Exchange 2007、Exchange 2003 與 Exchange 2000 的伺服器在進行驗證時可使用的方法，如下所示：

GSSAPI   一種代表一般安全性服務應用軟體程式設計介面，並且可讓使用者透過 Kerberos 進行驗證的方法。

NTLM   一種代表 Windows NT 與 LAN Manager，並且可讓使用者透過 Windows NT 挑戰/回應通訊協定進行驗證的方法。

LOGIN   一種代表 AUTH LOGIN 的方法，此為使用 Base-64 編碼之使用者名稱與密碼的純文字驗證方法。

,27,,>,250-exch-cas.msft.corp Hello [192.168.10.154],
,28,,>,250-SIZE,
,29,,>,250-PIPELINING,
,30,,>,250-DSN,
,31,,>,250-ENHANCEDSTATUSCODES,
,32,,>,250-AUTH NTLM,
,33,,>,250-X-EXPS EXCHANGEAUTH GSSAPI NTLM,
,34,,>,250-X-EXCHANGEAUTH SHA256,
,35,,>,250-8BITMIME,
,36,,>,250-BINARYMIME,
,37,,>,250-CHUNKING,
,38,,>,250-XEXCH50,
,39,,>,250 XRDST,
,40,,<,X-EXPS EXCHANGEAUTH,
,41,,*,SMTPSubmit SMTPSubmitForMLS SMTPAcceptAnyRecipient SMTPAcceptAuthenticationFlag SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender BypassAntiSpam BypassMessageSizeLimit SMTPSendEXCH50 SMTPAcceptEXCH50 AcceptRoutingHeaders AcceptForestHeaders AcceptOrganizationHeaders SendRoutingHeaders SendForestHeaders SendOrganizationHeaders SendAs,Set Session Permissions

,42,,*,CDE\OCS-UM$,authenticated
,43,,>,235 <authentication response>,
,44,,<,MAIL FROM: MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@msft.corp,
,45,,*,08CD45909F8ED06C;2010-11-25T05:57:22.812Z;1,receiving message
,46,,>,250 2.1.0 Sender OK,
,47,,<,RCPT TO: carol.lee@msft.corp,
,48,,>,250 2.1.5 Recipient OK,

,26,,<,EHLO OCS-UM.msft.corp,
,27,,>,250-exch-cas.msft.corp Hello [192.168.10.154],
,28,,>,250-SIZE,
,29,,>,250-PIPELINING,
,30,,>,250-DSN,
,31,,>,250-ENHANCEDSTATUSCODES,
,32,,>,250-AUTH NTLM,
,33,,>,250-X-EXPS EXCHANGEAUTH GSSAPI NTLM,
,34,,>,250-X-EXCHANGEAUTH SHA256,
,35,,>,250-8BITMIME,
,36,,>,250-BINARYMIME,
,37,,>,250-CHUNKING,
,38,,>,250-XEXCH50,
,39,,>,250 XRDST,
,40,,<,X-EXPS EXCHANGEAUTH,
,41,,*,,Inbound ExchangeAuth negotiation failed because of IllegalMessage
,42,>,454 4.7.0 Temporary authentication failure,

Comments

Post a Comment

Popular posts from this blog

E15 CU3–Update Failed–AD replicated Exceeded the tombstone lifetime.

-
Image
  Exchange 2013 CU3 The naming context is in the process of being removed or is not replicated http://technet.microsoft.com/en-us/library/replication-error-8452-the-naming-context-is-in-the-process-of-being-removed-or-is-not-replicated-from-the-specified-server(v=ws.10).aspx   C:\> REPADMIN /SHOWREPS Root\RDC01 DSA Options: IS_GC Site Options: (none) DSA object GUID: f1694974-47c4-4555-a214-db3c86854aeb DSA invocationID: f1694974-47c4-4555-a214-db3c86854aeb ==== INBOUND NEIGHBORS ====================================== CN=Schema,CN=Configuration,DC=lab7,DC=root     TW\AD02 via RPC         DSA object GUID: bfcc1053-e1da-46fd-8b9d-179c79921331         Last attempt @ 2013-12-19 17:
Read more

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

-
Image
Released: January 2023 Exchange Server Security Updates https://techcommunity.microsoft.com/t5/exchange-team-blog/released-january-2023-exchange-server-security-updates/ba-p/3711808 https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ 1.  Update KB5022143 (Exchange SU) 2. Run latest HealthCherker 3.  PowerShell Serialization Payload Signing https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ Certificate signing of PowerShell serialization payload in Exchange Server https://support.microsoft.com/en-us/topic/certificate-signing-of-powershell-serialization-payload-in-exchange-server-90fbf219-b0dd-4b2c-8a68-9d73b3309eb1 4.  MonitorExchangeAuthCertificate    https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/ 5.                 New-SettingOverride -Name "EnableSigningVerification" -Component Data -Section EnableSerializationDataSigning -Parameters @("Enabled=true&qu
Read more

E14–Bulk Create Mail Contact & Set-Contact

-
Image
  http://community.office365.com/en-us/w/exchange/579.aspx     Get-Contact | Export-Csv c:\temp\contact.csv Get-MailContact | Export-Csv c:\temp\Mailcontact.csv   [PS] Import-Csv .\Contact_Source.csv | % {New-MailContact -Name $_.Name -DisplayName $_.DisplayName -ExternalEmailAddress $_.ExternalEmailAddress -Alias $_.Alias -PrimarySmtpAddress $_.PrimarySMTPAddress -OrganizationalUnit "Contacts" -WhatIf }   [PS] >$Contacts = Import-Csv .\Contact_final.csv [PS] >$Contacts | foreach {Set-Contact $_.Name -Company $_.Company -Department $_.Department -Office $_.Office -Phone $_.Phone }
Read more