|
Home > Archive > microsoft.public.sqlserver.server > November 2002 > Timeout Expired Sql2k while connecting
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Timeout Expired Sql2k while connecting
|
|
|
| Configuration:
Win2k Server sp3. SQL Server 2000 sp2. Clients: win98 & win2k pro
Our 5 workstation network has been working fine for over a year.
Suddenly, we are receiving a "timeout expired" error.
On the server, I can connect using Query Analyzer and Enterprose
Manager with no problems. When I use both QA and EM from any of the
clients I get the timeout expired message.
A VB app that is set to wait 10 minutes for a connection will connect
after about a minute. I have read from several posts that I can change
the timeout settings in EM and QA accordingly (have yet to try it).
However, I am sure everyone will agree that waiting a minute to
connect is unacceptable. As I mentioned earlier, all was fine until
today.
Client Network Utility and Server Network Utility have TCP/IP and
Named Pipes listed. The network itself is fine. I can see the server
from all workstations.
One thing that *might* be relevant. We have a DSL connection through a
router connected to the hub. This problem happened intermittently
early last year. When I reset the router & DSL modem back then, the
timeout problem went away. I tried resetting both today but that did
not help. Coincidentally, our internet connection was down all day
today (sending this from another office). Could this be related to my
problem?
Any other suggestions?
Thanks,
Jim
| |
| Ricky Artigas 2002-11-09, 10:23 am |
| Hi, Jim.
Could it be that you were using WINS before and now it's no longer being
used? How about using a hosts file on your problematic client workstations
or using the ip address to connect? Is your DNS working ok?
Is the SQL Server on the same network?
"Jim L" <vbsql2k@hotmail.com> wrote in message
news:143740f2.0211090629.5c6a04d4@posting.google.com...
> Configuration:
> Win2k Server sp3. SQL Server 2000 sp2. Clients: win98 & win2k pro
>
> Our 5 workstation network has been working fine for over a year.
> Suddenly, we are receiving a "timeout expired" error.
>
> On the server, I can connect using Query Analyzer and Enterprose
> Manager with no problems. When I use both QA and EM from any of the
> clients I get the timeout expired message.
>
> A VB app that is set to wait 10 minutes for a connection will connect
> after about a minute. I have read from several posts that I can change
> the timeout settings in EM and QA accordingly (have yet to try it).
> However, I am sure everyone will agree that waiting a minute to
> connect is unacceptable. As I mentioned earlier, all was fine until
> today.
>
> Client Network Utility and Server Network Utility have TCP/IP and
> Named Pipes listed. The network itself is fine. I can see the server
> from all workstations.
>
> One thing that *might* be relevant. We have a DSL connection through a
> router connected to the hub. This problem happened intermittently
> early last year. When I reset the router & DSL modem back then, the
> timeout problem went away. I tried resetting both today but that did
> not help. Coincidentally, our internet connection was down all day
> today (sending this from another office). Could this be related to my
> problem?
>
> Any other suggestions?
>
> Thanks,
>
> Jim
| |
|
| Thanks for the reply Ricky.
Unfortunately I don't know how to answer your questions except for the last
one (SQL Server is on the same network). AFAIK, no one changed any of the
network settings and all other network activity is normal (file/print
sharing, etc.).
FYI, I was able to fix the problem by going into Client Network Utility and
putting named pipes ahead of TCP/IP. EM & QA now log on instantly. However,
my VB app still takes about a minute to load (used to connect quickly).
I'm not sure why reversing the order in CNU fixed my problem. The old
setting has been there for almost 2 years with no problems.
Prior to moving named pipes ahead of TCP/IP, I tried changing timeout
settings in EM & QA. EM logged on after about a minute while QA still timed
out with 120 second timeout setting. My DSL connection is still down in my
area. I am still wondering if there is some sort of connection. I sure would
like to get to the bottom of this.
Thanks again!
Jim
Could it be that you were using WINS before and now it's no longer being
used? How about using a hosts file on your problematic client workstations
or using the ip address to connect? Is your DNS working ok?
Is the SQL Server on the same network?
|
|
|
|
|