tonyv Posted August 17, 2016 Share Posted August 17, 2016 can somebody help me... i have tried to get my netduma working all morning.. it will not connect to the cod servers.. but when i try my att wifi or hardwire it works just fine.. but will not when i try to hard wire it with my netduma.. this is the first time i have had this problem. i have tried disabling the host filter.. reboot netduma.. and unplug netduma for 20 sec .. nothing is working... help!! Link to comment Share on other sites More sharing options...
nffcbaz72 Posted August 17, 2016 Share Posted August 17, 2016 Have you widened your radius in the geo-filter so it hits the servers?? Link to comment Share on other sites More sharing options...
Scrizzy Posted August 17, 2016 Share Posted August 17, 2016 XBL or PSN? Does the system get online, but just can't connect to COD? And you're sure the COD servers were not having issues? When you say you can't connect, what do you mean specifically? You can't find a game or cant even search for one or what? Have you tried other multiplayer games? Do they connect successfully? Was the IP for the console static? If not, the necessary ports (3074, 3075 in particular) may not be open or may be reserved for the wrong IP as the console IP address may have changed? See if the IP for the console and the IP for the port reservations match. If not, clear the UPnP and or Port Forwarding rules and put them in under the correct IP address. Then try rebooting and connecting again. Keep the geofilter disabled while testing Could be a number of things. Start by answering the above questions. This may begin to narrow down the source of the problem. Others, including an admin, can then follow up with you. Doesn't sound like a complicated problem. It should be resolved quickly once the issue is identified. Good luck. Link to comment Share on other sites More sharing options...
tonyv Posted August 17, 2016 Author Share Posted August 17, 2016 hi guys thanks.. well i mean i cannot connect to multiplayer at all with the netduma... but i can if i use my att connections instead.. an yes i have widen the go filter to about half the united states...i have not changed any settings at all so i don't know why i would have to do any port forwarding when it was working just fine yesterday.. ??? Link to comment Share on other sites More sharing options...
Dennis Pantalone Posted August 17, 2016 Share Posted August 17, 2016 You have to uncheck auto cloud and bleeding edge cloud and then you can pick the numbers. Set them to 1,1,1 and hit apply. Then see if it works normally. The geo-filter seems to work with the untick of bleeding edge cloud and auto cloud. It is definatly a solution for now. A better one than the untick of the geo filter Link to comment Share on other sites More sharing options...
Zennon Posted August 17, 2016 Share Posted August 17, 2016 Fraser has replied to another user with this possible fix..... please un tick bleeding & auto cloud in settings > miscellaneous and manually choose these: 21 14 25 Link to comment Share on other sites More sharing options...
Zennon Posted August 17, 2016 Share Posted August 17, 2016 Activision must have changed the IP's on the match making server a work around is to turn the geo filter off reboot the console and wait until you have the game booted and are in multi player then turn on the geo. Link to comment Share on other sites More sharing options...
secretface Posted August 17, 2016 Share Posted August 17, 2016 I had this problem last night on bo3 and aw. I think my consol just needed a restart after whatever updates and crap lagdovision did. I would try a restart. My consol connected to the internet fine btw Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 18, 2016 Administrators Share Posted August 18, 2016 Please see this thread regarding the issue: http://forum.netduma.com/topic/17880-cant-connect-to-games-nat-errors-etc-workaround-fixes/ Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.