It started of by getting that dreaded phone call 'The network is down can you come in early!'
Get in and the power has tripped in the server room, find that one of the power supplies on a server has died when we had a small power surge at about 6.15 this morning. Thats not a problem as server has 2 power supplies so will be ordering a new one.
Turned all servers on and all came on fine, went back to my machine and tried the internet and it didn't work. Tried to connect to the isa via rdp to make sure that all was ok and couldn't connect to it. Went back to the server it self and checked the services and the Microsoft Firewall service wont start.
I have rebooted it twice, done windows updates to if there was a package that was needed and still nothing.
Message in event viewer is attached as is the message i get when i open the isa management console.
Currently seeing if i can set it so all the machines bypass the isa and go straight to countys proxy.
Have you tried running a repair install and does it have SP1 installed. You may end up needing to reinstall it if this does not resolve it. An experts exchange post seemed to indicate that this could also be caused by corruption of the ISA bits in AD.
You can export all of the firewall setting from the configuration console. I think by right clicking on the server object in the right hand list. Its been a while since I was using 2004 but I know you can do it.
The other thing to try would be running the ISA BPA (Best Practice Analyser) on it to see if it can find anything wrong.
On your knackered ISA box, check the Service dependencies in regards to the firewall service.
Then check each of these services to ensure they are started.
I did a quick look around the Net but error code 2 (0x2) isn't one that I came up with. A few similar things in regards to the EventID came up and they suggested checking other services, as the ISA firewall service may be failing due to one of it's dependencies failing on you.