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.
| Author |
Topic |
|
bootsys
Starting Member
1 Post |
 Posted - 2010-08-08 : 14:55:56
|
| Hi All, i am new to the SQL forum and am a newbie sql admin. I need your assistance please.Problem; My clients connect to sql server instance using MSAccess 2003 using ODBC connector. Now the client cannot connect and error is;error 17:microsoft odbc sql server driver dbnetlib sql server does not exist or access deniedHistory; Problem started after installing a new instance of SQL 2005 were there was already an instance of SQL 2000. The 2005 instance connects ok but the original instance no longer connects! I managed to connect by changing the client config and adding a static port which i noticed the sql2000 instance was listening on, 1322. Problem is, i have 80 clients and i dont want to go to each physical pc and set this up, i want the clients to connect automatically to the same port my sql2000 is listening on or default 1433 if possible. The sql2005 instance is listening on dynamic port 2517.How can i resolve this so my clients can connect automatically as per prior to the new instance install?Thanks in advance. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2010-08-08 : 17:07:39
|
| You would need two NICs if you want them to use the same port. You can change the SQL 2000 to use port 1433 via SQL Server Configuration Manager.If the clients are still unable to connect, then we can send a registry change to each of them via a logon script or even as simple as email. Here's an example of the registry file:Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo]"DSQUERY"="DBNETLIB""Server1\Instance1"="DBMSSOCN,Server1,12345""Server1"="DBMSSOCN,Server1,23456"Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
 |
|
|
|
|
|
Client failing to connect to SQL Server Instance