Hi Ron,

Thanks for the reply!

I looked at this setting, however I have user instances turned Off so it is disregarded 🙁

I thought it may have to do with the tcp/ip keep alive feature that is new to 2005 and that perhaps when the database server is "asking" for a reply from the client that maybe that client is not responding due to how it was programmed and how that program is connected. What do you think about that as a possibility? I'd hate for it to be that since that requires a registry change on the client side.

The other worthy mention here is that I have another database on that server and it is connected to by a .net application which does not time out... odd.

Thanks again for your ideas!! I'll keep looking 🙂