[isalist] Re: The Web Proxy filter failed to bind its socket to 192.168.5.1 port 8080
- From: "Gerald G. Young" <g.young@xxxxxxxx>
- To: <isalist@xxxxxxxxxxxxx>
- Date: Tue, 10 Oct 2006 09:43:44 -0400
You can also try running the following command from the command prompt
to determine which process is using port 8080.
netstat -ano | find /i ":8080"
Cross reference the PID (furthest right column) against list of
processes in Task Manager or you can use the following command at the
same command prompt:
tasklist /FI "PID eq <enter PID from above command>" (e.g., tasklist /FI
"PID eq 204")
Cordially yours,
Jerry G. Young II
Applications Engineer, Platform Engineering
Enterprise Hosting
NTT America, an NTT Communications Company
22451 Shaw Rd.
Sterling, VA 20166
Office: 571-434-1319
Fax: 703-333-6749
Email: g.young@xxxxxxxx
________________________________
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Jim Harrison
Sent: Tuesday, October 10, 2006 9:08 AM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Re: The Web Proxy filter failed to bind its socket to
192.168.5.1 port 8080
This can also happen when the NIC drivers don't "plug 'n pray" properly,
leaving ISA with no IP on which to bind when the NIC is disconnected &
reconnected (like when your switch flakes out on you).
Try disabling DHCP media sense per
http://support.microsoft.com/kb/239924.
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On Behalf Of Krisna Keo
Sent: Tuesday, October 10, 2006 1: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
All mail to and from this domain is GFI-scanned.
Other related posts:
