I have a Vista Ultimate box which includes the Windows Media Center. I also have an XBOX 360 which can act as a Windows Media Center Extender. In this configuration, all of my CDs, MP3s, and pictures can be viewed and played on the XBOX 360 in the living room while the files sit on the Vista box across the house. It's pretty cool - I'm happy. The network config. is Vista box and XBOX both hard wired through a router. Up until this week I was simply running Windows firewall. Everything worked great. Now I have ESS for a firewall, and well, not so great at first. The XBOX couldn't see or access the pc on the network. (Might this be a similar bug to that other thread where the guy is having problems with his network printer and ESS?) After giving things some thought, it crossed my mind that maybe the ESS bug is that it's "trusted zone" firewall rule might be "stuck." So let's see what happens if I go in and make a global firewall of my own (Git er done!) So I create a firewall rule to Allow all inbound and outbound UDP and TCP traffic. Then in the next part of setting up the rule I chose "Trusted Zone" from the remote box. My appalachian logic being, I want all traffic to flow freely within the trusted zone. Low and behold, everything works great on the network! XBOX 360 is most happy! All is well. Just to confirm I didn't just write a rule that killed the firewall, I then put the Vista box in the routers DMZ, went to www.pcflank.com and I had it throw all it's exploit and trojan tests at my ESS firewall. Nothing got past ESS. I disabled ESS and re-ran the tests and sure enough it reported my computer was not protected. So it would seem the firewall is in good shape. So, here's my question for you experts. While it seems I've solved the "trusted zone" issue, and the firewall is standing up to threat scans, can anyone think of a reason the firewall rule I wrote might in anyway make my PC unsafe? Am I possibly overlooking something or did I just find a good fix for my system?