Re: Slow Internet Access with FW Client
- From: "Phillip Windell" <philwindell@xxxxxxxxxxx>
- Date: Wed, 1 Aug 2007 15:20:06 -0500
One thing you can do is download the Best Practices Analyser for ISA and run
it on the ISA. It will point out possible configureation issues that can
cause problems. I ran it several times during the installation of our ISA
before I put it into service.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html
Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc
Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx
-----------------------------------------------------
"johnny_mango" <johnnymango@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5A5F3370-108A-4D49-8472-52E75C17DF1A@xxxxxxxxxxxxxxxx
I had the external interface of the ISA Server with a fixed speed, to match
the 100MB/s speed of the switch, but performance was worse, so I have
reversed that.
Also, have configured the FW client to connect to the ISA server using its
FQDN.
Any more ideas? It seems the access is universally slow - ie all clients,
all web pages, and it is only a small number of clients using the ISA
2006.
"Phillip Windell" wrote:
"johnny_mango" <johnnymango@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DA2FA16C-071B-4331-BAC4-8B5F54678113@xxxxxxxxxxxxxxxx
Thanks for your reply. Unfortunately DHCP is not a possibility in this
scenario as the client doesn´t use it and desn´t want to - I´ll never
understand the reliance on static IP´s but there you go.
Not all clients will properly use the DNS method. That could be part of
your
problem.
Why would it be preferential to refer to the ISA Server by it´s FQDN
and
not
by its IP?
The WPAD entry is supposed to be a CNAME record that point to an A record
and not an IP#. In addiotn to that this would allow changing/replacing a
proxy by simply changing the A record that the CNAME points to. No
configuration changes would be required on the clients.
I'm just trying to create a "clean" setup to make it easier to figure out
the bad performance. Sometimes making the setup more clean makes to
problem
just go away to begin with.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or
Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html
Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc
Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx
-----------------------------------------------------
.
- Follow-Ups:
- Re: Slow Internet Access with FW Client
- From: johnny_mango
- Re: Slow Internet Access with FW Client
- References:
- Re: Slow Internet Access with FW Client
- From: Phillip Windell
- Re: Slow Internet Access with FW Client
- Prev by Date: Re: Slow Internet Access with FW Client
- Next by Date: Re: Slow Internet Access with FW Client
- Previous by thread: Re: Slow Internet Access with FW Client
- Next by thread: Re: Slow Internet Access with FW Client
- Index(es):
Relevant Pages
|