Re: iis - cannot find page (cannot find server or dns error)

From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 12/24/04 

Date: Fri, 24 Dec 2004 09:50:27 -0800

Based on your solution, the problem is unlikely to be related to IIS6. My
logic is that if IIS6 was working just fine and then all of a sudden fails
and rebooting the server doesn't help, the problem is VERY unlikely to be
IIS6. I suspect failure in the application itself (stale state stored in
SQL) or networking/DNS that is failing.

Please do the following for troubleshooting.
1. Turn off IE's "Show Friendly HTTP Errors" option and report the actual
error.
2. When you are having problems accessing the website, try using the PUBLIC
IP address of the web server directly from a client machine that is EXTERNAL
to the web server's network. If it works, the problem has nothing to do
with IIS and is likely DNS related.
3. If using IP does not work, then it has nothing to do with IIS and is
likely networking related

My suspicion is that your server's IP is not static, so every once in a
while, the telco changes the server's IP and causes it to be out of sync
with some but not all DNS servers in the world (DNS changes take a while to
propagate).

Can you also clarify whether the 4 client computers are on the same network
as the web server, or are we talking about two different locations? Maybe
you have a local DNS failure phenomenon if everything is local. 

-- 
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"keith58" <keith58@discussions.microsoft.com> wrote in message
news:7051D628-2EFE-4808-AC45-B96D7A53DC40@microsoft.com...
We have an ASP site that runs in IIS 6.0 under Windows 2003 (uses SQLServer
as well). The main users of the site run IE on 4 computers behind a router
which acts as a firewall. The site is very simple on uses only old ASP style
code (i.e. no .net).
The site runs fine for few days then suddenly they get this error (see
subject line). We've tried serveral solutions to get people working again
(re-boot computers, re-start web site, re-start web site service on windows
2003) but the only thing that seems to get the train back on the rails is
re-booting the modem which connects the remote office to the Internet and
waiting about 15-20 minutes.
This is not a dns or internet connection issue. The site still works at
other locations (around the world). The users can still get at other sites
on
the web while our site appears dead. The users can also use ping and tracert
to find our server.
I have not found out what the telco is doing when the modem is re-set but I
think things will point back to IIS 6.0 not liking 4 sessions pounding away
at it through a firewall. We seem to be hitting some kind of threshold in
IIS
6.0
Does anyone have any ideas why this might be happening? Thanks
-- 
Keith