Tim Radney takes us through a connection failure error:
Over the past few weeks, I’ve been contacted by multiple customers experiencing the same frustrating issue. Applications and SSMS sessions that had been rock-solid for years suddenly started throwing errors when connecting over VPN:
- Msg 10054: “An existing connection was forcibly closed by the remote host.”
- “Connection Failure (status code = 3000, [Microsoft][ODBC Driver 17 for SQL Server] The connection is broken and recovery is not possible…”
Read on to learn what’s going on and how you can remediate it.