Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 No ODBC Connection to SQL 2008

Author  Topic 

Johan1974
Starting Member

4 Posts

Posted - 2010-10-20 : 10:37:51
Hello,

I am trying to make an odbc connection from a Windows XP pro Station to a Windows 2008 R2 Server with SQL 2008. When i do a command on the server "SQLCMD -L" i can see the server and the server instance of the SQL server so like:

<SERVERNAME>
<SERVERNAME>\SQLEXPRESS

Within the Server i can also make perfectly all odbc connections i want.

Coming to the client, when i do there a command "SQLCMD -L"i only get to see the servername

<SERVERNAME>

But bot the instance. When i still try to make a connection to thsi server with an odbc connection i get a message like "Sql server does not exist or acces is denied" SQl server error 10060

How can i make the instance available to the client?


Johan





jeffw8713
Aged Yak Warrior

819 Posts

Posted - 2010-10-20 : 16:29:06
Is the SQL Browser service running on the server? If not, you can either start that service or you can find the port assigned to the Express Edition and reference the port.

Also, using the Surface Area configuration manager - verify that you have enabled remote connections to the Express instance.

Jeff
Go to Top of Page

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2010-10-20 : 18:29:53
No such thing as Surface Area Configuration tool in SQL 2008.

Enable remote connections with sp_configure or in the GUI (SSMS).

What does your connection string look like?
Go to Top of Page

Johan1974
Starting Member

4 Posts

Posted - 2010-10-21 : 01:34:25
ss
Go to Top of Page

jeffw8713
Aged Yak Warrior

819 Posts

Posted - 2010-10-21 : 15:49:58
Sorry - for some reason I thought this was for 2005.
Go to Top of Page

Johan1974
Starting Member

4 Posts

Posted - 2010-10-24 : 04:14:13
Hello,

I found the answer:

The "Ip ALL" property of the SQLEXPRESS ipadresses was set to TCP Dynamic Ports. After setting this to a fixed ipadres the problem was solved.
Go to Top of Page
   

- Advertisement -