When running long term queries or stored procs (batches or reports) on SQL server 2000 using ADO.NET you definitely want to change the SqlCommand.CommandTimeout. As a good developer you really don’t know how long the query is going to run, so you think: SqlCommand.CommandTimeout = 0
The problem you can get (not always and everywhere) is “General Network Error. Please check your network documentation”. The next step is searching Google and you’ll find some useful links, such as Dev Notes blog and Microsoft support. Resolution: you can call Microsoft for a quick fix, wait for the next version of ADO.NET or set the CommandTimeout to a number you will never going to reach..