bruistopher

UPDATE Fraser, I do you use Geo-Filter and it was enabled. And I didn't disable it when you told me to because I didn't go into the actual setting for whatever reason. I turned off "Strict Mode" instead of the "Filtering Mode" for my PC settings. I did disable the filtering for my PC just now and I was able to log into MW2 with no issues + with the NAT "open". But how do I re-enable Geo-Filter or when should I re-enable it for this game? It works fine for MW3. Should I turn it off when booting into MW2 and then turn it on once I'm in the game? UPDATE 2 Never mind. I answered my own question. Everything works now. Thanks, Fraser for the help!

Also if I connect the fiber ISP directly to my PC. I can have an open NAT with no problem and the issues when I switch to MW2 are not there anymore. So I'm thinking there is something with the communication between the fiber ISP router (primary) and the R3 (secondary). I still have the cable ISP modem and service active (I'm about to disconnect the service soon) and trial and error purposes I reconnected the R3 with that and I had no issues with open NAT on my PC. My fiber ISP is Verizon and the router they provided was a CR1000B. So the ONT has a ethernet cable going into the WAN port on that and I have a ethernet cable in the LAN port leaving the Verizon router going to the WAN port on the R3. I used Comcast previously as my cable ISP.

Just turned off Geo-Filter in the settings and it's doing the exact same thing. When I use the return back option to COD HQ from MW2. It produces the same error but in MW3. And when I try to boot up any other COD games from Steam after this error message. I have connecting issues to the games servers for those games. If I reboot the R3. The messages go away. But I have to do this every time. I didn't have this issue with the cable ISP modem. It just started now with the fiber ISP router. Also, when I check the port forwarding section in the R3 DumaOS webpage. It shows 3074 being active and then changes to inactive. I could just leave my NAT as "Moderate" and the issues will go away. But I really want to know why this is a issue all of a sudden. And I don't even know what "Socket Family Settings" mean.

Thanks, Fraser. I did the steps above and I'm still getting the error. The NAT is open on MW3 via PC (connected to R3 via Ethernet) with the ports above but I still run into the error when I try to open up MW2 within the COD HQ app on PC. If I turn my Xbox Series X (connected to R3 via Ethernet) the NAT is open and it shows up in the UPnP settings in my R3. But my PC doesn't.

Hello, I'm a R3 user. So I recently ran into an issue. I switched from my regional cable ISP to my regional telephone/fiber ISP and I'm trying to have an open NAT. I have the ISP ONT connected via ethernet going straight into the provided fiber ISP router and then from the ISP router going into the R3. But just recently I started receiving a "Invalid Socket Family Settings". It happens after I close the COD app to go to a different game within the COD HQ (MW2) or after an update. I could reset my R3 and I would be able to get into MW3. But I have to do that every time. The issue started after I switched to my fiber ISP. Now if I turn all the ports off or delete them on the ISP router and R3, my NAT goes back to moderate and the Call Of Duty games boot up as normal without the error message. My Xbox Series X and PlayStation 5 are hooked up to my R3 and are moderate (NAT) but don't have any issues with them. Those devices boot COD up fine. So I'm thinking it's either the ports I'm using on the fiber ISP provided router and R3 are incorrect or it's some setting on my PC that's wrong. I tried changing my DNS on my PC to 1.1.1.1 or 8.8.8.8 and that worked for a little but I still keep getting "Invalid Socket Family Settings" error message. The ports I have set up on the fiber ISP router and R3 are: TCP: 3074, 3075, 27015-27030, 27036-27037 UDP: 3074, 4380, 27000-27036 Any help would be appreciated. Thanks in advance and the R3 so far has been awesome.

Hello, Fraser. Could you add me also, please?

I wanted to try it out also pls

New to Netduma. Awesome device but I’m experiencing the same issue from wake up. Battle.net times out and I have to constantly type in my password from PC wake up. I hope we get a fix soon !