Tried that and, of course, it doesn't work.Īll of that for a trivial, casual, card game that should just work.Īnd, of course, it all starts with that ridiculous, cryptic error message: 'For all traffic coming from a specific computer that's going to certain ports, make those ports static (i.e., don't remap them). 'For all traffic coming from certain ports on a specific computer, make the ports static (i.e., don't remap them' Adjusting for this game and my setup, I did that, and it still doesn't work.Īccording to that person, in addition to the outbound NAT firewall rule noted at the top of this, we also need an outbound NAT firewall rule that specifies the necessary ports in the Destination field.

In that, the author says, basically, you also have to set up a port forwarding rule saying the same thing. I found other stuff from games with the same issue. In this case, the certain ports are those Uplay and Uno need, and the specific computer is the static IP address of the computer you're playing on. But, in some cases, it breaks things.Īccording to that same page, the solution is to set up an outbound NAT firewall rule that says for all traffic coming from certain ports on a specific computer, make the ports static (i.e., don't remap them). In most cases, that shouldn't be a problem since the router will keep track of what port goes where. I'm pretty sure that means that the router/firewall randomly remaps the ports traffic goes over for a bit of security. Just for posterity, I'll put some of the stuff I found that is supposed to work, but didn't for me (I'm using pfSense, but maybe some of this can be adapted by others).įirst, here's what I think is happening with strict NAT:

99% of the world works just fine with standard 'strict NAT.' But, UbiSoft (Uplay) and this game, Uno, can't.

Ubisoft uno pc