3. Prompt connection timeout
If you encounter a third error, it generally means that the client has found the server and can connect.
It is just that the connection time is greater than the allowed time, which leads to an error.
This usually happens when a user runs Enterprise Manager on the Internet to register another server that is also on the Internet.
And when it is a slow connection, the above timeout error may be caused. In some cases, such errors will also be caused due to network problems of the LAN.
To resolve such an error, you can modify the client's connection timeout setting.
By default, the timeout setting for registering another SQL Server through Enterprise Manager is 4 seconds.
The query analyzer is 15 seconds (this is also the reason why there is a high possibility of errors in the enterprise manager).
The specific steps are:
Settings in Enterprise Manager:
1. In the Enterprise Manager, select "Tools" on the menu, and then select "Options"
2. In the pop-up "SQL Server Enterprise Manager Properties" window, click the "Advanced" tab
3. Enter a relatively large number in the box to the right of "Login Timeout (Secs)" under "Connection Settings", such as 20.
Settings in the query analyzer:
Tools -- Options -- Connections -- Set the login timeout to a larger number
4. Most machines can only succeed by using Tcp/ip. Once I found out that using Named Pipes can be used?
This is because in the operating system after WINDOWS 2000, MS configures TCP/IP to solve the security problem of SQL SERVER
As the default connection protocol for SQLSERVER, you can see TCP/IP and NAME PIPE in CLIENT NETWORK UTILITY
order.
You can also:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib]
"ProtocolOrder"=hex(7):74,00,63,00,70,00,00,00,00,00
See the default protocol.
2. How to change Named Pipes, Tcp/ip in the program, and how to write its SQL statement?
You can modify the location of the registry mentioned above:
CLIENT end:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib]
"ProtocolOrder"=hex(7):74,00,63,00,70,00,00,00,00,00
SERVER end:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib]
"ProtocolOrder"=hex(7):74,00,63,00,70,00,00,00,00,00
My problem should belong to the first category, unfortunately, I cannot solve this problem according to the above methods. I use: telnet <server IP address> 1433 Showing that the connection cannot be correct. The method mentioned above cannot solve this problem. Some netizens said that the reason why port 1433 cannot be connected is because Sql Server 2000 is not patched, but after I called sp4, I still cannot connect port 1433 correctly.
My settings are:
<configuration>
<appSettings>
<!--"data source=SASANK;initial catalog=CODER;persist security info=False;user id=sa;workstation id=SASANK;packet size=4096"-->
<add key="ConnectionString" value="server=localhost;Trusted_Connection=false;user id=sa;password=sa;database=sichuan"/>
</appSettings>
<>
I have been looking for the reason for a long time, but it doesn't work.
Later, try to change the database connection item to:
<add key="ConnectionString" value="server=192.168.254.60;Trusted_Connection=false;user id=sa;password=sa;database=sichuan"/> That is to change the Server into the IP address of my machine in the LAN (note that I am debugging in the local machine, and I can't change the server to the machine name, and the connection is not enough). The connection is successful! The problem was solved, but I still don't quite understand what the reason is? Why did I use the telnet command to open port 1433 without success? Hope someone can explain it!
Previous page123Read the full text