|
Home > Archive > IIS Server > December 2004 > iis - cannot find page (cannot find server or dns error)
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 |
iis - cannot find page (cannot find server or dns error)
|
|
| keith58 2004-12-24, 6:32 pm |
| 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
| |
| David Wang [Msft] 2004-12-24, 6:32 pm |
| 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
| |
|
| Well conveniantly enough, the website has crashed again.
This is a different person writing this response. My father (original
writer, keith58) went out. The server has crashed since he's been gone. Ive
been doing basic troubleshooting. Nothing too different from what I've done
when it has crashed in the past. It's a very strange, reoccuring bug. Site
crashes for only people who use it most. I've checked "bandwidth throttling"
(turned off) and website connections, unlimited. Usually we get the 4
client-computers to restart their modem, wait for about 10-15 minutes and it
starts working again.
OH, on a side note Im not sure if this is related or not, but on the server
we've been getting an application error every minute or so for
"MSExchangeAL". It doesn't seem to hamper anything, so thus not mentioned. If
it was related, though, it would be rather foolish not to mention. I actually
have no idea what Microsoft Exchange does. I don't use it. That is, Im not
aware of using it.
I've done the following, in relation to the latest crashing:
from where the website wasn't working:
- ping ip: works fine
- try website: does NOT work fine
- ip in ie: does NOT work fine
from some random person i was talking to half way across the world on msn
- try website: works fine.
from same network as server
- try website: works fine.
It seems to not work only for the client computers.
> My suspicion is that your server's IP is not static
The IP is static.
> 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.
The 4 client computers are located at the storefrontand and are connected to
one router. It is seperate from the server.
The server is located behind a similar router/firewall system
There are laptops connected to wireless internet behind the server's, and
when website "crashes" it still works from there. This rules out IIS, I
imagine. Also, it works from computers outside of both networks, suggesting
that DNS is ruled out.
Ah they've restarted the modem
I restarted the server..
After about 10 minutes, it seems to be working now.
VERY strange bug.
Thanks
-tyler
| |
| George Hester 2004-12-24, 6:32 pm |
| Save and clear your logs in the Event Viewer on the server and reboot =
the server. All of them. Then post here
any warnings or errors that you have after rebooting. We are likely =
looking for DNS errors\warnings. Or
DHCP. I suspect your network is failing that is used by these 4 =
computers. It could be the router. How do
they get their IP addreess? Have you tried releasing and renewing their =
IP address when the issue occurs?
Exchange is Microsoft's Messaging application for the Enterprise. It is =
what sends e-mail addressed to your
users' Inbox. Works with Microsoft Outlook usually. Post the text of =
the error message you referred to so we
can determine what it is about. As far as I can tell it is saying your =
Exchange service is having a problem.
--=20
George Hester
_________________________________
"tyler" <tyler@discussions.microsoft.com> wrote in message =
news:93C4A7AC-A0D8-4445-9BE2-00B51D007285@microsoft.com...
> Well conveniantly enough, the website has crashed again.
>=20
> This is a different person writing this response. My father (original=20
> writer, keith58) went out. The server has crashed since he's been =
gone. Ive=20
> been doing basic troubleshooting. Nothing too different from what I've =
done=20
> when it has crashed in the past. It's a very strange, reoccuring bug. =
Site=20
> crashes for only people who use it most. I've checked "bandwidth =
throttling"=20
> (turned off) and website connections, unlimited. Usually we get the 4=20
> client-computers to restart their modem, wait for about 10-15 minutes =
and it=20
> starts working again.
> =20
> OH, on a side note Im not sure if this is related or not, but on the =
server=20
> we've been getting an application error every minute or so for=20
> "MSExchangeAL". It doesn't seem to hamper anything, so thus not =
mentioned. If=20
> it was related, though, it would be rather foolish not to mention. I =
actually=20
> have no idea what Microsoft Exchange does. I don't use it. That is, Im =
not=20
> aware of using it.=20
>=20
> I've done the following, in relation to the latest crashing:
>=20
> from where the website wasn't working:
> - ping ip: works fine
> - try website: does NOT work fine
> - ip in ie: does NOT work fine
> from some random person i was talking to half way across the world on =
msn
> - try website: works fine.
> from same network as server
> - try website: works fine.
>=20
> It seems to not work only for the client computers.
>=20
>=20
> The IP is static.
>=20
network[vbcol=seagreen]
Maybe[vbcol=seagreen]
>=20
> The 4 client computers are located at the storefrontand and are =
connected to=20
> one router. It is seperate from the server.
> The server is located behind a similar router/firewall system
> There are laptops connected to wireless internet behind the server's, =
and=20
> when website "crashes" it still works from there. This rules out IIS, =
I=20
> imagine. Also, it works from computers outside of both networks, =
suggesting=20
> that DNS is ruled out.
>=20
> Ah they've restarted the modem
> I restarted the server..
> After about 10 minutes, it seems to be working now.
> VERY strange bug.
>=20
> Thanks
> -tyler
| |
| Jeff Cochran 2004-12-25, 4:51 am |
| On Fri, 24 Dec 2004 09:31:02 -0800, "keith58"
<keith58@discussions.microsoft.com> wrote:
>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?
This doesn't sound like an IIS issue. If it were, restarting the
modem would have no effect. Next time, try just resetting the modem
and nothing else to see. There may be an issue with your modem/router
having a buffer overflow issue, or receiving too many fragmented
packets if you have a poor connection, but there's no way to be sure
without more diagnosis. If this error appears on a client, can you
still browse the site from the server? Or a client inside your
router/modem?
Jeff
|
|
|
|
|