Welcome to Netduma Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!
put it into dmz while the console is off, reboot netduma and then reboot console and see if that works. If it does then factory reset the netduma and reinput the ports as you did before and then when all setup test it again.
if successful then factory reset the netduma and then once you have everything as you want it create a profile so if you factory reset in the future all your settings are saved bud!
theres no photo's at all! either use upnp or port forwarding, not both at the same time. It is quite easy to open ports in port forwarding and forget to disable upnp. So do the following if you want to use upnp:
disable upnp and apply, then, enable upnp and apply. Do both these steps while your xbox is turned off and then turn console on after you have done those steps.
Also is your netduma behind another router/modem or is it connected directly to a modem and the duma is connecting via pppoe?
The more infor about your network setup the easier it will be to diagnose!
Thanks alot guys...I'll check out pingplotter tonight when I get home from work. one more question though....using pingplotter and say my ping is higher then I want...do you still use the CC to bring it down like you would on dslreports? or is it just a straight tell you what your line is doing?
your ping is your ping, you cannot reduce your base ping. The cc's are to control network congestion and to give your other devices a bit of buffer room (not bufferbloat)
the problem is with dslreports you are connecting to and relying on their servers where as pingplotter you can see the route from you modem to it's final destination and will show you your line quality.
the servers have been going off n on most of the day, this causes the 60hz tick rate to go out the window as it puts you on a p2p game and it drops to about 20 - 30hz but deffo not 60hz. It got so bad earlier that none of the cods would connect online at all.
using dsl reports is highly inaccurate as you are relying on their servers and that they are running as they should be. You would be better using pingplotter to actually test your connection direct from your modem to an ip address such as bbc, twitter or google and monitor your line for jitter (bufferbloat) which is extremely accurate!
I can have a bufferbloat of A+ and run the same test a minute later and get an A or a B with dslreports!