RE: Warning - 14148 - Web Proxy Server failed to bind to port 443
- From: "Jim Harrison" <jim@xxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Tue, 1 Oct 2002 13:28:25 -0700
Glad you found it...
Jim Harrison
MCP(NT4, W2K), A+, Network+, PCG
http://isaserver.org/pages/author_index.asp?aut=3
http://isatools.org
Read the books!
----- Original Message -----
From: "Alfonso Lopez de Ayala" <alopezdeayala@xxxxxxxxxxxx>
To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
Sent: Tuesday, October 01, 2002 10:41 AM
Subject: [isalist] RE: Warning - 14148 - Web Proxy Server failed to bind to
port 443
http://www.ISAserver.org
Ok... solved this one... sorry for having overlooked something so simple
and asking so many questions!
For completeness of threads in this awesome forum, here's what the
problem was:
IIS was indeed set to only listen to the internal IP and "socketpooling"
was disabled indeed, BUT in IIS > web site > Properties IP Address >
Advanced > Multiple SSL identities it also listed "(All Unassigned)" !!!
Removing that entry and restarting both the w3svc and the ISA Web Proxy
serviced solved everything, of course.
Jim, you're the best!
Alfonso
-----Original Message-----
From: Alfonso Lopez de Ayala [mailto:alopezdeayala@xxxxxxxxxxxx]
Sent: Tuesday, October 01, 2002 10:14 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] Warning - 14148 - Web Proxy Server failed to bind to
port 443
http://www.ISAserver.org
Everything was working fine and now suddenly get the following error in
the Windows Event logs (Application Log):
Type: Warning
Source: Microsoft Web Proxy
Event ID: 14148
Description: Web Proxy Server failed to bind its socket to port 443.
This could be caused by another service that is already using the same
port or by a network interface card that is not functional.
IIS is in the same box, but it's set to listen only on the internal IP,
and has SOCKETPOOLING disabled. I've tested the network card and it
works fine thru port 443.
As a result of this, a Web Publishing Rule set to allow traffic to a
secure web site in IIS doesn't work anymore! I can see the packets to
port 443 BLOCKED in the in the ISA IP logs.
WHAT OTHER SERVICE CAN BE TYING UP THE SSL PORT 443??? Could it be
another ISA service (firewall, scheduled download, or other) that causes
the problem?
Alfonso
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Exchange Server Resource Site: http://www.msexchange.org/
Windows Security Resource Site: http://www.windowsecurity.com/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
alopezdeayala@xxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Exchange Server Resource Site: http://www.msexchange.org/
Windows Security Resource Site: http://www.windowsecurity.com/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jim@xxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
