Error Reporting: firewall outbound rule
Hi, I have blocked outbound connections in the Windows firewall and allowed individual apps setting different rules. I don't seem to be able to create a rule to allow Windows Error Reporting through the firewall. I have tried to allow svchost.exe + windows error reporting under services but it doesn't work. I have also tried to allow different files in the c:\Windows\System32 folder with no success... When I allow again outbound connections the Windows Error Reporting works again so I am sure I have to create a rule for that. Many thanks
July 12th, 2009 2:57pm

Have you tried to allow DWWIN.EXE outbound access through the firewall?Ray
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2009 10:49pm

Have you tried to allow DWWIN.EXE outbound access through the firewall?Ray
July 13th, 2009 10:49pm

Hi Ray, I have just tried allowing DWWIN.EXE but windows error reporting is still not connecting (same results with wermgr and WerFault...) Any other idea?
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2009 12:08am

I missed that you didn't allow the Windows Error Reporting Service outbound connections through the firewall.Use the following procedure to accomplish this.Create a new Outbound ruleChoose Custom Rule and click NextIn the program Dialog click the Customize buttonSelect Apply to this serviceSelect the Windows Error Reporting Service and click OkClick Next in de Program dialogClick Next in the Protocol and Ports dialogClick Next in the scope dialogSelect Allow the connection in the Action dialog and click NextClick Next in the profile dialogDefine a name for the rule and click FinishThis should allow the service outbound connectivity.Ray
July 14th, 2009 12:26am

I missed that you didn't allow the Windows Error Reporting Service outbound connections through the firewall.Use the following procedure to accomplish this.Create a new Outbound ruleChoose Custom Rule and click NextIn the program Dialog click the Customize buttonSelect Apply to this serviceSelect the Windows Error Reporting Service and click OkClick Next in de Program dialogClick Next in the Protocol and Ports dialogClick Next in the scope dialogSelect Allow the connection in the Action dialog and click NextClick Next in the profile dialogDefine a name for the rule and click FinishThis should allow the service outbound connectivity.Ray
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2009 12:26am

I had tried that as well but I still get the error: "Problem connecting to the Windows Error Reporting service Some of the reports could not be uploaded to the Windows Error Reporting service. Please try again later" It must be something to do with the outbound rule as if I allow outbound connections on my Private profile I can send the report and I don't get that message... This thing is driving mad (regardless of the importance of sending this type of report!)!
July 14th, 2009 8:28pm

I understand your pain. I did not have the time to test this, but the Windows Errror reporting consists of the Service a number of DLLs and two executables. Did you try allowing both the Windows Error Reporting service, WerFault.exe and wermgr.exe outbound access through the firewall? There are no dependencies for the Error Reporting Services so I doubt there are any other processes or services involved.Just my 2 cents. Ray
Free Windows Admin Tool Kit Click here and download it now
July 15th, 2009 12:38am

I understand your pain. I did not have the time to test this, but the Windows Errror reporting consists of the Service a number of DLLs and two executables. Did you try allowing both the Windows Error Reporting service, WerFault.exe and wermgr.exe outbound access through the firewall? There are no dependencies for the Error Reporting Services so I doubt there are any other processes or services involved.Just my 2 cents. Ray
July 15th, 2009 12:38am

Hi Ray, Was off for few days so I have just managed to try it out now. Allowing the Windows Error Reporting service, WerFault.exe and wermgr.exe (3 different rules) doesn't seem to solve the problem unfortunately...
Free Windows Admin Tool Kit Click here and download it now
July 27th, 2009 7:51pm

Hi. I'm guessing that you've finally found a solution or work around by now, but for those who haven't I found that the problem, for me, was indeed the firewall settings. My work around was quite crude but it worked. I am running Windows 7 Professional and McAfee Security Center. I was getting the error described above: failed to connect to the error reporting service. in the Internet and Network Configuration pane Firewall Protection tab there is an advanced button. this lets you customize the security level select allow full access, check the action center for solutions to problems, and then select Allow outgoing access only.
November 11th, 2009 9:45pm

Thanks for the reply. I have not yet found a solution, at the moment I have to Allow all outgoing traffic to make it works... btw I am using windows firewall, I take the Internet and Network Configuration pane is in your McAfee? Thanks
Free Windows Admin Tool Kit Click here and download it now
November 11th, 2009 10:31pm

Allow explorer.exe (Windows Explorer) and it will work.
February 19th, 2010 11:58am

worked for me by following the above instructions on creating custom rules for the 3 services. It can now check for services.
Free Windows Admin Tool Kit Click here and download it now
November 28th, 2010 9:06am

My current Windows 7 installation is a week old. It's a clean install from a Windows 7 Ultimate x64 DVD with SP1 integrated. My firewall is unchanged, and as it came from Microsoft. Surely they wouldn't be so stupid as to block their own error reporting service in the firewall, would they? I can prove it's the firewall blocking the error reports because with the firewall on, I get "Problem connecting to the Windows Error Reporting service". Turn the firewall off, and the error reporting works flawlessly. Has somebody at Microsoft dropped the ball here? Surely there should be a pre-defined rule for error reporting, or at the very least a prompt to allow it the first time it tries to send a report?
March 18th, 2011 6:11pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics