Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

SQL Alias between client and server Expand / Collapse
Author
Message
Posted Wednesday, July 23, 2014 12:04 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, October 27, 2014 10:59 PM
Points: 1,794, Visits: 777
Hi,

I am trying to set up a client alias to connect to a named instance on another server but for the love of me it wont connect -

TITLE: Connect to Server
------------------------------

Cannot connect to fred.

------------------------------
ADDITIONAL INFORMATION:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

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

------------------------------

The network path was not found

------------------------------
BUTTONS:

OK
------------------------------

I have set up the alias on the server and as expected it works. On the client side I have used the SQL Server Client Network Utility to configure the client side alias but no luck

I am using TCP/IP with a specific port ..

Any ideas would be greatly appreciated.

By the way the SQL is SQL Server 2012 Ent and the O/S is Windows 2012 R2 minshell


Thanks


Hope this helps...

Ford Fairlane
Rock and Roll Detective





Post #1595347
Posted Wednesday, July 23, 2014 1:51 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, November 5, 2014 6:13 PM
Points: 38, Visits: 562
Hi,

Have you been able to connect from the client computer without using the alias? If your client software doesn't support that for some reason, you can use regular telnet with IP and Port to test connectivity. If it works from the DB server but not from the client, it could be a Firewall blocking your connection.


Mika Sutinen, Senior DBA
@SQLFinn on Twitter
Blogging at SQLStarters
Post #1595373
Posted Wednesday, July 23, 2014 2:12 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Friday, October 31, 2014 11:06 AM
Points: 5,430, Visits: 10,108
Is it just this one client that can't connect? Is remote access allowed?

EXEC sp_configure 'remote access'

John
Post #1595377
Posted Wednesday, July 23, 2014 5:22 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, October 27, 2014 10:59 PM
Points: 1,794, Visits: 777
Hi,

So to answer the two questions, yes I can connect from the client machine with out using the alias and yes remote connections has been enabled.

What I am doing is wanting to move some sharepoint databases to another instance and rather than have to redo the sharepoint sites, is create an alias with the old name pointing to the new instance and then leave the config settings as they are.

Thanks



Hope this helps...

Ford Fairlane
Rock and Roll Detective





Post #1595764
Posted Thursday, July 24, 2014 3:53 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Friday, October 31, 2014 11:06 AM
Points: 5,430, Visits: 10,108
Have you tried changing the protocol to TCP/IP in the alias?

John
Post #1595835
Posted Thursday, July 24, 2014 4:57 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, November 5, 2014 6:13 PM
Points: 38, Visits: 562
Hi,

If your client OS is 64-bit you have two cliconfg.exes, one is the 64-bit residing in \Windows\System32 folder and the other one is the 32-bit one in the \Windows\SysWOW64 folder.

If you're running 64-bit OS and just run cliconfg.exe from the Start \ Run, it'll open up the 64-bit one. Try running the one from SysWOW64 folder and adding the alias there.


Mika Sutinen, Senior DBA
@SQLFinn on Twitter
Blogging at SQLStarters
Post #1595850
Posted Thursday, July 24, 2014 8:49 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, October 27, 2014 10:59 PM
Points: 1,794, Visits: 777
The protocol is set to TCP/IP and I have tried using the 32 and 64bit app.

Still get the following:

TITLE: Connect to Server
------------------------------

Cannot connect to fred.

------------------------------
ADDITIONAL INFORMATION:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

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

------------------------------

The network path was not found

------------------------------
BUTTONS:

OK
------------------------------


Hope this helps...

Ford Fairlane
Rock and Roll Detective





Post #1596070
Posted Thursday, July 24, 2014 10:52 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, November 5, 2014 6:13 PM
Points: 38, Visits: 562
Hi,

Error code 53 means: "The network path could not be found". The most common reasons I've seen this occur are:

A) Name resolution failure. This can be tested by adding the server into host file or by creating the alias using the IP instead the server name.
B) Typo in the alias, for example "server/instance" when it should be "server\instance" if you have named instance.




Mika Sutinen, Senior DBA
@SQLFinn on Twitter
Blogging at SQLStarters
Post #1596085
Posted Thursday, July 24, 2014 11:42 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 11:23 PM
Points: 1,280, Visits: 1,761
Can you ping the server IP from the client? Ping the server name?
If you can, then add Telnet (from Windows Features) then telnet ip sqlport, eg. telnet 111.111.111.111 1544. Does it connect (blank cursor) or error?

If error, you have a network or port issue. If no error, it's a problem with the sql alias setup.

Remember to remove telnet afterwards.
Post #1596087
Posted Thursday, July 24, 2014 11:45 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, October 27, 2014 10:59 PM
Points: 1,794, Visits: 777
Hi,

I have tried host name, ip I have copied the connection from a working SSMS connection and still the same network error !!


Hope this helps...

Ford Fairlane
Rock and Roll Detective





Post #1596088
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse