What protocols are running on the servers and desktops? Which

network library are you using?

Kent

  Paul Broomfield <[EMAIL PROTECTED]> wrote:

Hello,

Thanks for getting back to me.

 

We’ve actually fixed it.  We had to change to named pipes from TCP/IP, it used to work.  I guess TCP/IP is screwed on the server which is odd as web sites are working fine. Oh well the joys of computers.

 

Thanks again

Paul

 

-----Original Message-----
From: Kent Spencer [mailto:[EMAIL PROTECTED]]
Sent: 23 August 2001 11:44
To: NT System Admin Issues
Subject: Re: SQL Timeouts

 

 

 

One of our servers runs NT 4 and SQL 7.  Our Client machines (Win2k Pro) try to connect to the SQL server either via ODBC (in a VB app) or using Enterprise manager, they keep receiving intermittent Timeout Expired messages.  This didnt happen a week ago, and AFAIK nothing has changed on the server or the client PCs.  Ive tried restarts, SP, Hotfixes, reinstalling client software.

 

The client PCs are made up to Win2kPro SP2, Visual Studio 6 SP5 and SQL 2000 Client Tools

Everything on the network is 100mb Cat 5

 

The odd thing is I installed a fresh copy of Win2k SP1, Visual Studio 6 (no SP) the user access our VB app and never gets a Timeout Expired error. Grrrrrr!.  Therefore I thought ahh perhaps then its SQL thats causing the problems, so I ripped it off my machine but I still get the same error message.

 

I cant see any problems with the server, web sites access the DB fine.

 

Any body have any ideas.

 

Thanks

Paul

http://www.sunbelt-software.com/ntsysadmin_list_charter.htm

 


Do You Yahoo!?
Make international calls for as low as $0.04/minute with Yahoo! Messenger. http://www.sunbelt-software.com/ntsysadmin_list_charter.htm

http://www.sunbelt-software.com/ntsysadmin_list_charter.htm

Reply via email to