dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2447
share rss forum feed

mattw13

join:2013-02-20
united state

Frequent line resyncs with NVG510

Hello. For the past month or so, my (well, actually not mine - I'm 16, so the AT&T account is my parents') UVerse connection has frequently been losing sync and disconnecting/ reconnecting. I read on the ATT Direct Support forum to post here first.

My dad called AT&T Thurs. and they did a line test and told my dad that the result was "indeterminate", and sent an ATT tech out. The tech stayed for about 5 minutes and recommended installing a new phone jack. However that would require drilling into the wall to which my dad replied "I'll think about it and will call back". We are thinking about switching to Comcast cable since we've always had problems with DSL (before UVerse, we had regular AT&T DSL and had problems of disconnects when using land line phone).

The DSL service we are paying for is the "AT&T U-verse High Speed Internet Max 12mbps" plan.

Here's what it says currently on the DSL statistics page(connection has been up for about 5-10 minutes, some information I manually redacted due to static IP information):

And here's what the log file is (some information I manually redacted due to static IP information):

P0000-00-00T00:00:04 L6 sdb[306]: log buffer size set to 8192
P0000-00-00T00:00:04 L7 sdb[306]: starting process /sbin/klogd (pid 313)
P0000-00-00T00:00:10 L7 sdb[306]: libmotopia: Closing /dev/motopia
P0000-00-00T00:00:10 L7 sdb[306]: Loading platform module bcm_enet
P0000-00-00T00:00:10 L6 sdb[306]: SSL CA-root-cert directory is ready.
P0000-00-00T00:00:10 L6 sdb[306]: Hardware is 'NVG510'
P0000-00-00T00:00:12 L6 sdb[306]: S/N 62035350423520, SKU 64
P0000-00-00T00:00:14 L3 sdb[306]: Wireless subsystem found
P0000-00-00T00:00:17 L5 sdb[306]: VOIP subsystem found
P0000-00-00T00:00:17 L7 sdb[306]: netfilter: redirect object not found. skip prerouting rules
P0000-00-00T00:00:18 L3 sdb[306]: scheduler: no ntp object
P0000-00-00T00:00:18 L6 sdb[306]: ip6.route[1]: Setting state from 'unset' to 'down'
P0000-00-00T00:00:20 L3 sdb[306]: Wi-Fi: Adding interface wl0
P0000-00-00T00:00:20 L3 sdb[306]: Wi-Fi: Adding interface wl0.1
P0000-00-00T00:00:20 L3 sdb[306]: Wi-Fi: Adding interface wl0.2
P0000-00-00T00:00:20 L3 sdb[306]: Wi-Fi: Adding interface wl0.3
P0000-00-00T00:00:20 L3 sdb[306]: DSL: EOC version 386bbb0687e0 NVG510 906221-64
P0000-00-00T00:00:20 L7 sdb[306]: enabling vc[1]
P0000-00-00T00:00:20 L7 sdb[306]: starting process /bin/voipexe (pid 997)
P0000-00-00T00:00:20 L5 sdb[306]: voipexe start returned ret=0
P0000-00-00T00:00:20 L5 sdb[306]: login authorization-delay timer set for 300 seconds
P0000-00-00T00:00:20 L4 sdb[306]: Configured for IPDSLAM mode
P0000-00-00T00:00:20 L5 sdb[306]: SYS: loading saved configuration
P0000-00-00T00:00:21 L6 sdb[306]: ip6_set_proc: setting to '1'
P0000-00-00T00:00:21 L6 sdb[306]: ip6_set_proc: setting to '1'
P0000-00-00T00:00:21 L6 sdb[306]: ip6_set_proc: setting to '0'
P0000-00-00T00:00:24 L7 sdb[306]: Ensw QoS: p-bit map: 0 0 0 0 1 1 2 2
P0000-00-00T00:00:24 L7 sdb[306]: Ensw: QoS configured
P0000-00-00T00:00:24 L7 sdb[306]: Ensw: max_age is 300
P0000-00-00T00:00:24 L3 sdb[306]: Wi-Fi: Intializing the subsystem
P0000-00-00T00:00:24 L3 sdb[306]: Wi-Fi: Setting country code to US
P0000-00-00T00:00:24 L3 sdb[306]: Wi-Fi: Country code set to US/2144584260
P0000-00-00T00:00:24 L3 sdb[306]: Wi-Fi: Starting autochannel scan...
P0000-00-00T00:00:26 L3 sdb[306]: Wi-Fi: Autochannel found channel 6 on attempt 1
P0000-00-00T00:00:27 L7 sdb[306]: starting process /sbin/eapd (pid 1066)
P0000-00-00T00:00:27 L3 sdb[306]: Wi-Fi: EAPD daemon started
P0000-00-00T00:00:27 L7 sdb[306]: starting process /sbin/nas (pid 1067)
P0000-00-00T00:00:27 L3 sdb[306]: Wi-Fi: NAS daemon started
P0000-00-00T00:00:27 L7 sdb[306]: Wi-Fi: Generated self WPS PIN = 14351082
P0000-00-00T00:00:27 L7 sdb[306]: starting process /bin/wps_monitor (pid 1074)
P0000-00-00T00:00:27 L3 sdb[306]: Wi-Fi: WPS daemon started
P0000-00-00T00:00:27 L7 sdb[306]: Port ssid-1 sending UP event
P0000-00-00T00:00:27 L3 sdb[306]: DSL: TPS-TC encoding set to PTM.
P0000-00-00T00:00:27 L6 sdb[306]: DSL: NLNM threshold value set to 60
P0000-00-00T00:00:27 L3 sdb[306]: DSL: Bitswap is ON, SRA is ON
P0000-00-00T00:00:27 L3 sdb[306]: DSL: Dying Gasp is OFF
P0000-00-00T00:00:27 L3 sdb[306]: DSL: DSP version - A2pD035b.d23i
P0000-00-00T00:00:28 L7 sdb[306]: DSL: Created net device ptm0, code = 0
P0000-00-00T00:00:30 L6 sdb[306]: conn[1]: linkchange_handler got event 19
P0000-00-00T00:00:30 L7 sdb[306]: conn[1]: new object ignoring event 19 from link[1]
P0000-00-00T00:00:30 L6 sdb[306]: conn[2]: linkchange_handler got event 19
P0000-00-00T00:00:30 L7 sdb[306]: conn[2]: new object ignoring event 19 from link[1]
P0000-00-00T00:00:30 L6 sdb[306]: conn[1]: linkchange_handler got event 19
P0000-00-00T00:00:30 L7 sdb[306]: conn[1]: new object ignoring event 19 from link[2]
P0000-00-00T00:00:30 L6 sdb[306]: conn[2]: linkchange_handler got event 19
P0000-00-00T00:00:30 L7 sdb[306]: conn[2]: new object ignoring event 19 from link[2]
P0000-00-00T00:00:30 L7 sdb[306]: link[2] sending DOWN event
P0000-00-00T00:00:30 L6 sdb[306]: conn[1]: linkchange_handler got event 17
P0000-00-00T00:00:30 L7 sdb[306]: conn[1]: new object ignoring event 17 from link[2]
P0000-00-00T00:00:30 L6 sdb[306]: conn[2]: linkchange_handler got event 17
P0000-00-00T00:00:30 L7 sdb[306]: conn[2]: new object ignoring event 17 from link[2]
P0000-00-00T00:00:30 L5 sdb[306]:
voice_event_handler: voice_get_wan_conn_obj returned null ..Not posting event:17
P0000-00-00T00:00:30 L6 sdb[306]: link[2]: Setting state from 'unset' to 'down'
P0000-00-00T00:00:30 L7 sdb[306]: starting process /bin/eap_tls_peer (pid 1319)
P0000-00-00T00:00:30 L6 sdb[306]: conn_apply conn[1]
P0000-00-00T00:00:30 L6 sdb[306]: conn[1]: conn_state_mc_controller got event 31 subevent 302
P0000-00-00T00:00:30 L7 sdb[306]: conn[1]: static_state_mc_controller got event 302
P0000-00-00T00:00:30 L7 sdb[306]: conn[1]: starting, current state is 'down'
P0000-00-00T00:00:30 L7 sdb[306]: priv_data: conn[1]/link[1]: static
P0000-00-00T00:00:30 L6 sdb[306]: starting conn[1] on link[1], interface=br1
P0000-00-00T00:00:30 L6 sdb[306]: conn[1]: config (0.0.0.0)->(192.168.1.254) flags=[1, 2, 0]
P0000-00-00T00:00:30 L5 sdb[306]: conn[1]: interface configured for 192.168.1.254
P0000-00-00T00:00:30 L7 sdb[306]: DNS: reloading proxy because /var/etc/hosts changed
P0000-00-00T00:00:30 L5 sdb[306]:
voice_event_handler: voice_get_wan_conn_obj returned null ..Not posting event:10
P0000-00-00T00:00:30 L6 sdb[306]: conn[1]: Setting state from 'unset' to 'up'
P0000-00-00T00:00:30 L7 sdb[306]: dhcps: invoke on interface br1
P0000-00-00T00:00:30 L7 sdb[306]: dhcps: adding interface string "br1"
P0000-00-00T00:00:30 L7 sdb[306]: starting process /bin/dhcpd (pid 1328)
P0000-00-00T00:00:30 L6 sdb[306]: conn_apply conn[2]
P0000-00-00T00:00:30 L6 sdb[306]: conn[2]: conn_state_mc_controller got event 30 subevent 254
P0000-00-00T00:00:30 L7 sdb[306]: conn[2]: dhcpc_state_mc_controller got event 254
P0000-00-00T00:00:30 L3 sdb[306]: Wi-Fi: Setting country code to US
P0000-00-00T00:00:30 L6 sdb[306]: log buffer size set to 32768
P0000-00-00T00:00:30 L6 sdb[306]: setting log level to 5
P0000-00-00T00:00:31 L5 sdb[306]:
voice_event_handler: voice_get_wan_conn_obj returned null ..Not posting event:16
P0000-00-00T00:00:31 L3 sdb[306]: lan_redirect_status_get: no conn
P0000-00-00T00:00:32 L3 sdb[306]:
voice_send_event: error 2:No such file or directory message size 100
P0000-00-00T00:00:34 L5 sdb[306]: database initialized
P0000-00-00T00:00:34 L3 vosdb[997]: SDB "isapplying" failed: Connection timed out
P0000-00-00T00:00:34 L5 sdb[306]: ELAN: Port lan-1 (eth0) going up
P0000-00-00T00:00:34 L5 sdb[306]: ELAN: Port lan-1 (eth0) speed 100 duplex full
P0000-00-00T00:00:34 L3 vosdb[997]: SDB "isapplying" failed: Connection timed out
P0000-00-00T00:00:35 L3 vosdb[997]: **********Starting VOIP Tasks *************
P0000-00-00T00:00:46 L3 sdb[306]: DSL: Filters may be missing: Yes
P0000-00-00T00:00:46 L3 sdb[306]: DSL: Echo level: 0 dB
P0000-00-00T00:00:46 L3 sdb[306]: DSL: Affected tones: 273
P0000-00-00T00:00:52 L3 sdb[306]: DSL: Last Retrain Reason: 0x8000 Reason Unknown 2
P0000-00-00T00:01:10 L3 sdb[306]: DSL: Filters may be missing: No
P0000-00-00T00:01:10 L3 sdb[306]: DSL: Echo level: 0 dB
P0000-00-00T00:01:10 L3 sdb[306]: DSL: Affected tones: 46
P0000-00-00T00:01:16 L3 sdb[306]: DSL: Mode ADSL2+ (PTM)
P0000-00-00T00:01:16 L3 sdb[306]: DSL: Sync Rate in kbps D/S 11996 U/S 1021
P0000-00-00T00:01:16 L3 sdb[306]: DSL: Latency path Interleaved
P0000-00-00T00:01:16 L3 sdb[306]: DSL: Trellis D/S:ON U/S:ON
P0000-00-00T00:01:16 L3 sdb[306]: DSL: CO Vendor BDCM
P0000-00-00T00:01:16 L3 sdb[306]: DSL: Link showtime counter since boot 1
P0000-00-00T00:01:21 L5 supp1x[1319]: Sending START Packet
P0000-00-00T00:01:23 L2 supp1x[1319]: Supplicant event = FAILURE
P0000-00-00T00:01:25 L4 sdb[306]: no WAN IP address detected
P0000-00-00T00:02:53 L2 supp1x[1319]: Supplicant event = FAILURE
P0000-00-00T00:02:55 L4 sdb[306]: no WAN IP address detected
P0000-00-00T00:03:53 L5 supp1x[1319]: Sending START Packet
P0000-00-00T00:04:29 L2 supp1x[1319]: Supplicant event = FAILURE
P0000-00-00T00:04:30 L4 sdb[306]: no WAN IP address detected
P0000-00-00T00:04:53 L2 supp1x[1319]: Supplicant event = FAILURE
P0000-00-00T00:04:56 L4 sdb[306]: no WAN IP address detected
P0000-00-00T00:05:03 L2 supp1x[1319]: Supplicant event = FAILURE
P0000-00-00T00:05:08 L4 sdb[306]: no WAN IP address detected
P0000-00-00T00:05:16 L3 sdb[306]: DSL: Last Retrain Reason: 0x1 RDI Detector
P0000-00-00T00:05:17 L3 sdb[306]: DSL: Link drop counter since boot 1
P0000-00-00T00:05:20 L5 sdb[306]: authorization-delay timeout cleared
P0000-00-00T00:05:36 L3 sdb[306]: DSL: Filters may be missing: No
P0000-00-00T00:05:36 L3 sdb[306]: DSL: Echo level: 0 dB
P0000-00-00T00:05:36 L3 sdb[306]: DSL: Affected tones: 55
P0000-00-00T00:05:42 L3 sdb[306]: DSL: Last Retrain Reason: 0x8000 Reason Unknown 2
P0000-00-00T00:06:00 L3 sdb[306]: DSL: Filters may be missing: No
P0000-00-00T00:06:00 L3 sdb[306]: DSL: Echo level: 0 dB
P0000-00-00T00:06:00 L3 sdb[306]: DSL: Affected tones: 50
P0000-00-00T00:06:06 L3 sdb[306]: DSL: Mode ADSL2+ (PTM)
P0000-00-00T00:06:06 L3 sdb[306]: DSL: Sync Rate in kbps D/S 11999 U/S 1021
P0000-00-00T00:06:06 L3 sdb[306]: DSL: Latency path Interleaved
P0000-00-00T00:06:06 L3 sdb[306]: DSL: Trellis D/S:ON U/S:ON
P0000-00-00T00:06:06 L3 sdb[306]: DSL: CO Vendor BDCM
P0000-00-00T00:06:06 L3 sdb[306]: DSL: Link showtime counter since boot 2
P0000-00-00T00:06:10 L5 supp1x[1319]: Sending START Packet
P0000-00-00T00:06:17 L5 supp1x[1319]: Supplicant event = SUCCESS
P0000-00-00T00:06:19 L5 sdb[306]: conn[2]: interface configured for [REDACTED PERSONAL IP ADDRESS]
P0000-00-00T00:06:27 L5 cwmp[1381]: DSLF_WanMgmtChg path[conn[2].ipaddr] val[REDACTED PERSONAL IP ADDRESS]
P0000-00-00T00:06:27 L3 vosdb[997]: Sdb Failed to get ip.ntp.time-qcquired
2013-02-24T22:05:30-06:00 L5 ntph[2624]: update system date & time from NTP server 68.94.156.17
2013-02-24T22:05:33-06:00 L5 cwmp[1381]: Next Periodic Inform after 86400 s
2013-02-24T22:05:33-06:00 L4 cwmp[1381]: Resolving ACS URL - Retry 0
2013-02-24T22:05:33-06:00 L5 cwmp[1381]: Connect to »cwmp.c01.sbcglobal.net/cwmp/services/CWMP [] Retry 0
2013-02-24T22:05:33-06:00 L5 cwmp[1381]: (SSL) Connect Success: cwmp.c01.sbcglobal.net
2013-02-24T22:05:33-06:00 L5 cwmp[1381]: (SSL) Certificate Verify Success: cwmp.c01.sbcglobal.net
2013-02-24T22:05:34-06:00 L5 cwmp[1381]: Post Inform - reason 1 BOOT 0 BOOTSTRAP
2013-02-24T22:05:34-06:00 L5 cwmp[1381]: Server auth challenge received
2013-02-24T22:05:34-06:00 L5 cwmp[1381]: Receive InformResponse
2013-02-24T22:05:34-06:00 L5 cwmp[1381]: Post 0
2013-02-24T22:05:35-06:00 L5 cwmp[1381]: Receive SetParameterValues
2013-02-24T22:05:35-06:00 L5 cwmp[1381]: Next Periodic Inform after 15089 s
2013-02-24T22:05:35-06:00 L5 cwmp[1381]: Post SetParameterValuesResponse
2013-02-24T22:05:36-06:00 L5 cwmp[1381]: Receive SetParameterValues
2013-02-24T22:05:36-06:00 L5 cwmp[1381]: Post SetParameterValuesResponse
2013-02-24T22:05:37-06:00 L5 cwmp[1381]: Receive SetParameterAttributes
2013-02-24T22:05:37-06:00 L5 cwmp[1381]: Post SetParameterAttributesResponse
2013-02-24T22:05:37-06:00 L5 cwmp[1381]: Receive GetParameterValues
2013-02-24T22:05:37-06:00 L5 cwmp[1381]: Post GetParameterValuesResponse (chunk-length - 3153)
2013-02-24T22:05:37-06:00 L4 cwmp[1381]: Continue GetParameterValuesResponse (chunk-length - 0)
2013-02-24T22:05:37-06:00 L5 cwmp[1381]: Receive SetParameterValues
2013-02-24T22:05:38-06:00 L3 sdb[306]: Wi-Fi: Setting country code to US
2013-02-24T22:05:39-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2013-02-24T22:05:42-06:00 L5 cwmp[1381]: Post SetParameterValuesResponse
2013-02-24T22:05:42-06:00 L5 cwmp[1381]: Closing connection on HTTP 204
2013-02-24T22:05:42-06:00 L5 cwmp[1381]: (SSL) Closing Connection: cwmp.c01.sbcglobal.net
2013-02-24T22:56:21-06:00 L3 sdb[306]: DSL: Last Retrain Reason: 0x1 RDI Detector
2013-02-24T22:56:22-06:00 L3 sdb[306]: DSL: Link drop counter since boot 2
2013-02-24T22:56:22-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
2013-02-24T22:56:23-06:00 L3 sdb[306]: dns_lan_redirect_notify. DOWN. restart proxy
2013-02-24T22:56:23-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2013-02-24T22:56:23-06:00 L3 sdb[306]: dns_lan_redirect_notify. DOWN. restart proxy
2013-02-24T22:56:23-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
The last message was repeated 3 times.
2013-02-24T22:56:24-06:00 L3 sdb[306]: dns_lan_redirect_notify. DOWN. restart proxy
2013-02-24T22:56:41-06:00 L3 sdb[306]: DSL: Filters may be missing: No
2013-02-24T22:56:41-06:00 L3 sdb[306]: DSL: Echo level: 0 dB
2013-02-24T22:56:41-06:00 L3 sdb[306]: DSL: Affected tones: 49
2013-02-24T22:56:46-06:00 L3 sdb[306]: DSL: Last Retrain Reason: 0x8000 Reason Unknown 2
2013-02-24T22:57:05-06:00 L3 sdb[306]: DSL: Filters may be missing: No
2013-02-24T22:57:05-06:00 L3 sdb[306]: DSL: Echo level: 0 dB
2013-02-24T22:57:05-06:00 L3 sdb[306]: DSL: Affected tones: 48
2013-02-24T22:57:10-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
2013-02-24T22:57:11-06:00 L3 sdb[306]: DSL: Mode ADSL2+ (PTM)
2013-02-24T22:57:11-06:00 L3 sdb[306]: DSL: Sync Rate in kbps D/S 11999 U/S 1021
2013-02-24T22:57:11-06:00 L3 sdb[306]: DSL: Latency path Interleaved
2013-02-24T22:57:11-06:00 L3 sdb[306]: DSL: Trellis D/S:ON U/S:ON
2013-02-24T22:57:11-06:00 L3 sdb[306]: DSL: CO Vendor BDCM
2013-02-24T22:57:11-06:00 L3 sdb[306]: DSL: Link showtime counter since boot 3
2013-02-24T22:57:11-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
2013-02-24T22:57:11-06:00 L3 sdb[306]: dns_lan_redirect_notify. DOWN. restart proxy
2013-02-24T22:57:11-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2013-02-24T22:57:15-06:00 L5 supp1x[1319]: Sending START Packet
2013-02-24T22:57:18-06:00 L5 supp1x[1319]: Supplicant event = SUCCESS
2013-02-24T22:57:18-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2013-02-24T23:35:49-06:00 L3 sdb[306]: DSL: Last Retrain Reason: 0x1 RDI Detector
2013-02-24T23:35:50-06:00 L3 sdb[306]: DSL: Link drop counter since boot 3
2013-02-24T23:35:50-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
2013-02-24T23:35:50-06:00 L3 sdb[306]: dns_lan_redirect_notify. DOWN. restart proxy
2013-02-24T23:35:50-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2013-02-24T23:35:51-06:00 L3 sdb[306]: dns_lan_redirect_notify. DOWN. restart proxy
2013-02-24T23:35:51-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
The last message was repeated 3 times.
2013-02-24T23:35:52-06:00 L3 sdb[306]: dns_lan_redirect_notify. DOWN. restart proxy
2013-02-24T23:36:09-06:00 L3 sdb[306]: DSL: Filters may be missing: No
2013-02-24T23:36:09-06:00 L3 sdb[306]: DSL: Echo level: 0 dB
2013-02-24T23:36:09-06:00 L3 sdb[306]: DSL: Affected tones: 54
2013-02-24T23:36:14-06:00 L3 sdb[306]: DSL: Last Retrain Reason: 0x8000 Reason Unknown 2
2013-02-24T23:36:33-06:00 L3 sdb[306]: DSL: Filters may be missing: No
2013-02-24T23:36:33-06:00 L3 sdb[306]: DSL: Echo level: 0 dB
2013-02-24T23:36:33-06:00 L3 sdb[306]: DSL: Affected tones: 55
2013-02-24T23:36:38-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
2013-02-24T23:36:39-06:00 L3 sdb[306]: DSL: Mode ADSL2+ (PTM)
2013-02-24T23:36:39-06:00 L3 sdb[306]: DSL: Sync Rate in kbps D/S 11997 U/S 1021
2013-02-24T23:36:39-06:00 L3 sdb[306]: DSL: Latency path Interleaved
2013-02-24T23:36:39-06:00 L3 sdb[306]: DSL: Trellis D/S:ON U/S:ON
2013-02-24T23:36:39-06:00 L3 sdb[306]: DSL: CO Vendor BDCM
2013-02-24T23:36:39-06:00 L3 sdb[306]: DSL: Link showtime counter since boot 4
2013-02-24T23:36:39-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
2013-02-24T23:36:40-06:00 L3 sdb[306]: dns_lan_redirect_notify. DOWN. restart proxy
2013-02-24T23:36:40-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2013-02-24T23:36:43-06:00 L5 supp1x[1319]: Sending START Packet
2013-02-24T23:36:46-06:00 L5 supp1x[1319]: Supplicant event = SUCCESS
2013-02-24T23:36:46-06:00 L1 sdb[306]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.



Tech007
Premium
join:2013-01-25
Belleville, IL
Reviews:
·AT&T DSL Service

so you say you had a similar problem before when you had home phone..Do you still have a home phone? How is the modem plugged into the wall, is it just plugged into a reg jack that was there before(not a jack that a tech installed) It sounds to me like you are using older home wiring to feed the nvg and if that older home wiring is all linked together(i.e. you have 4 jacks in the house and the modem signal is basically running to all those jacks even though its plugged into jack3)

If you were on a lower speed profile you may not have as many drops but for the speed your getting the modem really needs its own cable(cat5e or higher) from the outside nid(network interface) where telephone drop hits the house and the house inside wiring starts all the way to the modem for the best connection


mattw13

join:2013-02-20
united state

said by Tech007:

so you say you had a similar problem before when you had home phone..Do you still have a home phone? How is the modem plugged into the wall, is it just plugged into a reg jack that was there before(not a jack that a tech installed) It sounds to me like you are using older home wiring to feed the nvg and if that older home wiring is all linked together(i.e. you have 4 jacks in the house and the modem signal is basically running to all those jacks even though its plugged into jack3)

If you were on a lower speed profile you may not have as many drops but for the speed your getting the modem really needs its own cable(cat5e or higher) from the outside nid(network interface) where telephone drop hits the house and the house inside wiring starts all the way to the modem for the best connection

Yeah re: own CAT5e cable, that's exactly what the AT&T guy recommended.

As for where the modem is installed, it's installed into a jack that was there before currently. And no - we don't have a landline phone anymore.


Tech007
Premium
join:2013-01-25
Belleville, IL
Reviews:
·AT&T DSL Service

i am a uverse tech, i run into a lot of older home wiring that is causing problems, the older wire can work but its always better with the newer. if the jacks are all going to a common junction, than even removing unused wires that are just bouncing with the signal could inmprove the reliability


mattw13

join:2013-02-20
united state

said by Tech007:

i am a uverse tech, i run into a lot of older home wiring that is causing problems, the older wire can work but its always better with the newer. if the jacks are all going to a common junction, than even removing unused wires that are just bouncing with the signal could inmprove the reliability

Thanks for the advice. Told my dad and he said he will call AT&T soon to schedule an appointment with an ATT tech to install a new phone jack.

mattw13

join:2013-02-20
united state

2 edits
reply to mattw13

Update: well dad finally called AT&T today. The tech installed a new phone jack (with a new CAT5 cable the tech said). However, now I'm unable to resync at the full speed (downstream before was ~12000, now ~9000, not a big difference I'll admit). Also, I'm getting some amount of FEC errors (currently 121 after being up for about ~10 minutes). Should I be worried re: errors?

Any feedback would be appreciated.

Edit: A few minutes after this original reply posting, the DSL disconnected and reconnected again.

Edit 2: I'm getting this error whenever I have to reconnect: "DSL: Last Retrain Reason: 0x1 RDI Detector"



hadtodoit

@ritternet.com

I had the same thing when I went from DSL to uverse. WE chased the problem for a month and the final solution was to go down a tier in speed.

I'm at 6mbit instead of 12mbit but I have none of this crap "DSL: Last Retrain Reason: 0x1 RDI Detector"


mattw13

join:2013-02-20
united state
reply to mattw13

Hmm - after dealing with multiple ATT techs, tech who came out today replaced the outside NID -- and the issues appear to have been fixed. Just wanted to provide some closure to this thread/ topic.


GusHerb94

join:2011-11-04
Chicago, IL
kudos:1
reply to mattw13

Perhaps, even though you think your issue may be fixed you should post a photo of the phone jack, and a photo of the NID outside (opened up showing the wiring of course) and some of the inside wiring if you can. It would help us determine if there is anything that has been overlooked that could help improve your situation even more.