RE: Port 80 on external interface

  • From: Jim Harrison <jim@xxxxxxxxxxxx>
  • To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
  • Date: Thu, 22 Jan 2004 06:44:04 -0800

Got an ISAInfo?
It's a lot easier to find this stuff that way...
http://isatools.org

  Jim Harrison
  MCP(NT4, W2K), A+, Network+, PCG
  http://isaserver.org/Jim_Harrison/
  http://isatools.org
  Read the help / books / articles!


On Thu, 22 Jan 2004 05:48:46 -0700
 "Derek Taylor" <d.taylor@xxxxxxxxxxxxxx> wrote:
http://www.ISAserver.org

Thanks for responding Thomas. I get four messages, pasted below:

Server publishing rule [Vulture] that maps 192.168.1.4:80 TCP to
212.219.51.11:80 for protocol [HTTP Inbound] 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.

Server publishing rule [Owl] that maps 192.168.1.14:80 TCP to
212.219.51.59:80 for protocol [HTTP Inbound] 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.

Server publishing rule [AFCL] that maps 192.168.1.44:80 TCP to
212.219.51.23:80 for protocol [HTTP Inbound] 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.

Server publishing rule [Kite] that maps 192.168.1.6:80 TCP to
212.219.51.14:80 for protocol [HTTP Inbound] 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.


Regards

Derek

------------------------------------------------------
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
------------------------------------------------------
Other Internet Software Marketing Sites:
Leading Network Software Directory: http://www.serverfiles.com
No.1 Exchange Server Resource Site: http://www.msexchange.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
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: