At the moment I have no idea if this problem is caused by a DOS to our win2000 box or
is only a bug triggered by some client application that connects to the sql server.

However this is what it happens:
- client applications connected to the sql server stop working giving a timeout runtime
error or freeze if CommandTimeout property is set to 0 in the ADODB.Connection object
of the client apps.
- no other clients can connect to the sql server.

It is possible to login from remote to the server via terminal service and all seems to be
normal, sql server working, there is no strange disk activity, memory usage or other
resource leaks.

The only way to solve this block is to log in and log off on physical console! I'm getting
crazy! How can be possible that services that run in background are influenced from an
interactive login on console?

I've made several analyses using a packet sniffer on the lan and doing sql traces
running sql profiler and it seems to be all ok but never happend this problem during
these analyses!

Thank you in advance for any help.
--
Gianni Arru
gianni (at) comi (dot) it [email concealed]

------------------------------------------------------------------------
---
------------------------------------------------------------------------
---

[ reply ]