[isalist] Re: proxy configuration
- From: "Ara Avvali" <Ara.Avvali@xxxxxxxxxxxxx>
- To: <isalist@xxxxxxxxxxxxx>
- Date: Fri, 27 Oct 2006 10:15:47 -0700
Hi Dan,
Would you mind keeping me posted if you find the help reference? Thank
you
________________________________
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Ball, Dan
Sent: Friday, October 27, 2006 10:11 AM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Re: proxy configuration
If you recall, a month or so ago I had problems with similar symptoms.
I'll have to go back through my messages and see what the final result
was, as I think it was a combination of things like DNS resolution, wpad
retrieval, auto-configuration, etc...
________________________________
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Ara Avvali
Sent: Friday, October 27, 2006 11:58 AM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Re: proxy configuration
Hi Jim,
Thanks for your response. The problem I have we are using a web based
ADP payroll by going to https://payex.adp.com. As you notice it requires
an assigned certificate to go to site. Client is a xp sp2 with pop up
blocker disabled and there is an allow rule on top going from internal
to *.adp.com which allows all users access.
Problem is behind ISA pages load slowly (2-3 times slower) and sometimes
they even time out. Checking on live monitoring I found that connections
are going to njpod18.adp.com which I think *.adp.com should cover it. If
I connect the client directly to the router in front of ISA then
everything works as fast as expected. Yesterday there was a threat about
speed and Tom mentioned increasing connections should help. Even that
gave me no luck.
I have convinced the accounting that we should migrate to installed
version of payroll program instead of web based. But that could be done
after January. For now on I just connect one of machines directly to
internet and let them do the payroll but that is not the practical
solution. Man what a mess it would be if I deploy IE7 and the
certificate check it has.
I was wondering if anyone has any experience with this problem. ADP
support as soon as they see a proxy server set in IE, then it is my side
to figure out the problem. They have no documents about it. I found some
instructions but that was no help either. That was why I tried the
direct access solution.
http://isainsbs.blogspot.com/2006/01/allowing-adp-through-isa-2004.html
http://forums.isaserver.org/m_2002000597/mpage_1/key_/tm.htm#2002029215
Appreciated
________________________________
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Jim Harrison
Sent: Thursday, October 26, 2006 6:25 PM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Re: proxy configuration
You're shotgunning, Ara.
Creating an "allow all" rule has nothing to do with "speed".
Unless *.adp is part of the network structure that it "local" to the
browser client, adding it to the web browser and domains data is
inappropritate.
Proxycfg has nothing to do with IE settings or IE behavior.
Can you explain what you mean by "speed problems"?
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Ara Avvali
Sent: Thursday, October 26, 2006 4:32 PM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] proxy configuration
Hello everyone.
I added *.adp.com for direct access to adp site. Created a rule to allow
all outbound traffic from internal to *.adp.com but I still have speed
issues. So I ran the proxycfg on the client which is xp sp2 with
firewall client installed and it is telling me nothing is set for direct
access. Any idea why? Appreciated
All mail to and from this domain is GFI-scanned.
Other related posts:
