ISA Server: Windows Server 2003 Standard
DNS/DHCP/PDC: Windows Server 2003 x64 R2 Standard
Users: Windows XP SP2, Firewall Client (most recent version)..
*Affecting random people, including myself (domain admin).

Suddenly my network has been getting the "Connect to wpad" prompt when
attempting to access a webpage. Last week random users were prompted
for about an hour, then the problem vanished. Today is it back, and
hasn't gone away.

On my computer, when I set Firewall Client to Auto detect ISA server,
it fails to connect.  When I manually specify the server, it connects
to the ISA Server.

I must then go into IE LAN settings, and UNcheck Autodetect settings,
and UNcheck Use Proxy Server.

Then I have Inter/Intranet acess..

Disabling the Firewall Client from the start also seems to work, until
certain firewall policies are accessed.

Two weeks ago we added a domain controller to another network that
runs through ISA.. my colleague thinks this might be related, but it
may not. This new DC is not running DHCP or DNS server.

I think its related to whatever is causing my computer to fail when
auto-discovering ISA.. however I don't know how to pinpoint it since
nothing has changed in ISA in months.  There was a WPAD entry on our
DHCP server, but we removed it this morning thinking it would help.
Where else can I look?

Thanks, Kurt

We re-added the WPAD Entry in DHCP.

I've also noticed that as computer's leases expire, and they restart..
then that computer now is affected with this wpad prompt. So soon the
entire network will be affected.

See if http://support.microsoft.com/kb/885683 or
http://support.microsoft.com/kb/889035 help.

--
Jim Harrison (ISA SE)

This posting implies no warranty and confers no rights.
http://catb.org/~esr/faqs/smart-questions.html




We re-added the WPAD Entry in DHCP.

I've also noticed that as computer's leases expire, and they restart..
then that computer now is affected with this wpad prompt. So soon the
entire network will be affected.

As a follow up: this link worked for me

http://support.microsoft.com/kb/889035

I found it about an hour before you posted, but that was the one!