| analog 2005-01-21, 5:52 pm |
| we access a database application on a remote server via an https:// url.
from time to time during the day this site becomes inaccessible to us,
sometimes for hours.
unfortunately, we don't have access to the server, so i can't do any
monitoring from that end. the network administrator there feels that the
problem is on our end. i am not so sure.
1) we can access other secure sites even when this one is down. we use
other secure sites extensively during the day without incident.
2) we can access this site most of the time.
3) sometimes when we cannot access the url with https:// we can access it
with
http://
4) when we cannot access it from our site (cable broadband*) we can use a
dial up and access it. (*we have dynamic IP, but it does not change during
these incidents).
5) when we cannot access it from our site, i can access it if i browse
anonymously (anonymizer 2005).
6) sometimes when it spontaneously becomes available again it seems to be
around the time of a database update. (apparently the service is not
restarted as part of this, though).
7) the site is running IIS 5.0 and the database app uses ASP.
doesn't this seem to suggest that our IP address is being blocked from the
secure url from time to time, and that something on the server is releasing
it? is there some setting on the server OS or the web server or the
certificate that would account for this? if i can find something specific to
have the site owners check, they'll probably do it....
|