February 10, 2003 at 6:46 am
Has anyone ever run into issues where once we moved to a Windows 2000 operating system, we could no longer connect to our SQL Server 2000 database from a Windows NT client (running SP 6)?
February 10, 2003 at 7:18 am
No, this typically isn't an issue. Check the SQL Server logs (in EM: Management, SQL Server Logs | Current).
You should see a line similar to: SQL Server is listening on TCP, Shared Memory, Named Pipes, except matching whatever network protocols you are using.
Are you able to connect with other clients (Win2K, for instance)?
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
February 10, 2003 at 12:11 pm
Thanks for the reply. I actually found that if I run MDAC 2.5 or less I cannot connect to SQL 2000 on Windows 2000 Server.??? Any ideas why or if you know that this is the case?
February 10, 2003 at 1:40 pm
Are you using a Named Instance (Server\Instance Name)? MDAC 2.5 and below doesn't support them unless you use an alias and manually specify the TCP port.
Also, is your server listening on Named Pipes? I believe MDAC 2.6 changes the client from using Named Pipes as the default and makes it TCP/IP. What you may do is run cliconfg.exe from Start | Run and check the network library on one of the systems that can't connect.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply