Wireless Connection dropped

[macgyver2]

Not to confuse you or anything but it would show that its part of the issue, it could still be your cable modem. Further testing would be needed from what I can tell. Like resetting the router to default settings. Taking stuff like a router out of the loop just shows where the issue is finding the cause after that is the fun part and takes more testing to trouble shoot.

 

[macgyver2]

well now that i want it to disconnect so I can track the problem at least on my end I can't get it to happen. I don't know if unpluggin the modem 3 times now has fixed it, or taking the router out for a connection fixed it. Plus I have not heard worked if road runner internet has any connection issues in my area.

So how is the testing going on your end?

 

[TastyFood]

I connected my comp to the modem directly and the internet is working perfectly fine. So, I guess the problem is with the router? right? I either got to find whats wrong with the router or buy a new one.

 

[macgyver2]

Well I just found out that my cable modem was connected to the power supply from my router. they were both 12v 1.0A but my modems receive power level went from 2dBmV to 5.5dBmV so I think I found my issue. or at least part of it. still have to test if the router will work now that I have the power issue out of my way.

to see some cable modem stats type 192.168.100.1 into your web browser. I get a status screen about my modem and the power levels. It also auto refreshes in a window for me.

 

[macgyver2]

unplug your router for about 30 seconds, also look for a reset button before you connect it again to see if the problem returns. if it returns then yes your router is the issue and fixing it or get a new one. If it doesn't return well there could be many things that caused it. If you have custom settings in your router and if when re-connected the issue is still gone then redo your settings one at a time to see if they cause any issue.

 

[TastyFood]

Thanks macgyver2 for your help, as well as everybody! . I'll let you know if its fixed, or else I'll probably end up buying a new router.

 

[TastyFood]

Logs
The Logs Page provides diagnostic messages generated by the Cable Modem. It is intended for use by a qualified technician.



[FONT=Arial,Helvetica] Status[/FONT] [FONT=Arial,Helvetica] Signal[/FONT] [FONT=Arial,Helvetica] Addresses[/FONT] [FONT=Arial,Helvetica] Configuration[/FONT] [FONT=Arial,Helvetica] Logs[/FONT] [FONT=Arial,Helvetica] Help[/FONT] [FONT=Arial,Helvetica]Time[/FONT] [FONT=Arial,Helvetica]Priority[/FONT] [FONT=Arial,Helvetica]Code[/FONT] [FONT=Arial,Helvetica]Description[/FONT] 1970-01-01 00:01:143-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.1970-01-01 00:01:033-CriticalR002.0No Ranging Response received - T3 time-out (US 2)1970-01-01 00:00:573-CriticalR002.0No Ranging Response received - T3 time-out (US 4)1970-01-01 00:00:413-CriticalR004.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o1970-01-01 00:00:093-CriticalR002.0No Ranging Response received - T3 time-out (US 2)1970-01-01 00:00:163-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.1970-01-01 00:00:026-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 23:10:226-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 23:10:206-NoticeM571.4Ethernet link dormant - not currently active2010-11-06 23:09:446-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 23:09:426-NoticeM571.4Ethernet link dormant - not currently active2010-11-06 22:49:086-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 22:49:066-NoticeM571.4Ethernet link dormant - not currently active2010-11-06 22:48:326-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 22:48:306-NoticeM571.4Ethernet link dormant - not currently active2010-11-06 22:27:446-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 22:27:426-NoticeM571.4Ethernet link dormant - not currently active2010-11-06 22:27:086-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 22:27:066-NoticeM571.4Ethernet link dormant - not currently active2010-11-06 22:09:066-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 22:09:046-NoticeM571.4Ethernet link dormant - not currently active2010-11-06 21:47:366-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 21:47:326-NoticeM571.4Ethernet link dormant - not currently active2010-11-06 21:46:586-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 21:46:566-NoticeM571.4Ethernet link dormant - not currently active2010-11-06 21:37:126-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 21:37:106-NoticeM571.4Ethernet link dormant - not currently active2010-11-06 21:36:346-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 21:29:386-NoticeM571.4Ethernet link dormant - not currently active2010-11-06 16:17:046-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 16:17:006-NoticeM571.4Ethernet link dormant - not currently active2010-11-06 16:16:266-NoticeM571.1Ethernet link up - ready to pass packets2010-11-06 16:16:106-NoticeM571.4Ethernet link dormant - not currently active2010-11-06 02:11:505-WarningD103.0DHCP RENEW WARNING - Field invalid in response2010-11-01 21:38:526-NoticeM571.1Ethernet link up - ready to pass packets2010-11-01 21:38:506-NoticeM571.4Ethernet link dormant - not currently active2010-11-01 02:11:505-WarningD103.0DHCP RENEW WARNING - Field invalid in response2010-10-27 00:01:566-NoticeM571.1Ethernet link up - ready to pass packets2010-10-27 00:01:546-NoticeM571.4Ethernet link dormant - not currently active2010-10-25 14:20:506-NoticeM571.1Ethernet link up - ready to pass packets2010-10-25 14:20:486-NoticeM571.4Ethernet link dormant - not currently active1970-01-01 00:00:143-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.1970-01-01 00:00:026-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:036-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:153-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.1970-01-01 00:01:433-CriticalD001.0DHCP FAILED - Discover sent, no offer received1970-01-01 00:01:113-CriticalR002.0No Ranging Response received - T3 time-out (US 2)1970-01-01 00:00:553-CriticalR004.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o1970-01-01 00:00:336-NoticeM571.1Ethernet link up - ready to pass packets1970-01-01 00:00:316-NoticeM571.4Ethernet link dormant - not currently active1970-01-01 00:00:233-CriticalR005.0Started Unicast Maintenance Ranging - No Response received - T3 time-out1970-01-01 00:00:063-CriticalR002.0No Ranging Response received - T3 time-out (US 2)1970-01-01 00:00:026-NoticeM571.1Ethernet link up - ready to pass packets2010-10-22 06:11:453-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.2010-10-22 06:11:423-CriticalD001.0DHCP FAILED - Discover sent, no offer received2010-10-22 06:10:383-CriticalR002.0No Ranging Response received - T3 time-out (US 2)2010-10-22 06:10:313-CriticalR002.0No Ranging Response received - T3 time-out (US 4)2010-10-22 06:10:183-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:10:176-NoticeM572.0T1 No Ucd Timeout - Reinitialize MAC...2010-10-22 06:10:173-CriticalU001.0No UCD's Received - Timeout2010-10-22 06:10:073-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:10:073-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2010-10-22 06:10:063-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:10:056-NoticeM572.0T1 No Ucd Timeout - Reinitialize MAC...2010-10-22 06:10:053-CriticalU001.0No UCD's Received - Timeout2010-10-22 06:09:553-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:09:553-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2010-10-22 06:09:543-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:09:546-NoticeM572.0T1 No Ucd Timeout - Reinitialize MAC...2010-10-22 06:09:543-CriticalU001.0No UCD's Received - Timeout2010-10-22 06:09:443-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:09:433-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2010-10-22 06:09:433-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:09:436-NoticeM572.0T1 No Ucd Timeout - Reinitialize MAC...2010-10-22 06:09:433-CriticalU001.0No UCD's Received - Timeout2010-10-22 06:09:323-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:09:323-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2010-10-22 06:09:323-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:09:316-NoticeM572.0T1 No Ucd Timeout - Reinitialize MAC...2010-10-22 06:09:313-CriticalU001.0No UCD's Received - Timeout2010-10-22 06:09:213-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:09:213-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2010-10-22 06:09:203-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:09:206-NoticeM572.0T1 No Ucd Timeout - Reinitialize MAC...2010-10-22 06:09:203-CriticalU001.0No UCD's Received - Timeout2010-10-22 06:09:093-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:09:093-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2010-10-22 06:09:083-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:09:086-NoticeM572.0T1 No Ucd Timeout - Reinitialize MAC...2010-10-22 06:09:083-CriticalU001.0No UCD's Received - Timeout2010-10-22 06:08:573-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:08:573-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2010-10-22 06:08:573-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:08:576-NoticeM572.0T1 No Ucd Timeout - Reinitialize MAC...2010-10-22 06:08:573-CriticalU001.0No UCD's Received - Timeout2010-10-22 06:08:463-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2010-10-22 06:08:456-NoticeM572.0Current Ds Freq Not On Target List - Reinitialize MAC...1970-01-01 00:01:433-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.1970-01-01 00:01:363-CriticalD001.0DHCP FAILED - Discover sent, no offer received1970-01-01 00:00:583-CriticalR002.0No Ranging Response received - T3 time-out (US 1)

 

[TastyFood]

Well I just found out that my cable modem was connected to the power supply from my router. they were both 12v 1.0A but my modems receive power level went from 2dBmV to 5.5dBmV so I think I found my issue. or at least part of it. still have to test if the router will work now that I have the power issue out of my way.

to see some cable modem stats type 192.168.100.1 into your web browser. I get a status screen about my modem and the power levels. It also auto refreshes in a window for me.

So can these logs help identify what the problem is?

 

[macgyver2]

seeing a lot of failures in there as I don't know what all those mean it really sounds like its your modem from that log. those DHCP failures seem to be whats reseting your connection at least that would be my best guess from a quick read. If I can find what some of those codes are I might be able to see whats happening.

WarningD103.0DHCP RENEW WARNING - Field invalid in response2010-11-01 21:38:526-NoticeM571.1Ethernet link up

this looks like the modem is linking up with your router or the server it gets its IP not sure but either way its an issue that will keep your offline.
I had issues getting my router back online and so far now that the correct cords are connected on my end things seem to be working for now.

 

[TastyFood]

Everything has been working fine for the last couple of hours. Once again, thank you.

/end thread

 

[TastyFood]

OMG lol, the problem just came back, however the internet just stops working for like 30 seconds only. It's not really a big problem, I'll deal with it until I get a new router.

 

[SolarWind]

Before you think of buying one - Update the router firmware (available from your router manufactuerers website).

 

[SolarWind]

TRENDnet Downloads

 

[macgyver2]

my cable modem (oops wrote router) was showing a log like yours, I was able to get my internet provider to send a refresh and restart remotely and it seems to have cleared the issue. By the time we neared the end of our convo my connection would reset 2-3 times. While I waited to talk with my ISP my modem reset 24 times.

I couldn't keep the chat log since the connection was reset while in the middle of the chat but what ever they were able to send to the modem stopped the issues I was having with a log that looked pretty close to what you posted here.

So you might want to contact your service provider.

 

[tinytim1587]

brighthouse and roadrunner

there is not brighthouse internet. the internet brighthouse offers is called roadrunner so if you have internet through brighthouse then you have roadrunner.