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 |
|
contec
Starting Member
9 Posts |
 Posted - 2007-05-25 : 12:52:27
|
| Hi, having a weird problem.We have a db server with several sql 2000 instances. I can connect to all db instances from most client machines. However recently one client was rebuilt (with XP sp2) and now can only connect to the default instance on the db server.When trying to connect to other instances I get a 'server not found or access denied' error. All instances (including the default instance) are running SQL2000 SP4.Can anyone assist with this? |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-05-25 : 14:03:45
|
| Used correct instance name? Which netlib did you use on client? |
 |
|
|
contec
Starting Member
9 Posts |
Posted - 2007-05-25 : 14:19:34
|
| Yes, instance name is correct - have tried connecting with Enterprise Manager, Query Analyzer, System.Data.SqlClient, and ODBC DSN - TCPIP and Named Pipes are both enabled on the instance.I think it's a problem with the client machine as I can connect with all of the above from all other client machines. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-05-25 : 16:39:46
|
| Tried connect with ip address and port number instead of instance name? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-05-25 : 17:04:09
|
| Add aliases for the named instances on the client machine using Client Network Utility.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
contec
Starting Member
9 Posts |
Posted - 2007-05-25 : 18:03:55
|
| Thanks Tara, that fixed it |
|
|
|
|
|
|
Can't connect to non-default instances