RE: Port 80 on external interface
- From: "Derek Taylor" <d.taylor@xxxxxxxxxxxxxx>
- To: isalist@xxxxxxxxxxxxx
- Date: Thu, 22 Jan 2004 05:48:46 -0700
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
Other related posts:
