|
Home > Archive > IIS Server Security > July 2005 > SSL HTTPS works at first, then very slow or stops after some time?
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 |
SSL HTTPS works at first, then very slow or stops after some time?
|
|
|
| Hello,
I am in the process of implementing SSL for our companies' Web site. We
have a digital certificate installed on a W2K box running IIS 5.0. When
I first access the Web site over HTTPS, the response is immediate
(after the digital certificate alert). I can continue to access pages
on the Web site untill a few minutes later HTTPS requests stop or
become very slow (2-10 minutes). When I configure the site to use just
HTTP everything works fine. Do you know what this could be?
Thank You For Your Help,
Nathan
| |
|
| I figured out what was wrong. It was our router. Our Netgear MV814V2
wireless router was doing something wrong (port forwarding or deeper)
because we purchased a new Linksys WRT54GS wireless router and it
worked fine, both with HTTP and HTTPS. I have an open case with
Netgear, but based on our experience I would not suggest using this
model when you have Web servers behind the router.
| |
| David Wang [Msft] 2005-07-07, 2:48 am |
| Thanks for reporting the resolution.
This one *is* pretty weird.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Nate" <nathandeneau@cox.net> wrote in message
news:1120680165.842973.278480@f14g2000cwb.googlegroups.com...
I figured out what was wrong. It was our router. Our Netgear MV814V2
wireless router was doing something wrong (port forwarding or deeper)
because we purchased a new Linksys WRT54GS wireless router and it
worked fine, both with HTTP and HTTPS. I have an open case with
Netgear, but based on our experience I would not suggest using this
model when you have Web servers behind the router.
|
|
|
|
|