Unless the router is physically inside of your computer, it cannot access the process list so it can't verify the integrity of the application name as it needs to be able to access the NDIS interface in order to find socket descriptors bound to windows processes.

In other words, stop wasting your time on something so trivial, it's just an identifier for a single instance of a forwarding rule.

Since you blurred off your IP address, I assume that you took your public IP (something that doesn't look like 192.168.n.n or 10.0.n.n) and stuck that into the IP field. Your router doesn't go through a public DNS server to resolve internal host names, so it'll never find that public IP, which is the identifier for your router. Do an ipconfig and check for something like this:


take the bolded IP and put it in the inbound ip address. Then go to your windows firewall and either disable it or make an exception rule with the following parameters:

Inbound/Outbound: allow via port, udp, 36963, all networks

Note that even with this, you may still not be able to accept arbitrary incoming packets. If this is the case, then understand that your wireless router is too stingent and just disconnect it and just use the modem.