Netgear router problem with wifi only (LAN Ok)

Specific forum for all wireless related issues. Even if you have a wireless router, only post here if you have a question about issues with the wireless functionality of it. Questions about wireless access points, cards, hot-spots etc. are also welcome here.
Post Reply
nadeaa0a
Newbie
Newbie
Posts: 1
Joined: Tue Feb 19, 2013 7:19 am

Netgear router problem with wifi only (LAN Ok)

Post by nadeaa0a » Tue Feb 19, 2013 7:40 am

Good Day All,

So i have a cable modem (Netgear CG3000D-RG) that has been working perfectly for the past six months until last month.

The router works perfectly when using the LAN cable but becomes very laggy when using wifi. The ping test on wifi is almost 264ms and only 16ms on LAN cable.

Video streaming is a pain in the butt. :(

Tried resetting the router with no benefits at all.

What is weird is the event log. It shows some critical errors on it.

You can find below the event log from the router in addition to the report from the router diagnostic software.

Router event log:

Time Priority Description
Mon Feb 18 22:03:24 2013 Notice (6) TLV-11 - unrecognized OID;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 18 21:40:48 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 18 13:13:03 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 18 01:45:21 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Sun Feb 17 13:49:29 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Sun Feb 17 01:54:21 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 16 13:53:31 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 16 01:55:54 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 15 13:41:21 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 15 01:36:46 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 14 13:55:07 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 14 01:55:45 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Wed Feb 13 13:53:10 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Wed Feb 13 01:52:19 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 12 13:36:49 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 12 01:52:08 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 11 13:45:34 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 11 01:54:10 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Sun Feb 10 13:43:37 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Sun Feb 10 01:32:18 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 09 21:54:35 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 09 17:56:21 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 09 13:41:03 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 09 11:57:47 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 09 01:34:41 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 08 17:31:20 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 08 13:56:29 2013 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.0;CM-VER=3.0;
Fri Feb 08 13:55:48 2013 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Feb 08 13:55:42 2013 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.0;CM-VER=3.0;
Fri Feb 08 13:52:18 2013 Critical (3) DHCP FAILED - Request sent, No response;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.0;CM-VER=3.0;
Fri Feb 08 13:49:21 2013 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=84:1b:5e:19:d7:a8;CMTS-MAC=00:12:d9:54:a0:14;CM-QOS=1.0;CM-VER=3.0;



and this is the log from the software:

Router Diagnostic | https://www.routertech.org - v1.3.3 - 18/02/2013 22:14:06

Ping 192.168.0.1 = PASS

Windows IP Configuration

Host Name . . . . . . . . . . . . : Ahmad
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Hosted Network Virtual Adapter
Physical Address. . . . . . . . . : X-X-X-X-X-X
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : X-X-X-X-X-X
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : X-X-X-X-X-X
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6235
Physical Address. . . . . . . . . : X-X-X-X-X-X
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::311c:b37f:5c0:8ec1%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, February 18, 2013 9:07:27 PM
Lease Expires . . . . . . . . . . : Monday, February 18, 2013 11:12:27 PM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 264537352
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-8C-2E-DD-C4-85-08-0A-58-16
DNS Servers . . . . . . . . . . . : 68.105.28.11
68.105.29.11
68.105.28.12
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{63FED929-B66B-40F2-8AD1-E3A907A3635E}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:3096:10be:9d4f:fdad(Preferred)
Link-local IPv6 Address . . . . . : fe80::3096:10be:9d4f:fdad%17(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 469762048
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-8C-2E-DD-C4-85-08-0A-58-16
NetBIOS over Tcpip. . . . . . . . : Disabled

******************************************
File not found!
******************************************
Ping 216.239.59.104 = FAIL [ip req timed out]
Ping www.google.com (74.125.227.147) = ip success



******************************************
File not found!
******************************************
Diagnostic page timed out with no refresh





Can you please help me!
Attachments
NETGEAR Gateway.pdf
(90.04 KiB) Downloaded 341 times
duke
Regular
Regular
Posts: 61
Joined: Mon Nov 26, 2012 7:03 pm

Re: Netgear router problem with wifi only (LAN Ok)

Post by duke » Tue Feb 19, 2013 4:24 pm

:idea: hello

are you using iptv ? -> contact tech support

if not
your modem is trying to
https://secure.dslreports.com/faq/power ... tions#8560

it is a common problem see
http://www.cableforum.co.uk/board/12/33 ... nging.html

https://secure.dslreports.com/forum/r26 ... ce-ranging

A T3 error is an indication of a potential return path or upstream issue. A colelction of these, large in number, can point to either a local fault or a problem further up the line on the network.

:damnall: Basically a cable modem gets online this way:

The modem scans for a digital QAM channel (which can be digital TV or modem downstream channels) and "listens" for upstream channel descriptor (UCD) information on it (which is only found on modem downstream channels). If it doesn't get the UCD after a few seconds of receiving data on that channel, a T1 timeout occurs and the modem looks for another digital QAM channel.

Once the modem finds the correct downstream channel and receives the upstream channel descriptor, it then waits for its initial opportunity to "talk" to the CMTS. If it doesn't get that chance within 12 seconds, a T2 timeout occurs.

So during initial modem connections, T1 and T2 timeouts are perfectly normal to see in the modem logs.

After locating a downstream data carrier channel, the modem gets its chance to "talk" to the CMTS and sends data to negotiate the proper upstream signal levels and timing. This negotiation process takes several data exchanges between the cable modem and the CMTS. If at any point the modem doesn't receive a response from the CMTS within about 200 milliseconds, a T3 timeout occurs. Several T3s have to occur before a modem resets.

The modem then goes through the DHCP, TFTP, TOD processes and once all are completed the modem is online.

Once the modem is online, the CMTS sends "Periodic Ranging" or keep-alive requests to it every 30 seconds. If the modem doesn't receive one, a T4 timeout occurs. Once 16 of the T4 timeouts have to occurred, a modem resets.

If there is a downstream communication problem, the cable modem might not receive these "keep-alive requests". If the upstream utilization is too high, or too many modems are connected to the same upstream port, it is possible that some modems will not get the required bandwidth or transmit opportunities to respond to the keep-alive requests. Either of these issues can result in T3 or T4 timeouts occurring.
Post Reply