• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 375
  • Last Modified:

SQL Server 2005 Connection Problem: Error 26

First, yes, have researched this searching for solutions first. Just about everything found relates to ASP / .NET. This isn't, as far as we can see, an ASP/.NET problem.

Having a problem connecting to a SQL Server 2005 (not Express) instance using SQL Server Management Studio from a newly deployed Windows Server 2008 server. The SQL Server 2005 instance is installed on another server in a different domain from the new server. The same instance can be connected from another Windows Server 2003 machine (in the same domain as the new server). Have checked that appropriate ports are open on the firewall between the two domains. Verified that SQL Server has been configured to accept remote connections (otherwise it wouldn't work from the other server, now would it?). This does not involve ASP / .NET, but will in the future as the new machine is to be the home of web sites and applications migrated from the Server 2003 machine that does connect properly. So, if the ports are open, Surface configuration set-up properly (equivalent to the 2003 configuration), the account used for connection on both machines is the same, what is being missed?

Hope we can get this resolved quickly as we need to get these apps/sites migrated off the old hardware (that is no longer under support).

Many thanks in advance!
0
richlich
Asked:
richlich
  • 4
  • 2
  • 2
  • +1
1 Solution
 
Kelvin McDanielSr. Developer/ConsultantCommented:
Can you ping the new server from the old server?

If so, are you sure that the SQL Server Browser service is running on the 2008 machine?
0
 
richlichAuthor Commented:
Yes, the server can be pinged either by FQDN or by IP address.

The 2008 machine is the "client" machine. I thought the browser had to run on the SQL Server machine? Neither the Server 2003 machine (which connects fine) or the Server 2008 machine are running an MS SQL Server browsing service.
0
 
wolfman007Commented:
You only get this error message if you are trying to connect to a SQL Server named instance. You do not get this error connecting to the default instance.

So you probably have all the settings right.

You get this error message because the client stack could not receive SSRP response UDP packet from SQL Browser. It's easy to isolate the issue. Here are the steps:

1) Make sure your server name is correct, e.g., no typo on the name.
2) Make sure your instance name is correct and there is actually such an instance on your target machine. [Update: Some application converts \\ to \. If you are not sure about your application, please try both Server\Instance and Server\\Instance in your connection string]
3) Make sure the server machine is reachable, e.g, DNS can be resolve correctly, you are able to ping the server (not always true).
4) Make sure SQL Browser service is running on the server.
5) If firewall is enabled on the server, you need to put sqlbrowser.exe and/or UDP port 1434 into exception.

Once you are done the steps, you should not see this error message anymore.

from

http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
richlichAuthor Commented:
Been through all of this based on that article. That's one of the first articles I went through.

1. No typos in server name.
2. Instance name is correct.
3. Pingable by FQDN and IP address.
4. SQL Browser service is be running. I can connect to the
SQL Server via Management Studio 2005 from two different machines, one running Vista and one running Server 2003.
5. There is a firewall between the two domains (since one is running an a DMZ). The firewall people tell me there are rules in the firewall that have the ports open. (We do not use the default ports.)

Next?
0
 
rjbookCommented:
When you say you are having a problem connecting, does that mean an error message is being returned or the connection just hangs? If there is an error message being returned please post it to this thread. Also have you checked both the SQL Error Log and the Windows Event Log on the taget machine you are trying to connect to to see if there are any error messages getting written there? I do know that if you are trying to connect to a Named Instance on a remote machine that the Browser Service must be running on that Remote Machine.
0
 
rjbookCommented:
Sorry, just noticed the title of this thread has the Error Number...that is a Network Error, if you do a search in Books Online it has some options try.
0
 
richlichAuthor Commented:
TITLE: Connect to Server
------------------------------

Cannot connect to sqlvs2.sainc.com\externalweb.

------------------------------
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

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

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

OK
------------------------------
0
 
richlichAuthor Commented:
Error when the fqdn is removed (alias is defined):

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

Cannot connect to externalweb.

------------------------------
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: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)

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

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

OK
------------------------------
0
 
wolfman007Commented:
Have a look at the following article, there is a know problem connecting to named instances from Windows Server 2008 under certain circumstances.

FIX: Error message when you connect to a named instance of SQL Server on a client computer that is running Windows Vista or Windows Server 2008: "Specified SQL server not found" or "Error Locating Server/Instance Specified"

http://support.microsoft.com/kb/944390
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now