We have 2 SQL server 2016 servers that are having communication issues when setting up Availability groups and replication. The servers can ping each other and can be connected using a UDL file and an ODBC connection. Port query indicates both server can reach TCP port 1433 and UDP Port 1434. TCP and NP are configured on both servers in SQL Config Mgr. The server will both ping on IPv4 but not on IPv6. Work stations donot appear to be getting any connectivity error from either machine. The error being returned between the servers is:

Cannot connect to Reporting.


An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (Microsoft SQL Server, Error: 64)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476

The specified network name is no longer available

This occurs when trying to set up an AG replica from our Production server to our Reporting server. It also occurs when setting up replication between the 2 servers. Can create distributor on either machine and get like errors regardless of location when trying to initialize the subscription.

  • If you have Windows firewall, or a third-party firewall on the servers, you need to allow port 5022 (default) or whatever port you specify for the replication traffic. I'm not sure what error is returned if that port is blocked... – Tony Hinkle Sep 30 '19 at 20:14

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.