April 2006 - Posts
SQL Server 2005 could fail to bring up due to various causes, there are several great blogs that talk about different reason: http://blogs.msdn.com/sql_protocols/archive/2006/01/10/511330.aspx http://blogs.msdn.com/sql_protocols/archive/2005/10/31/487090.aspx
Read More...
To be able to do this, you need more than one network interface cards on the local machine. You can do the same for one interface too (although it is a hack). The key here is to ask for any loopback traffic (127.0.0.0) to go thru your new route (the gateway)
Read More...
In order to better assist troubleshooting connectivity related issues, the more specific you describe the problems, the faster we can help you out. Please take a few minutes to answer the following questions and post them along with your specific repro
Read More...
The client error messages related to this post are the followings. For MDAC client, [DBNETLIB]General network error. Check your network documentation. [DBNETLIB]ConnectionRead (recv()). For SNAC client, For SNAC client, “ TCP Provider: An existing connection
Read More...
Recently, we in customer scenario, amount of attacks come through making connection to SQL Server 2005 and trying invalid sa login. Under such a situation, SQL Server report error " login failed for user sa [CLIENT..]". It is quite annoying to get a lot
Read More...
In my previous post , I provided some sample C# code that allows you to configure SQL Server connection properties remotely through Windows Management Instrumentation. But WMI can also be used to configure client connection properties on a remote machine.
Read More...
