CRC error after an hour working and internet not working anymore
Hello everyone
I have TD-W8961N
I had many issues in using ADSL at home with this device, we changed the device and after a week our internet was disconnected,
the problem was about the CRC error, After an hour modem was ON, and I saw the crc was about 1000 or above, and my ping to 1.1.1.1 or 4.2.2.4 was timed out!
I had to reboot the modem from the web console so after 2 minutes it worked until it crashed again,
Now I I borrowed another modem, and after 3 days, I'm still connected with no issues,
Would you please tell me how should I fix this?
Why it is generating CRC error?
*Note: I did not change anything in my environment, except the modem, so the phone cable, spliter and ... are the same.
*I upgrade to the latest firmware but still have a problem with
Thanks for this froum
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, when the issue happens, is ADSL status and Internet status still show up? all client devices lose internet access at the same time, right?
Please share with us the screenshot of the whole Status page and also the system log file
- Copy Link
- Report Inappropriate Content
@Sunshine Yes, Exactly
I connected my modem again and removed the new modem, now the crc is around 27 after 6 hours of working
But in my ping, I see lots of Lost packet
I let you know about this
Thanks
- Copy Link
- Report Inappropriate Content
This is it:
12/16/2023 1:25:40> dns2str too long 33 12/16/2023 1:25:40> dns2str too long 0 12/16/2023 1:25:40> dns2str too long 37 12/16/2023 1:25:40> dns2str too long 164 12/16/2023 1:25:40> dns2str too long 55 12/16/2023 1:25:40> dns2str too long 36 12/16/2023 1:25:40> dns2str too long 30 12/16/2023 1:25:40> dns2str too long 19 12/16/2023 1:25:40> dns2str too long 66 12/16/2023 1:25:40> dns2str too long 31 12/16/2023 1:25:40> dns2str too long 43 12/16/2023 1:25:40> dns2str too long 33 12/16/2023 1:25:40> dns2str too long 18 12/16/2023 1:25:40> dns2str too long 4 12/16/2023 1:25:40> dns2str too long 14 12/16/2023 1:25:40> dns2str too long 25 12/16/2023 1:25:40> dns2str too long 19 12/16/2023 1:25:40> dns2str too long 0 12/16/2023 1:25:40> dns2str too long 31 12/16/2023 1:25:40> dns2str too long 30 12/16/2023 1:25:40> dns2str too long 20 12/16/2023 1:25:40> dns2str too long 45 12/16/2023 1:25:40> dns2str too long 10 12/16/2023 1:25:40> dns2str too long 4 12/16/2023 1:25:40> dns2str too long 12 12/16/2023 1:25:40> dns2str too long 7 12/16/2023 1:25:40> dns2str too long 21 12/16/2023 1:25:56> netMakeChannDial: err=-3000 rn_p=8046a7d8
- Copy Link
- Report Inappropriate Content
This log blog restarting the modem
1/1/2000 0:1:41> ADSL: UP 1/1/2000 0:1:42> netMakeChannDial: err=-3000 rn_p=8046a7d8 1/1/2000 0:1:42> MPOA Link Up 1/1/2000 0:1:42> PPPoE: Send PADI 1/1/2000 0:1:44> Last errorlog repeat 1 Times 1/1/2000 0:1:44> netMakeChannDial: err=-3000 rn_p=8046a7d8 1/1/2000 0:1:49> Last errorlog repeat 4 Times 1/1/2000 0:1:49> PPPoE: Send PADI 1/1/2000 0:1:49> PPPoE: Recieve PADO 1/1/2000 0:1:49> PPPoE: Send PADR 1/1/2000 0:1:49> PPPoE: Recieve PADS 1/1/2000 0:1:49> PAP Authentication Successful 1/1/2000 0:1:49> ppp_ready: ch:804c1f04, iface:803ea98c 1/1/2000 0:1:49> netMakeChannDial: err=-3000 rn_p=8046a7d8 1/1/2000 0:1:49> PPP get IP Address:188.253.67.167 1/1/2000 0:1:49> PPP gateway:5.202.112.165 1/1/2000 0:1:49> PPP subnetmask:255.255.255.255 1/1/2000 0:1:49> PPP primary DNS:5.202.100.100 1/1/2000 0:1:49> PPP secondary DNS:5.202.100.101 1/1/2000 0:1:49> SNMP TRAP 3: link up 1/1/2000 0:1:49> Accept() fail 1/1/2000 0:1:50> Last errorlog repeat 1 Times 1/1/2000 0:1:50> netMakeChannDial: err=-3000 rn_p=8046a7d8 1/1/2000 0:2:10> Last errorlog repeat 17 Times 1/1/2000 0:2:10> sending request to NTP server(85) 1/1/2000 0:2:10> received from NTP server(85) 12/16/2023 11:6:43> Adjust time to 657d84c3 12/16/2023 11:6:43> adjtime task pause 1 day
- Copy Link
- Report Inappropriate Content
1/1/2000 0:1:42> netMakeChannDial: err=-3000 rn_p=8046a7d8 1/1/2000 0:1:42> MPOA Link Up 1/1/2000 0:1:42> PPPoE: Send PADI 1/1/2000 0:1:44> Last errorlog repeat 1 Times 1/1/2000 0:1:44> netMakeChannDial: err=-3000 rn_p=8046a7d8 1/1/2000 0:1:49> Last errorlog repeat 4 Times 1/1/2000 0:1:49> PPPoE: Send PADI 1/1/2000 0:1:49> PPPoE: Recieve PADO 1/1/2000 0:1:49> PPPoE: Send PADR 1/1/2000 0:1:49> PPPoE: Recieve PADS 1/1/2000 0:1:49> PAP Authentication Successful 1/1/2000 0:1:49> ppp_ready: ch:804c1f04, iface:803ea98c 1/1/2000 0:1:49> netMakeChannDial: err=-3000 rn_p=8046a7d8 1/1/2000 0:1:49> PPP get IP Address:188.253.67.167 1/1/2000 0:1:49> PPP gateway:5.202.112.165 1/1/2000 0:1:49> PPP subnetmask:255.255.255.255 1/1/2000 0:1:49> PPP primary DNS:5.202.100.100 1/1/2000 0:1:49> PPP secondary DNS:5.202.100.101 1/1/2000 0:1:49> SNMP TRAP 3: link up 1/1/2000 0:1:49> Accept() fail 1/1/2000 0:1:50> Last errorlog repeat 1 Times 1/1/2000 0:1:50> netMakeChannDial: err=-3000 rn_p=8046a7d8 1/1/2000 0:2:10> Last errorlog repeat 17 Times 1/1/2000 0:2:10> sending request to NTP server(85) 1/1/2000 0:2:10> received from NTP server(85) 12/16/2023 11:6:43> Adjust time to 657d84c3 12/16/2023 11:6:43> adjtime task pause 1 day 12/16/2023 11:6:57> netMakeChannDial: err=-3000 rn_p=8046a7d8
- Copy Link
- Report Inappropriate Content
When Tp-Link is connected to the line, it shows the SNR 15/14
But when Dlink connected, it showed the SNR 10/11
With tp-link I just connected under 72 hours but with dlink there is no limitation or disconnecting from internet
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 833
Replies: 6
Voters 0
No one has voted for it yet.