Quantcast
Channel: Exchange Server 2013 - General Discussion forum
Viewing all articles
Browse latest Browse all 4521

A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 46.

$
0
0

Hi everyone!

For start, here is my infrastructure:

1 HAProxy which proxy POP, IMAP, HTTPS connections to CAS.

3 CAS - 2013 CU21 (CAS1.HQ.PHARM.COM, CAS2.HQ.PHARM.COM, MAIL4.HQ.PHARM.COM)

2 MBX - 2013 CU21 (MBOX1.HQ.PHARM.COM, MBOX3.HQ.PHARM.COM)

Few days ago i've noticed that our CAS servers got many errors with code 46. After some surfing, i found that it could be caused by incorrect TLS certificate settings. So i've checked everything at least twice:

1) All servers have wildcard cert installed with name *.pharm.com.

2) Cert assigned to IIS, SMTP, POP and IMAP services on all CAS servers.

3) Cert assigned to "Default Frontend" and "Client Frontend" connectors for all CAS servers with set-receiveconnector command.

Mails are going fine, and we dont have any problems with authorization. I'm running out of ideas about what this errors could be caused by, only guesses:

1) Сould this be due to the fact that the name of main certificate is *.pharm.com, and name of servers *.hq.pharm.com?

2) May this be caused to incorrect settings in Default Frontend and Client Frontend receive connectors?

3) Can this issue be related to mbx?

Please help!






Viewing all articles
Browse latest Browse all 4521

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>