should work fine as it is. It also works on my Win 7 Pro machine, and has reportedly worked on Windows XP.
One right way to do that is to have the Windows Firewall turned ON and running with recommended settings. If you mess with your firewall settings, chances are you've turned Windows' UPnP support off entirely.
Also, if your computer has two network interfaces that are both connected (e.g. a PC with an Ethernet cable and a WLAN connection), UPnP can't work and thus selecting the option won't help either (I'm searching for a workaround there, but I think it's a design flaw in Windows' NATUPnP implementation).
I have a bunch of ideas but the whole feature will have to stay experimental for a while.
The problem is, it's impossible to autodetect what users need, and the more options I give them, the more they are going to screw up. Even worse, I've seen people who were able to play PERFECTLY screw up their settings by turning on UPnP (which then makes their router trip over its own, perfectly set up port forwardings or NAT tables).
Why? Whyyyyy? Don't try to fix anything if it ain't broke, people. Seriously. ![Crying or Very Sad :cry:](/images/smilies/icon_cry.gif)
Statistics: Posted by thygrrr — 26 Mar 2012, 11:29
]]>