Windows xp firewall.log path

Cancel Submit. In reply to Joe Schmoecher's post on June 27, I stated the path in my first reply. In gpedit. You can enable them on Success, Failure, both, or no auditing at all. Turn all the auditing off and you won't record anything in your log file. As the saying goes In the Event Viewer, simply right-click on the "System", "Applicaiton", or "Security" entry in the left column and select "Properties".

You can have as many rules as you have applications that need one. If your application needs a different port open, say port for Remote Desktop, then use the appropriate port. Click OK to close the Firewall window and save your settings. Remember that the more holes you create here, the more potential you create for someone to access your machine from the Internet. And Thank you for reading my post. Your email address will not be published.

Save my name, email, and website in this browser for the next time I comment. Skip to content. Share this on Leave a Reply Cancel reply Your email address will not be published. Tried this in my environment with similar results.

Taking a look at this TechNet discussion , it appears that option doesn't actually map to a real setting. The correct key to enable logging appears to be:. While this is odd, I believe I can offer an explanation for this behavior. Logging was an option in XP SP2, as show by the compatibility list on that policy:. Most likely, Microsoft just didn't want to break the forward compatibility on this existing setting, and instead, just disabled the corresponding checkbox in the newer GUI configuration.

You may still need to configure the other options aside from the logging locations in order for logging to function properly. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?

Learn more.