Hmm. This is one thing I am not getting at all. Why the heck does UPnP have to be "active" in Windows? I mean, if you are using it as part of a firewall, where the firewall needs to let people/things through, then OK, but I would presume that most people use better firewalls than that, and can be more selective about if/when a port is open. A modem/router is "not" part of the OS. The OS doesn't have any control over its UPnP services "period". With a modem, maybe that would be different, but still not likely, since most modems are on the "other side" of a router, and are not directly connected to the machine, so having a "driver" for them makes no sense either, which means Windows isn't going to be using its UPnP to tell the modem's UPnP anything.
Do you see my point? Why does Windows even have UPnP, when those types of services are better handled by the firewall systems in the routers/modems? The only place I can see it making sense is if you are running your machine as a server on a network, with the intent of having *it* act as one of the routers. Otherwise... It just doesn't make any sense to me why you need NAT traversal services on the physical machine you are using, when the *machine* itself isn't even doing the NAT services or traversal. But yeah. Having it on by default is just stupid, especially in like 90% of all cases where its redundant in the first place. Like on *most* people's networks. |