protasov
join:2002-02-23
Deerfield, IL
| reply to armyrebel4
Re: [Speed Problem] getting only 384k downstream
stats:
ADSL Information
Line State Up
Modulation DMT
Data Path interleaved
To Modem To Internet
Max Allowed Speed (kbps) 384 384
SN Margin (dB) 14.0 16.0
Line Attenuation (dB) 57.0 31.0
Loss of Signal 0 0
Loss of Frame 0 0
CRC Errors 5 0
ATM Information
VPI / VCI 0/35
Protocol Bridged
In Octets 40377102
In Errors 0
In Unicast Packets 28121
In Non Unicast Packets 0
In Discard Packets 0
Out Octets 1666961
Out Errors 0
Out Unicast Packets 15604
Out Non Unicast Packets 0
Out Discard Packets 0
LAN Information
Modem IP Address 192.168.1.254
Modem Netmask 255.255.255.0
Devices on LAN
*IP Address* *MAC Address* *Name* *Status*
192.168.1.64 00:00:00:00:00:00 192.168.1.64 Active
Ethernet Information
MAC Address 00:24:92:6a:0e:80
In Octets 40127528
In Errors 0
In Unicast Packets 28169
In Non Unicast Packets 48
In Discard Packets 0
Out Octets 1503218
Out Errors 0
Out Unicast Packets 15581
Out Non Unicast Packets 39
Out Discard Packets 0
Click here to go back to top |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| said by protasov  :stats: ADSL Information Line State Up Modulation DMT Data Path interleaved To Modem To Internet Max Allowed Speed (kbps) 384 384 SN Margin (dB) 14.0 16.0 Line Attenuation (dB) 57.0 31.0 ... CRC Errors 5 0 At 57 dB, your attenuation is somewhat high, but not unreasonably so. People routinely report connecting at 768 kb/s with attenuation as high as 63 dB. SNR is really good. Is this right after a reboot? You may be able to get some help from the techs by posting in the AT&T Direct forum. Unlike these public access forums, AT&T Direct is a private forum, and you can safely post your phone number there:
»/forum/sbcdirect
This is a holiday weekend, so they won't be answering until next week; and probably have a backlog to address, so it could take three days before you see a response. You can link this thread in your Direct post. But don't respond to, or "bump", your Direct thread after posting. Edit should be O.K., but anything else will knock it out of the queue.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
protasov
join:2002-02-23
Deerfield, IL
| Yes, it was after modem reboot.
I played with different configurations (splitter/no splitter, different wall sockets, different data cables, phone/no phone) went back to the same config and it is a bit better now (no idea why):
Statistics
ADSL Information
Line State Up
Modulation DMT
Data Path interleaved
To Modem To Internet
Max Allowed Speed (kbps) 384 384
SN Margin (dB) 16.0 16.0
Line Attenuation (dB) 55.0 31.0
Loss of Signal 0 0
Loss of Frame 0 0
CRC Errors 0 0
ATM Information
VPI / VCI 0/35
Protocol Bridged
In Octets 144
In Errors 0
In Unicast Packets 2
In Non Unicast Packets 0
In Discard Packets 0
Out Octets 797
Out Errors 0
Out Unicast Packets 7
Out Non Unicast Packets 0
Out Discard Packets 0
LAN Information
Modem IP Address 192.168.1.254
Modem Netmask 255.255.255.0
Devices on LAN
*IP Address* *MAC Address* *Name* *Status*
192.168.1.64 00:00:00:00:00:00 192.168.1.64 Active
Ethernet Information
MAC Address 00:24:92:6a:0e:80
In Octets 32624
In Errors 0
In Unicast Packets 70
In Non Unicast Packets 7
In Discard Packets 0
Out Octets 12046
Out Errors 0
Out Unicast Packets 56
Out Non Unicast Packets 26
Out Discard Packets 0 |
|
protasov
join:2002-02-23
Deerfield, IL | Opened a ticket through online chat at helpme.att.net, got call from customer care, guy reset line, works at 768 now. |
|
jkinney
join:2009-06-12
| I just setup our DSL Service yesterday and was having this same problem, called customer care, they reset the line, works great now
this is a huge improvement over what i had before (hughesnet). plus no caps
 |
|
