1. Timout expired error - TCP/IP connection w/ SQL Server 2000
I just installed the 2000 client tools to connect to a 2K server using
TCP/IP and I am having trouble connecting.
I previously had SQL Server 7.0 client tools installed, and was connecting
to multiple 7.0 servers using TCP/IP just fine using Enterprise Mngr and
Query Analyzer. The need arose to connect to a 2K server, so I installed
the 2K client tools, since the 7.0 EM would not work with a 2K database
(although QA worked with the 2K server just fine). So I installed the 2K
client tools, and now I can't connect using EM or QA, due to the timeout
expired error. What happenned with that 2K install to cause this?
In the past, when it worked, I used the IP address as the server name, and I
used SQL Server Login to authenticate.
To troubleshoot, I've tried resetting the timeout value, I've triple-checked
the Client Configuration Utility to make sure it is set to TCP/IP, and I've
tried creating an alias. I've also tried it on three different machines,
Win98, Win2K Pro, and NT 4.0, and all have the same problem.
I'm at my wit's end, please help : )
Thank you!
2. How to check existing DSN and how to build a DSN?
3. [ODBC SQL Server Driver] Timout expired
4. NLS English server from japanese client
5. Text manager cannot continue with current statement
6. ODBC--remote query timout expired
7. Free SPAM Program
8. Timout expired, from within SQLserver enterprice manager
9. Help: SQL Timout Expired
10. 2147217871 Timout expired error
11. Timout Expired on Recordset Open
12. SqlServer - ODBC - Multiple connections cause Connection is busy and Timeout expired