![]() ![]() Both servers use the same SSL SAN certificate which is signed by a trusted public CA and the certificate is valid and assigned to services.Įverything was working fine as far as Exchange is concerned. our internal and external DNS point to the internal and external IPs respectively. We don't have any DNS load balancing set up, so instead each server has its own permanent IP and we point the DNS for to a third IP which we manually move between the servers if we need to perform maintenance on one etc, but otherwise it stays on one server. All of our databases are replicated on both servers and half of them are active on each server. The servers are in a DAG and both have all roles installed. We have two Exchange 2016 servers running CU18. I don't understand why this has happened as everything was working when I made the checkpoint. These problems started after applying a Hyper-V checkpoint which I will explain more below. The errors only seem to affect accounts in databases which are not active on the front end server so there appears to be an issue proxying the users to their mailboxes. We are getting intermittent 503 errors for OWA and ActiveSync with Exchange 2016. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |