Windows Firewall UPnP exception bug?

[Guest]

I have a strange problem with Windows Firewall (I think). I set my Xbox 360
to connect to my Windows XP SP2 PC running Windows Media Connect 2.0 and all
works fine... except when I turn my Xbox 360 off and then on again, it can't
see my PC unless I uncheck the UPnP exception in Windows Firewall, save that
setting, then check it again and save. Suddenly, my PC is visible to the
Xbox 360 - the second I hit the OK button after re-enabling the UPnP
exception.

What's going on?

 

[Guest]

I have a strange problem with Windows Firewall (I think). I set my Xbox 360
to connect to my Windows XP SP2 PC running Windows Media Connect 2.0 and all
works fine... except when I turn my Xbox 360 off and then on again, it can't
see my PC unless I uncheck the UPnP exception in Windows Firewall, save that
setting, then check it again and save. Suddenly, my PC is visible to the
Xbox 360 - the second I hit the OK button after re-enabling the UPnP
exception.

What's going on?

Bump.

Can anyone help? I need to know is why disabling and re-enabling an
exception rule in Windows Firewall would suddenly reactivate a service,
without any errors ever showing in the event logs.

Is the packet filtering for UPnP in MS Firewall stateless or stateful?
Could it be that under certain circumstances, UPnP requests are ignored.
Maybe this is why disabling/reanabling the relevant rule (or restarting the
services) forces the firewall to see the requests?