Results 1 to 2 of 2

Thread: Comcast - Experiencing disconnect nearly every 20 min - using SBG900

  1. #1

    Comcast - Experiencing disconnect nearly every 20 min - using SBG900

    Hi all, using an SBG900 modem / gateway combo Im getting frequent internet drops with Comcast. Ill pull up my error info and signal info if itll help:

    Downstream Value

    Frequency 699000000 Hz Locked

    Signal to Noise Ratio 37.9 dB

    Power Level 12.1 dBmV
    The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading.

    HFC MAC Address 00:1E:46:E5:BC:B8



    Upstream Value

    Channel ID 4

    Frequency 36500000 Hz Ranged

    Power Level 49.7 dBmV


    Before a power cycle it was at:

    Downstream Value

    Frequency 699000000 Hz Locked

    Signal to Noise Ratio 38.0 dB

    Power Level 12.2 dBmV
    The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading.

    HFC MAC Address 00:1E:46:E5:BC:B8



    Upstream Value

    Channel ID 4

    Frequency 36500000 Hz Ranged

    Power Level 50.2 dBmV


    Other info is -

    2010-01-10 12:50:53 5-Warning P250.00 CAP unable to make C-NAPT mapping. No WAN IP address available

    2009-11-24 00:55:24 3-Critical D001.00 DHCP FAILED - Discover sent, no offer received

    2009-11-24 00:55:24 5-Warning P250.00 CAP unable to make C-NAPT mapping. No WAN IP address available

    2009-11-24 00:55:08 3-Critical D001.00 DHCP FAILED - Discover sent, no offer received

    2009-11-24 00:55:08 5-Warning P250.00 CAP unable to make C-NAPT mapping. No WAN IP address available

    2009-11-24 00:55:00 3-Critical D001.00 DHCP FAILED - Discover sent, no offer received

    2009-11-24 00:55:00 5-Warning P250.00 CAP unable to make C-NAPT mapping. No WAN IP address available

    2009-10-01 02:37:41 3-Critical D002.00 DHCP FAILED - Request sent, No response

    2009-10-01 02:37:34 3-Critical D001.00 DHCP FAILED - Discover sent, no offer received


    And -

    2010-01-10 12:50:55 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:11 3-Critical R002.00 No Ranging Response received - T3 time-out

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    2010-01-10 12:44:53 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:59 3-Critical R004.00 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

    1970-01-01 00:00:26 3-Critical R005.00 Started Unicast Maintenance Ranging - No Response received - T3 time-out

    1970-01-01 00:00:10 3-Critical R002.00 No Ranging Response received - T3 time-out

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    2010-01-10 12:30:15 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    Time Priority Code Message

    1970-01-01 00:00:11 3-Critical R002.00 No Ranging Response received - T3 time-out

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    2010-01-10 12:07:47 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    2010-01-08 01:25:25 3-Critical R004.00 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

    2010-01-07 18:58:32 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:43 3-Critical R004.00 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

    1970-01-01 00:00:11 3-Critical R002.00 No Ranging Response received - T3 time-out

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    2010-01-07 00:55:45 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:06 3-Critical X501.10 Operating in Gateway mode

    Time Priority Code Message

    2009-12-21 15:12:16 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    2009-12-13 15:25:52 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    2009-12-08 07:08:48 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:06 3-Critical X501.10 Operating in Gateway mode

    2009-11-24 12:35:27 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    2009-11-24 01:04:06 3-Critical R004.00 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

    2009-11-24 01:03:34 3-Critical R005.00 Started Unicast Maintenance Ranging - No Response received - T3 time-out

    2009-11-24 00:59:33 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    Time Priority Code Message

    2009-11-24 00:58:58 3-Critical R002.00 No Ranging Response received - T3 time-out

    2009-11-24 00:58:34 3-Critical R003.00 Init RANGING Critical Ranging Request Retries exhausted

    2009-11-24 00:58:34 3-Critical R002.00 No Ranging Response received - T3 time-out

    2009-11-24 00:57:56 3-Critical R004.00 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

    2009-11-24 00:57:24 3-Critical R005.00 Started Unicast Maintenance Ranging - No Response received - T3 time-out

    2009-11-24 00:56:29 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    2009-11-24 00:55:44 3-Critical R004.00 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

    2009-11-24 00:55:11 3-Critical R005.00 Started Unicast Maintenance Ranging - No Response received - T3 time-out

    2009-11-24 00:54:31 3-Critical R002.00 No Ranging Response received - T3 time-out

    2009-11-24 00:53:49 3-Critical R003.00 Init RANGING Critical Ranging Request Retries exhausted

    Time Priority Code Message

    2009-11-24 00:53:49 3-Critical R002.00 No Ranging Response received - T3 time-out

    2009-11-24 00:53:11 3-Critical R004.00 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

    2009-11-24 00:52:38 3-Critical R005.00 Started Unicast Maintenance Ranging - No Response received - T3 time-out

    2009-11-23 18:14:27 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:12 3-Critical R002.00 No Ranging Response received - T3 time-out

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    2009-11-22 12:06:30 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    2009-11-21 20:18:15 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    2009-11-20 03:08:54 3-Critical R002.00 No Ranging Response received - T3 time-out

    Time Priority Code Message

    2009-11-20 03:08:42 3-Critical T002.00 SYNC Timing Synchronization failure - Failed to acquire FEC framing

    2009-11-20 03:08:41 3-Critical R004.00 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

    2009-11-20 03:08:41 3-Critical T002.00 SYNC Timing Synchronization failure - Failed to acquire FEC framing

    2009-11-20 01:13:06 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    2009-11-11 01:13:15 3-Critical R004.00 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

    2009-11-10 21:10:39 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:06 3-Critical X501.10 Operating in Gateway mode

    2009-11-10 13:30:56 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:19 3-Critical D001.00 DHCP FAILED - Discover sent, no offer received

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    Time Priority Code Message

    2009-11-10 12:48:34 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:19 3-Critical R002.00 No Ranging Response received - T3 time-out

    1970-01-01 00:00:18 3-Critical U002.00 UCD invalid or channel unusable

    1970-01-01 00:00:13 3-Critical R002.00 No Ranging Response received - T3 time-out

    1970-01-01 00:00:12 3-Critical U002.00 UCD invalid or channel unusable

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    2009-11-10 12:46:34 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:01:06 3-Critical R002.00 No Ranging Response received - T3 time-out

    1970-01-01 00:01:05 3-Critical U002.00 UCD invalid or channel unusable

    1970-01-01 00:00:53 3-Critical R002.00 No Ranging Response received - T3 time-out

    Time Priority Code Message

    1970-01-01 00:00:52 3-Critical U002.00 UCD invalid or channel unusable

    1970-01-01 00:00:47 3-Critical R004.00 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

    1970-01-01 00:00:13 3-Critical R002.00 No Ranging Response received - T3 time-out

    1970-01-01 00:00:13 3-Critical U002.00 UCD invalid or channel unusable

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    2009-11-10 12:14:20 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:14 3-Critical R002.00 No Ranging Response received - T3 time-out

    1970-01-01 00:00:12 3-Critical U002.00 UCD invalid or channel unusable

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    1970-01-01 00:01:05 3-Critical R002.00 No Ranging Response received - T3 time-out

    Time Priority Code Message

    1970-01-01 00:01:03 3-Critical U002.00 UCD invalid or channel unusable

    1970-01-01 00:00:46 3-Critical R004.00 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

    1970-01-01 00:00:13 3-Critical R002.00 No Ranging Response received - T3 time-out

    1970-01-01 00:00:13 3-Critical U002.00 UCD invalid or channel unusable

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    2009-11-04 06:46:39 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:12 3-Critical U002.00 UCD invalid or channel unusable

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    2009-11-02 14:27:00 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    2009-10-16 05:02:20 3-Critical R002.00 No Ranging Response received - T3 time-out

    Time Priority Code Message

    2009-10-16 05:02:20 3-Critical U002.00 UCD invalid or channel unusable

    2009-10-16 00:46:06 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:00:13 3-Critical R002.00 No Ranging Response received - T3 time-out

    1970-01-01 00:00:11 3-Critical U002.00 UCD invalid or channel unusable

    1970-01-01 00:00:07 3-Critical X501.10 Operating in Gateway mode

    1970-01-01 00:00:11 3-Critical R002.00 No Ranging Response received - T3 time-out

    1970-01-01 00:00:10 3-Critical U002.00 UCD invalid or channel unusable

    1970-01-01 00:00:06 3-Critical X501.10 Operating in Gateway mode

    2009-10-11 23:49:04 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)

    1970-01-01 00:01:03 3-Critical R002.00 No Ranging Response received - T3 time-out

    And finally -

    Transmitted Fragment Count 1711

    Multicast Transmitted Fragment Count 103

    Failed Count 0

    Retry Count 53

    Multiple Retry Count 6

    Frame Duplicate Count 3

    Request to Send Success Count 0

    Request to Send Failure Count 0

    Acknowledge Failed Count 88

    Received Fragment Count 0

    Multicast Received Fragment Count 1784

    Frame Check Sequence Error Count 8354

    Transmitted Frame Count 1711

    WEP Undecryptable Count 0

    Any help figuring this out is greatly appreciated, because i cant. Comcast is coming tomorrow because online support was no help!

    -Jeff-

  2. #2
    Ohh Hell yeah.. Sava700's Avatar
    Join Date
    Feb 2002
    Location
    Somewhere
    Posts
    24,052
    power levels look too high... should be +-5 center of 0

Similar Threads

  1. This is why Comcast sucks! (Rant)
    By JPThomas68 in forum US Broadband Providers
    Replies: 9
    Last Post: 06-24-11, 06:08 AM
  2. HOWTO: Overclock C2D (Core 2 Duo) and C2Q (Core 2 Quads) - A Guide
    By graysky in forum Hardware & Overclocking
    Replies: 25
    Last Post: 04-23-10, 05:22 AM
  3. Terrible Comcast!
    By Coryb314 in forum General Broadband Forum
    Replies: 11
    Last Post: 02-04-09, 09:36 PM
  4. HOWTO: Minimizing Vcores and Operating Temps-must read
    By graysky in forum Hardware & Overclocking
    Replies: 0
    Last Post: 05-04-08, 08:41 AM
  5. Chicago Comcast Sucks - Rant
    By ghettoside in forum General Discussion Board
    Replies: 29
    Last Post: 11-13-07, 06:18 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •