I have tried this under two different scenarios, and have achieved the same
results.

> MS Proxy 2 [snip] is very easy to configure, and it has good lagging
> capabilities,

LOL.  Sure you didn't mean "logging"? :-).
I meant lagging, but I should have said logging

> where it lacks at is the performance area, it can really slow
> certain types of web access down, especially real audio, large FTP
> transfers, etc...

I haven't seen this problem with my MSP2.0 install. I suspect this might be
an under-configuration problem for your server.

The hardware is definitely not lacking, raid, large amount of cache, lots of
memory, larget internet pipe, etc..
I suspect that it would be better configured in a manner that offloaded the
logging and packet filtering from the machine that is responsible for the
proxying...

I have seen far greater performance in the freeBSD and Linux environments,
which because of overhead is  probably unrealistic to expect out of NT, (I
am definitely not flaming microsoft, because there are some products that
really work well for me, others I feel have more appropriate counterparts,
whether on the MS platform or another).

Running Performance monitor locally or remotely shows no overloaded
processes which can be attributed to this, so this is the basis for my
reccomendations.

But if you really want LAGGING capabilities, well then....

Tim Doscher
MCSE
[EMAIL PROTECTED]
(I still use MS Proxy2 alot anyways)

-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]

Reply via email to