Re: Server Publishing Rule Failed & Firewall service failed to bind socket
From: Jenna (stilesj)
Date: 03/11/04
- Next message: Martin Berry: "Viewing HTTPS site on a different port"
- Previous message: Ahmed Nour: "ISA Configuration for leased line"
- In reply to: Jenna: "Server Publishing Rule Failed & Firewall service failed to bind socket"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 11 Mar 2004 07:14:40 -0500
I apologize...I should have read all my materials first...I found the
solution in Tom Shinder's book, ISA Server and Beyond as a simple change to
make to the Incoming Web Requests listener (it was causing a port
contention).
Thanks!
"Jenna" <anonymous@discussions.microsoft.com> wrote in message
news:acb501c406fb$f92f6f90$a101280a@phx.gbl...
> Running ISA Server 2000 on Windows Server 2003, with IIS
> 6.0 (also running
> Exchange 2003 with OWA and hosts our website).
> It came to my attention two days ago that we can no
> longer access our
> website or OWA outside of the LAN. If you go to
> www.meachamapel.com, you'll
> see what I mean. First of all, it asks for a password
> (which it shouldn't
> do), then no matter what you fill it, it just asks you
> three times, then
> gives an ISA 401 Unauthorized error message.
>
> With that, I started noticing in the event log this error:
>
> Event Type: Warning
> Event Source: Microsoft Firewall
> Event Category: None
> Event ID: 14163
> Date: 3/9/2004
> Time: 9:51:15 PM
> User: N/A
> Computer: MA2
> Description:
> Server publishing rule [WWW] that maps 10.0.0.4:80 TCP to
> 10.0.1.2:80 for
> protocol [WWW] failed because the port on the external
> interface is being
> used by another application. The Firewall service failed
> to bind socket for
> the server on the firewall since another process is using
> the same port.
> Check for any other process using the same port and
> terminate if necessary.
>
> This sounds very similar to a post I read here from IT
> Dep on 1/30, but I
> don't have Windows Media Services nor anything else I can
> think of that
> would be using port 80. How can I check what process
> could be using that
> port?
>
> The only thing I can think of that I did before this
> started happening was
> to uninstall the FTP component on IIS...then reboot the
> server.
> I'm very grateful for any advice and would be happy to
> provide further
> information on any of our settings if it would help solve
> this issue.
- Next message: Martin Berry: "Viewing HTTPS site on a different port"
- Previous message: Ahmed Nour: "ISA Configuration for leased line"
- In reply to: Jenna: "Server Publishing Rule Failed & Firewall service failed to bind socket"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
