you mention xxx.xxx.xxx.135... what ip does that belong to. I'm sure it's bound to the incoming NIC. But it's not the primary IP is it ? This is all ringing a bell, like I have heard of it before. I will look though my archive of past isalist posts for whatever I can find. ----- Original Message ----- From: "Bryan Andrews" <bandrews@xxxxxxxxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Saturday, March 02, 2002 2:49 PM Subject: [isalist] Re: Server Publishing - for websites... http://www.ISAserver.org Secure NAT only. Why would the proxy service be trying to bind to these external IP's? The firewall service actually does the server publishing right? Bryan Andrews - Trend Influence 404.523.8649 Office - 404.597.2316 Cell [ http://www.trendinfluence.com ][ http://www.umix.net ] -----Original Message----- From: Mark Strangways [mailto:strangconst@xxxxxxxxxx] Sent: Saturday, March 02, 2002 2:35 PM To: [ISAserver.org Discussion List] Subject: [isalist] Re: Server Publishing - for websites... http://www.ISAserver.org Your servers need to be secureNAT only, no firewall client or proxy client. How are these machine set ? Mark ----- Original Message ----- From: "Bryan Andrews" <bandrews@xxxxxxxxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Saturday, March 02, 2002 2:10 PM Subject: [isalist] Re: Server Publishing - for websites... http://www.ISAserver.org Do I need to configure outgoing web requests individually as well? It does not seem to have anything to do with external ips though? Only internal. -----Original Message----- From: Bryan Andrews Sent: Saturday, March 02, 2002 2:08 PM To: [ISAserver.org Discussion List] Subject: [isalist] Re: Server Publishing - for websites... http://www.ISAserver.org There is nothing on the ISA server box except ISAserver. No dns, no IIS, etc. 1 ip is being used for several multihomed webs internally (thru server publishing), and another ip that is using web publishing to another internal ip on another box (exchange server OWA). It seems to be something with the Web Proxy. Everything seems to work ok as long as the web proxy does not start first. Event Type: Warning Event Source: Microsoft Web Proxy Event Category: None Event ID: 14148 Date: 3/2/2002 Time: 2:05:36 PM User: N/A Computer: TATLISA2 Description: Web Proxy service failed to bind its socket to 216.0.216.135 port 80. This could be caused by another service that is already using the same port or by a network interface card that is not functional. The error code specified in the Data area of the event properties indicates the cause of the failure. For more information about this event, see ISA Server Help. Data: 0000: 40 27 00 00 @'.. I just don't understand what the web proxy is trying to hook up to that ip and port for... -----Original Message----- From: Mark Strangways [mailto:strangconst@xxxxxxxxxx] Sent: Saturday, March 02, 2002 2:01 PM To: [ISAserver.org Discussion List] Subject: [isalist] Re: Server Publishing - for websites... http://www.ISAserver.org Bryan , are these servers on the ISA ? Looks like you may need to try to get Host Headers working at the ISA server machine. Seems to be a binding problem with the IP's, as if you are trying to use one IP for many servers. Maybe I'm not seeing your problem fully ? Mark ----- Original Message ----- From: "Bryan Andrews" <bandrews@xxxxxxxxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Saturday, March 02, 2002 1:41 PM Subject: [isalist] Server Publishing - for websites... http://www.ISAserver.org We currently publish web sites in 2 ways, server and web publishing. I only have 1 web site published via web publishing and I have disabled it trying to troubleshoot this issue (does not seem to make a difference). I have the web listeners configured individually for incoming web requests. But I always get either one of these two error messages: This one occurs if I start the firewall service first then the proxy: Event Type: Warning Event Source: Microsoft Web Proxy Event Category: None Event ID: 14148 Date: 3/2/2002 Time: 1:32:28 PM User: N/A Computer: TATLISA2 Description: Web Proxy service failed to bind its socket to 216.0.216.135 port 80. This could be caused by another service that is already using the same port or by a network interface card that is not functional. The error code specified in the Data area of the event properties indicates the cause of the failure. For more information about this event, see ISA Server Help. Data: 0000: 40 27 00 00 @'.. or These 2 occur when I start the proxy and then the firewall: Event Type: Warning Event Source: Microsoft Firewall Event Category: None Event ID: 14163 Date: 3/2/2002 Time: 1:30:26 PM User: N/A Computer: TATLISA2 Description: Server publishing rule [All TI Multi-Homed Webs] that maps 10.0.2.121:80 TCP to 216.0.216.135:80 for protocol [_http access] 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. Event Type: Warning Event Source: Microsoft ISA Firewall H.323 Filter Event Category: None Event ID: 20063 Date: 3/2/2002 Time: 1:30:44 PM User: N/A Computer: TATLISA2 Description: H.323 filter is not configured to register with an H.323 Gatekeeper, attempting to find a gatekeeper using multicast discovery. Inbound H.323 calls will not succeed while the filter is not registered with a gatekeeper. To configure the filter to use a particular gatekeeper, edit the H.323 filter Call Control properties and enter the H.323 gatekeeper to register with. I have just updated to sp1 but this was an issue before that I had hoped was something weird that might be fixed now. What exactly is the proxy trying to hook up to the external address via: Web Proxy service failed to bind its socket to 216.0.216.135 port 80? How do I separate this? I thought configuring the incoming web listeners would do this. Thanks for any help. ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: strangconst@xxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: bandrews@xxxxxxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: bandrews@xxxxxxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: strangconst@xxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: bandrews@xxxxxxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: strangconst@xxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')