Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

Other Features

Windows Firewall

One area where you can see a visible improvement is in the new Windows Firewall (Figure 6). The new firewall combines Vista with IPsec and provides management of both incoming and outgoing connections (in XP you could only manage incoming).

Windows Vista Firewall.

Figure 6: Windows Vista Firewall

Connection Security Status offers a wealth of connectivity functions, though, like everything else in Vista, they've all been given Disney names. This is probably the only place within Vista where you'll actually be able to see a real improvement instead of just a bunch of fancy new menus that are only going to slow you down.

I had been working with Vista for quite some time while preparing this article. So I decided to check out the firewall logs since I didn't see any kind of window where you could actually monitor firewall activity. The logs are located all the way at the bottom of the Windows Firewall main menu under "Monitoring."

Monitoring provides sort of an overview of your incoming and outgoing firewall connections. If you have a specific secure location (like a VPN tunnel or something.) then it can be displayed under "View active connection security rules".

The log file is right in the middle of the Monitoring window under "Logging Settings" and lists the file name C:\Windows\system32\firewall\pfirewall.log. But when I clicked it, I received a cheery C:\Windows\system32\firewall\pfirewall.log does not exist. Would you like to create this file?

Uh, yeah. And could you create the information that's supposed to be there from the past week or so of use while you're at it? I was (unpleasantly) surprised to find that the log does not keep track of dropped packets or successful connections by default, nor can you just turn them on from the Monitoring window. You have to return to the Windows Firewall main menu, select "Windows Firewall Properties" and turn them on from there. But when I did that... wonder oh wonders:


Why would turning on firewall logging actually turn the firewall off? Maybe it was just a fluke. But a hell of a fluke to run into if you're getting bombarded by unwanted connections and you want to turn on logging (which is the only way I see that you can find out where the hits are coming from).

More Stuff

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

I'm looking at buying a couple of new Asus AX routers. I was thinking on spending the extra money for the ROG Rapture GT-AX11000 but I see an awful lo...
The past few days the CPU temp is sitting ~80*C for no reason. The CPU load reports to be less than 10%, the only thing I can think of is that maybe t...
i have problem updating latest firmware Version Currently i have 6204 installed. i checked for new firmware and node has been update...
So today I noticed the LED's are all off. But the router still works perfectly. Did the LED'S just go out? Is there a fix for this?
Hi, just got a rapture AX11000 . Work mostly well with the exception on the connection to playfi speakers / harmony / hue. After a few minutes the rou...

Don't Miss These

  • 1
  • 2
  • 3