We're running ISA 2004 SP2 on Win 2003 SP1 server, WinXP SP2 clients w/IE6. Clients are configured to automatically detect proxy settings with WPAD from DHCP entry.
Everything was working fine until I changed public IP addresses for new ISP last week. Now When we first open the browser, some users get a 20-30sec delay. Some of those affected say "Connecting to Site <IP address of ISA>" and others say "Detecting proxy settings...". Once we get past the initial delay, web pages download at a normal speed.
If I uncheck Automatically detect settings, there is no delay. I've applied the patch from KB907455 and there are still delays. Any more ideas to try before I call PSS?
I had the exact same issue with the delay. I have 2 network interfaces on my ISA server, one Internal, one external. Same server/client setup as you. Here is how I fixed it: Go to the properties of the External NIC (then go to Properties of TCP/IP, click on Advanced, click on the DNS tab, and make sure the Register this Connection's addresses in DNS is not checked). Once you are done that, go to your Domain Controller, go into DNS, open up Forward lookup Zones and delete the entry for the External IP (there should be 2 entries there for your ISA server, 1 internal IP and 1 external). Reboot your ISA server after this is Let me know if this worked
jzietsma: Sorry, but there is only one IP in DNS for ISA and it's the internal interface
PatrickM: Clients are connecting via the WINS name. As far as I can tell, it's not a DNS/Ad issue because fwctool TestAutoDetect /type:DNS and fwctool TestAutoDetect /type:DHCP both come back clean without any delays. In fact, for the biggest part of the delay, teh status bar is displaying "Connecting to Site <IP address of ISA>".
Well, I'm off to PSS to see what they have to say. I'll let you know
As part of my intial troubleshooting on this issue, I had disabled the web proxy. What fixed it was re-enabling it. What was happening was that clients were hitting th ISA server on port 8080 and getting denied. They would then time out and retry on port 80 and get right thru.