SQLSever 2012 Management Studio connection failure

Hello I am getting the following error while trying to connect SQL sever remotely via SQLSever Management Studio 2012 ( version 11.0.2100.60). What does this error mean - please help . thx PS


Cannot connect to,3389 .


A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider)

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

Server Name:,3389 Error Number: 64 Severity: 20 State: 0

Program Location:

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error) at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket() at System.Data.SqlClient.TdsParserStateObject.ReadBuffer() at System.Data.SqlClient.TdsParserStateObject.ReadByte() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, TimeoutTimer timeout) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, TimeoutTimer timeout, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server) at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

more ▼

asked Sep 18, 2012 at 06:15 PM in Default

avatar image

10 1 1 1

Are you showing anything in the errorlog of the SQL instance listening on,3389?

I'm actually very curious as to why you have SQL Server listening on the port that is used for Remote Desktop access. Did you move RDP to another port? And why are you passing along a port number at all? How many instances are running on that server, do you have the SQL Browser service running and does the connection succeed when you try to use an instance name rather than a port?

Sep 18, 2012 at 08:37 PM SirSQL

@SirSQL - I think you have answered it and you should change your comment to an answer.

RDP will acknowledge that a connection was made but won't authenticate a login so the symptoms are entirely what you have insinuated.

Sep 20, 2012 at 12:27 PM Blackhawk-17

@PS21 - when you look in the SQL Server errorlog what port does it say it is listening on?

Sep 20, 2012 at 12:28 PM Blackhawk-17
(comments are locked)
10|1200 characters needed characters left

1 answer: sort voted first

There are a couple of reasons that I have found for this. 1) The sql server service is not started at that ip address and listening at that port.....or..... 2) the sql server at that address is not configured for tcpip connections.

more ▼

answered Sep 19, 2012 at 05:50 PM

avatar image

170 2 3

(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.



asked: Sep 18, 2012 at 06:15 PM

Seen: 2712 times

Last Updated: Sep 20, 2012 at 12:28 PM

Copyright 2016 Redgate Software. Privacy Policy