I connect my computer via wired connection. I checked what you suggested but it was already set to as 1 week. Is there another solution or situation you may know of?
Ok, an issue with a wired connection indicates some form of connection problem either with the CGN3 to PC or possibly with the cable feed from the neighborhood node or possibly with the path down to the game server, which I suspect is located in the southern US.
1. Can you indicate what plan you are on and what your typical speedtest results are with the rogers and speedtest.net tests?
2. Can you have a look at the back of the CGN3 and see if the connected port LED is yellow / orange indicating a Gb/s interconnect rate with the pc, or if its green which indicates a 10/100 Mb/s connection. If it is green you will end up with throttled down data rates due to a CGN3 firmware bug. Read post 138 on the previous page for a little more explanation. Let us know what you observe for the port colour. If it is green, (10/100 Mb/s) I wonder if a side effect is momentary a loss of connectivity.
3. Can you have a look at the following post which shows my power levels and signal to noise ratios from my CGN3. Can you log into your CNG3, navigate to the DOCSIS WAN page and copy the downstream and upstream tables and paste them into this thread. Copy the tables only, not the IP Data and other data above the downstream table. Those tables will indicate whether or not you have a cable power level or signal to noise issue.
4. Lastly, can you determine what the game server address is and run a trace down to the game server. This will hopefully illustrate if there are any issues from you to the game server. To run the trace, open a command prompt and type in for example:
Or, you could type in an IP address instead of google.com What you should use if you can determine it, is the gaming server address. Here is a link to the WOW servers in case you are having an issue with WOW.
When the trace is complete you can copy the results by selecting the command prompt symbol at the upper left hand corner of the command prompt window and use the drop down menu to select.....edit.....select all and then once again to select ....edit....copy. At that point you can paste the results in the thread. Here is an example of a trace to the WOW Cyclone Reckoning server:
Tracing route to INTEL_CE_LINUX [184.108.40.206]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms INTEL_CE_LINUX [10.0.0.1]
2 21 ms 16 ms 19 ms INTEL_CE_LINUX [220.127.116.11]
3 13 ms 11 ms 15 ms INTEL_CE_LINUX [18.104.22.168]
4 28 ms 29 ms 29 ms so-4-0-0.gw02.ym.phub.net.cable.rogers.com [22.214.171.124]
5 25 ms 21 ms 19 ms INTEL_CE_LINUX [126.96.36.199]
6 15 ms 19 ms 29 ms ae53.edge1.Toronto2.Level3.net [188.8.131.52]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 35 ms 49 ms 41 ms ae-1-60.edge3.NewYork1.Level3.net [184.108.40.206]
11 43 ms 51 ms 47 ms att-level3.newyork1.level3.net [220.127.116.11]
12 154 ms 109 ms 109 ms cr1.n54ny.ip.att.net [18.104.22.168]
13 103 ms 103 ms 105 ms cr2.cgcil.ip.att.net [22.214.171.124]
14 101 ms 103 ms 109 ms cr1.cgcil.ip.att.net [126.96.36.199]
15 108 ms 99 ms 109 ms cr2.dvmco.ip.att.net [188.8.131.52]
16 105 ms 103 ms 109 ms cr1.slkut.ip.att.net [184.108.40.206]
17 101 ms 106 ms 104 ms cr2.la2ca.ip.att.net [220.127.116.11]
18 119 ms 110 ms 108 ms gar5.lsrca.ip.att.net [18.104.22.168]
19 105 ms 109 ms 109 ms 12-122-254-226.attens.net [22.214.171.124]
20 110 ms 109 ms 128 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [126.96.36.199]
21 105 ms 108 ms 117 ms paxonix-placeholder.lax1.attens.net [188.8.131.52]
22 100 ms 119 ms 111 ms INTEL_CE_LINUX [184.108.40.206]
Note the timeouts between hops 6 and 10 for Level 3 and the big jump in time for the returns from Level3 and AT&T. Its possible that your trace will indicate something similar, in which case it becomes a matter of knowing about it, and possibly contacting the gaming company to see if they can do anything about it. There isn't anything you can do if there is a path problem, but, if the gaming company receives enough complaints, maybe something can be done from their end.
Give that a go and paste in your results. Hopefully with a little more technical data, members here on the forum can help determine what the issue is.
I'm on the Fiber 150 plan. Another thing i have noticed is that in the morning till late afternoon, I would not have any issue, but at night, the problem will start happening.
yes I am using the CGN3. I had a router connected before and thougt that it may have been the problem, however even with out the router the problem still occurs. If you have any idea on how i may be able to fix this i would be very happy.
Just got this modem last week, was using the SMC modem before, be honest I liked the SMC better! The Advanced modem sucks for wifi coverage, I have to be within 20 feet or less to get a decent connection for my laptop.... my basement 25 feet away from modem and weak signal, .... never had a problem with the SMC modem, could even connect when in my backyard. But switching to Fibre 60 they said I had to exchange modems.... otherwould I wouldn't have bothered.