SqlConnection.Open Timeout Framework 2.0

Hello Everyone,

I have a problem with SqlConnection class when i try to get a SQL Server 2000 connection, i'm using Ms Framework 2.0 and System.Data.SqlClient namespace, i also have a Windows 2003 Server and i need to use Integrated Security, there is something rare because i use the same code with Framework 1.1 and it works fine.

SqlConnection conexion = new SqlConnection("Initial Catalog=MyBase; Data Source=MyServer; Integrated Security=SSPI");
conexion.Open();

On the client machine i have windows xp sp2 and i signed in.

Should i install a service pack, update or something else

Thanks for any help!


Answer this question

SqlConnection.Open Timeout Framework 2.0

  • Johnny Ashcan

    Hi,

    I am facing a bit more peculiar problem. I am using SQL server 2000 server/client architecture on 2 Windows XP SP2 machines. The client was successfully connecting to the server using sqlclient driver for .net 2.0. It was also possible to connect to server using Query Analyzer from the client. Then I run the "Network setup wizard" on the server. Now the Query analyzer on the client machine can connect to the server but my Net 2.0 app can't connect to the server using sqlclient driver. But it can connect to sql server using OLEDB driver. Since I am using Dataset (*.xsd), it is not posssible to change the driver easily, especially it is quiet a hardwork to change all the parameters manually. I have reinstalled all the software on the server machine including the OS. It has solved the problem. But I am afraid that it will happen again, if the Network setup wizard in run on the server machine. I have successfully repoduced the problem on two other machines. I am badly in need of a solution. Can anybody point me towards a solution Thanks to all anyway...


  • Sammy1971

    Thank's ahmedilyas i disabled the firewall and it worked fine, then i just open the 1433 tcp port, i just wonder why this issue is just for Framework 2.0, is it a kind of bug

    Regards.


  • Daniel Coleman

    it looks ok. Try disabling your firewall temporarily and see what happens. If you havent, what happens if you increase the connection timeout

  • SqlConnection.Open Timeout Framework 2.0