Re: Slow companyweb over https://fqdn:444

Tech-Archive recommends: Fix windows errors by optimizing your registry

Someone posted recently with a similar speed issue.
Someone responding pointed them a program called TCP Optimizer.

When the OP ran it, it lists current settings and there is a button to select optimal settings and then a check box to apply to all NICs.

Fix the MTU issue for them...it certainly couldn't hurt in this case

http://www.speedguide.net/downloads.php
Yes I have run it on my own workstation and server

--
Cris Hanna [SBS-MVP]
--------------------------------------
Please do not respond directly to me, but only post in the newsgroup so all can take advantage
"Jim Behning" <jimbehning@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:2tj19219m3dq3uabuqfe4rhfg1j8lck3se@xxxxxxxxxx
So what is the upload speed of the dsl. Most dsl connections are not
symetric. Are you testing this from the real world? Of course that
would be the first url of course. No, there is nothing to do with
certificates if you are having speed issues. The server cannot serve
any faster than your slowest connection. That means that fi you do a
speed test fromdslreports.com and it shows an upload speed of 256 k
then no one in the real world is going to see your server any faster
than that.

On Wed, 14 Jun 2006 19:20:01 -0700, IT PHYTOSAN
<ITPHYTOSAN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>Thanks for your note. Its a 1.5MBs DSL, but it is not bandwith related: Two
>scenarios on the same remote computer with the same internet connections:
>
>1. https://fdqn:444 very slow
>2. http://companyweb over vpn very fast
>
>It seems that the https protocol bears significant overhead and I am
>guessing that I can tweak the certificate extensions. Any hints?
>
>IT PHYTOSAN
>
>"Mark" wrote:
>
>> DSL or T1? sounds like bandwidth
>>
>> "IT PHYTOSAN" <ITPHYTOSAN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:8D840C0C-C475-4A16-8DD0-4A16E2A6B509@xxxxxxxxxxxxxxxx
>> > The company web is slow to respond over a secure connection
>> > https://fqdn:444
>> > and fairly quick over port 80 using a VPN. certificates are standard
>> > certificates issued by the SBS2003 built in CA.
>> >
>> > Any ideas?
>> >
>> > Thanks IT PHYTOSAN
>>
>>
>>
Quantcast