469,127 Members | 1,440 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,127 developers. It's quick & easy.

mssql8 AND mssql 2005

I have both 8 and 2005 installed on a windows 2003 server. However from a remote machine I can only see the 2005 instance. Is there a configuration I have missed or is this not possible?
Sep 13 '07 #1
13 1446
davef
98
Are you using SQL Server 2005 Management Studio to connect to a remote database engine? If so, you may wanna try to select <Browse for more...> option from the Server Name dropdown list and then switch to the Network Servers tab. Let me know how you're getting along.
Sep 13 '07 #2
I can see both instances on the Windows 2003 system and can connect to the v8 thru sql server management as you suggest. My issue is a remote machine with only 8's client cannot connect to the mssql v8 instance.
Sep 13 '07 #3
davef
98
Are you getting any error at all? Try to quickly create a .udl file on the remote machine to see if you could make and test a connection to the server.
Sep 13 '07 #4
I get a server not found message.
Sep 13 '07 #5
davef
98
How did you name your 2000 and 2005 instances on the same box?
Sep 13 '07 #6
2005 = server
other is server\server2003
Sep 13 '07 #7
davef
98
And server\server2003 is not visible from 2000 client, right?
Sep 13 '07 #8
Yes. I wonder if I should name it something else maybe it doesn;t like that name. Maybe OldSQL?
Sep 13 '07 #9
davef
98
Yes. I wonder if I should name it something else maybe it doesn;t like that name. Maybe OldSQL?
Try to name it without slash. I doubt though it'll help. I once experienced a very funny problem with my replication whereby the distributor wouldn't connect to the subscriber. I had to enable Naming Pipes on the subscriber via the SQL config console to fix it. Just a thought.
Sep 13 '07 #10
Tried the name pipes didn;t help. Don;t think I can rename it as the machine is called server which is where that comes from shoulf just be server2003 to connect. Going to move this db to a different machine and not worry about it anymore. Chalk it up to a 2005 quirk I think.
Sep 13 '07 #11
Thanx for your help anyway.
Sep 13 '07 #12
davef
98
Good luck to you. Sorry couldn't help you better. Try to search in MSDN troubleshooting articles.
Sep 13 '07 #13
I had to change the port for the mssql8 version to get it to work.
Sep 21 '07 #14

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

7 posts views Thread by mj | last post: by
1 post views Thread by theintrepidfox | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by Mortomer39 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.