December 15, 2005 at 8:55 am
Hi all! I hope to write in the right forum.
I have a problem with a SQL Server 7 installed on Windows 2003.
When I try to connect to it via query analyzer, I get the famous error 11: general connection error.
If I set "Named pipe" protocol it works, but if I set TCP/IP it doesn't work. Have you any suggestions?
The servers are in the same domain.
Thanks
December 15, 2005 at 9:01 am
Microsoft made significant changes in Windows Server 2003, especially with regards to how the communications work. SQL Server 2000 doesn't work on TCP/IP until you apply SP3. My guess is that TCP/IP isn't usable on Windows Server 2003 for SQL Server 7.0. Is upgrading to SQL Server 2000 or downgrading to Windows 2000 Server not available options?
K. Brian Kelley
@kbriankelley
December 15, 2005 at 10:00 am
I can't downgrade Windows or upgrade SQL for some months.
I have already a Windows 2003 with SQL 7 and from the same remote SQL I can do a linked server without problems. Seem a permission problems, but I don't understand the different behavior
December 15, 2005 at 10:02 am
Are you sure it's not dropping back to Named Pipes to make the connection to the linked server?
K. Brian Kelley
@kbriankelley
December 15, 2005 at 10:13 am
I have setted with cliconfg the default protocol to TCP/IP on both system and on the client of the linked server.
Perhaps I have not understand your message. I speak poor english, sorry.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply