This is the event that I guess is the culprit. Most of the stuff I was doing yesterday was creating some new client sets and destination sets. Event Type: Warning Event Source: Microsoft Firewall Event Category: None Event ID: 14163 Date: 12/11/2001 Time: 7:39:24 PM User: N/A Computer: TATLISA2 Description: Server publishing rule [All TI Multi-Homed Webs] that maps 10.1.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. This is my server publishing rule that I publish all my webs on (not Web Publishing). I do however have a couple of web publishing rules as well for Exchange and Others that I am not concerned about reporting for. Event Type: Error Event Source: Microsoft ISA Server Control Event Category: None Event ID: 14079 Date: 12/11/2001 Time: 3:22:25 PM User: N/A Computer: TATLISA2 Description: Due to an unexpected error, the service fwsrv stopped responding to all requests. This occurred 1 time(s) in the past 13:53 hours. Try to stop the service or kill the corresponding process if it does not respond, and start it again. Check the Event Viewer for related error messages. Not sure... is this the Web Proxy Service: Event Type: Information Event Source: DrWatson Event Category: None Event ID: 4097 Date: 12/11/2001 Time: 3:21:18 PM User: N/A Computer: TATLISA2 Description: The application, wspsrv.exe, generated an application error The error occurred on 12/11/2001 @ 15:21:17.302 The exception generated was c0000005 at address 01024F7A (CKeepAlive::operator=) Data: Then I have hundreds of these before the others above (the day before my recent major troubles though): Event Type: Warning Event Source: Microsoft Firewall Event Category: None Event ID: 14152 Date: 12/10/2001 Time: 12:38:40 PM User: N/A Computer: TATLISA2 Description: A User Datagram Protocol (UDP) packet was dropped because it was larger than the maximum UDP packet allowed by the Firewall service. I also have these periodically: Event Type: Warning Event Source: Microsoft ISA Firewall H.323 Filter Event Category: None Event ID: 14 Date: 12/12/2001 Time: 10:38:57 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. -----Original Message----- From: Jim Harrison [mailto:jim@xxxxxxxxxxxx] Sent: Tuesday, December 11, 2001 10:17 PM To: [ISAserver.org Discussion List] Subject: [isalist] Re: My ISA server is sensitive... http://www.ISAserver.org No; you may be experiencing one or (heaven forbid) more known issues with ISA and publishing. What event log entries do you see in the system and application event logs? Jim Harrison MCP(NT4, 2K), A+, Network+, PCG http://isaserver.org/authors/harrison/ ----- Original Message ----- From: "Bryan Andrews" <bandrews@xxxxxxxxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Tuesday, December 11, 2001 18:51 Subject: [isalist] My ISA server is sensitive... http://www.ISAserver.org I don't know about anyone else here... but our ISAserver seems really sensitive... I mean, I feel like I know this thing pretty well... I have built it twice now... We are using client sets and destination sets I believe the way I am supposed to, and network is great - As long as I don't molest it. It seems like whenever I do anything much to it... it will get tempermental and my webs will stop being published (I'll start to get URL denied errors). I am very careful to know what I have done and how to undo it. But it seems more often than not I have to either restart it, or restore the config. It has gotten to the point where I have to adhere by a very strict SLA policy (of after midnight), which is not a bad rule, but there are things that I should be able to do (and undo if I have to) without disturbing normal network traffic. Perhaps I am screwing something up, but when stopping and restarting the services doesn't work, but restarting the box does, this gets very frustrating and makes me think I am not screwing it up many of the times... Is this par for the course with ISA in anybody else's experience? Thanks for any thoughts here... ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx 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')