Jim's answer was the correct one. Please follow that lead. From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Glenn P. JOHNSTON Sent: Tuesday, October 10, 2006 10:49 PM To: isalist@xxxxxxxxxxxxx Subject: RE: [isalist] Re: The Web Proxy filter failed to bind its socket to 192.168.5.1 port 8080 The message indicates that something is hooking up to 8080, before the firewall attempts to. What ever it is , it must be happening fairly soon after the boot process finishes as the ISA firewall is pretty quick off the mark. Use of a tool like IP-TOOLS or one of the many similar shareware programs available on the internet will probably give you a lead on what program / servive is hooking 8080 before the ISA firewall attempts to. ________________________________ From: isalist-bounce@xxxxxxxxxxxxx on behalf of Krisna Keo Sent: Wed 11/Oct/2006 12:46 To: isalist@xxxxxxxxxxxxx Subject: [isalist] Re: The Web Proxy filter failed to bind its socket to 192.168.5.1 port 8080 Hi Amy, I only run DHCP service on my MS ISA. Thanks Krisna ________________________________ From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Amy Babinchak Sent: 10/10/2006 7:06 PM To: isalist@xxxxxxxxxxxxx Subject: [isalist] Re: The Web Proxy filter failed to bind its socket to 192.168.5.1 port 8080 This is usually caused by when something else binds 8080 before ISA can get there. What else is running on your firewall? Amy ________________________________ From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Krisna Keo Sent: Tuesday, October 10, 2006 4:16 AM To: isalist@xxxxxxxxxxxxx Subject: [isalist] The Web Proxy filter failed to bind its socket to 192.168.5.1 port 8080 Dear ISA List members, My gateway machine is running Ms ISA 2004 std on Ms window 2003 server std edition. Recently, I have not noticed my ISA server alert the warning message: Event ID 14148, source Microsoft ISA server Web Proxy, Description: The Web Proxy filter failed to bind its socket to 192.168.5.1 port 8080. This may have been caused by another service that is already using the same port or by a network adapter that is not functional. To resolve this issue, restart the Microsoft Firewall service. The error code specified in the data area of the event properties indicates the cause of the failure. I've found the related information on http://forums.isaserver.org/m_2002020318/mpage_1/tm.htm#2002022651, but my server does not run IIS service Any help would be appreciated. Thanks Krisna