Isa Server Error The Operation Failed
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > The Operation Failed error when clicking Protocol tab on a Firewall rule in ISA Server Want to Advertise Here? Solved The Operation Failed error when clicking Protocol tab on a Firewall rule in ISA Server Posted on 2008-01-03 MS Forefront-ISA Windows Networking 1 Verified Solution 9 Comments 2,040 Views Last Modified: 2008-11-18 When I click the protocol tab in ISA SErver firewall rule, I get an error "The operation failed". Here is the text that comes with the mmc.exe error afterwards. I'm trying to open port 2001. szAppName : mmc.exe szAppVer : 5.2.3790.3959 szModName : hungapp szModVer : 0.0.0.0 offset : 00000000 0 Question by:bridgetimiller Facebook Twitter LinkedIn Google LVL 51 Best Solution byKeith Alabaster It can be if you use WSUS - you can also get it from MS updates but it is from one of the other options as it is not a critical one. Go to Solution 9 Comments LVL 51 Overall: Level 51 MS Forefront-ISA 40 Windows Networking 25 Message Expert Comment by:Keith Alabaster2008-01-04 Which version of ISA are you using and what service pack? Is ISA installed as a firewall/proxy or just proxy? 0 Message Author Comment by:bridgetimiller2008-01-04 I'm using ISA 2004 4.0.2163.213. It's a firewall and proxy. 0 LVL 51 Overall: Level 51 MS Forefront-ISA 40 Windows Networking 25 Message Expert Comment by:Keith Alabaster2008-01-04 OK - make sure ISA sp3 is installed also Are you running the mmc from the ISA server itself or from a management console elsewhere? If it is from a seperate machine, does it work OK from the ISA console? Standard version of ISA are the Enterprise version? Has this ever worked or is it a new install? If it has worked before, what has changed? MS Updates? Make sure you have .net 1.1 installed on the ISA Server then run up the BPA - find it here. http://www.microsoft.com/downloads/details.aspx?FamilyID=D22EC2B9-4CD3-4BB6-91EC-0829E5F84063&displaylang=en What does it report? Keith 0 Message Author Comment by:bridgetimiller2008-01-04 I'm going to do this next week....I'll keep you posted. Thanks! 0 LVL 5
Yosefi - MSFTApril 6, 20098 Share 0 0 1. Introduction This scenario is based on a real experience that we were able to reproduce in lab. When Microsoft firewall client tries to connect to ISA 2006 server, it fails with an error: Operation failed as result of a network error. This happens with both automatic and manual detection of the ISA server from the client. Figure 1 – Firewall Client Error message and red mark https://www.experts-exchange.com/questions/23056464/The-Operation-Failed-error-when-clicking-Protocol-tab-on-a-Firewall-rule-in-ISA-Server.html in the firewall client icon in taskbar. Although the error message says “Operation failed as result of a network error” we didn’t have any network problem reaching the ISA Server 2006 from this workstation, as you can see in the netmon trace below: TCP Three Way Handshake successfully happening: 10.20.20.201 10.20.20.1 TCP TCP:Flags=……S., SrcPort=1173, DstPort=1745, PayloadLen=0, https://blogs.technet.microsoft.com/isablog/2009/04/06/firewall-client-is-unable-to-connect-to-isa-server-2006/ Seq=2944340194, Ack=0, Win=65535 (scale factor 0) = 65535 10.20.20.1 10.20.20.201 TCP TCP:Flags=…A..S., SrcPort=1745, DstPort=1173, PayloadLen=0, Seq=576250929, Ack=2944340195, Win=16384 (scale factor 0) = 16384 10.20.20.201 10.20.20.1 TCP TCP:Flags=…A…., SrcPort=1173, DstPort=1745, PayloadLen=0, Seq=2944340195, Ack=576250930, Win=65535 (scale factor 0) = 65535 Client configuration request: 10.20.20.201 10.20.20.1 TCP TCP:Flags=…AP…, SrcPort=1173, DstPort=1745, PayloadLen=1, Seq=2944340195 - 2944340196, Ack=576250930, Win=65535 (scale factor 0) = 65535 Client sending a TCP FIN to close the connection: 10.20.20.201 10.20.20.1 TCP TCP:Flags=…A…F, SrcPort=1173, DstPort=1745, PayloadLen=0, Seq=2944340196, Ack=576250930, Win=65535 (scale factor 0) = 65535 2. Using File Monitor to Troubleshoot Firewall Client To better understand what the Firewall Client application was doing during the time of the issue, we used File Monitor from Sysinternals. When we launched Filemon and clicked on “Test Server” button, the log shows that the FwcAgent.exe process (Microsoft Firewall client) gets an “Access Denied” in the context of Local Service when trying to create a file under %systemdrive%\Documents and Settings\LocalService\Local Settings\Temp. Note: LocalService and sub folders are hidden by default in Windo
från GoogleLogga inDolda fältSök efter grupper eller meddelanden