timeout expired msg when internet down
-
Hello everyone, we have been having internet problems recently and everytime the internet is down, my users get a "Timeout Expired" message when they try to do anything in the database. This seems odd and it really shouldn't be happening since our network is functioning and we are able to access any computer within the network. Any idea why this happens and how to fix it? Thank you.
-
Sounds like something is trying to access something not on your local network (like that helps a lot).
How are they attempting to do things in the database? Do you have the same problems with EM or QA? -
Yes, the same problem occurs in QA and EM.
-
Are your DNS, WINS, or Active Directory, possibly hosted services. If not, and they are in house, so to speak, check for entries referenced in them for the same name as your server, and verify that the pointers are all within your local network. I think I would also look at the client network utilities, and verify the same thing. With it happening across multiple applications, I would think that you do in fact have a network issue of some sort. You might also do some network investigation by pinging the server from a comand line and seeing what address is returned, and that it is what you expect. I would also check your PDC and BDC for the same types of things.
The only similar experience I have here, was on a hosted system. While the connection to the hosted system was down, authentication requests would time out and not allow connection, yet log-ons and machine to machine communications were not immediately affected as the lease they had was cached and had a lifetime of a day, and the machines handled their own authentication peer to peer. I know that doesn't help much, and wish I had more to offer.
HELLO, all you other guys could jump in at ANY time.........
-
Are your users receiving timeouts only when referencing the SQL server(s), or do they experience similar issues when accessing other network resources as well?
-
I had a FoxPro application that connected to SQL Server 7.0 via ODBC. When my internet connection went down, all the machines except one would access the server and continue working. The one, I determined, always checked the DNS at our ISP before attempting a WINS connection in-house. I finally added the servers and IP addresses to the hosts file c:\winnt\system32\drivers\etc and no longer had the problem.
Michelle
How are they attempting to do things in the database? Do you have the same problems with EM or QA?Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply