Why can't I connect at 56k?
Over the last several
years, phone companies have replaced most of the analog lines connecting
their Central Offices (CO's) with digital equipment. Analog technology
sends data as a continuous wave, which can persist over long distances
and adverse conditions, but may arrive distorted from its original form.
Digital technology sends data as 0's and 1's and is more sensitive to interference,
but when properly administrated will pass from point to point with 100%
reliability. This greater reliability allows for higher speeds and is the
basis behind 56k modems. The connection between your local Central Office
and your house is still analog, however. Data you request from the Internet
arrives at Bee.Net's equipment in a digital form, and we pass it to a nearby
CO, still fully digital. Provided the data reaches your local CO without
being converted to analog anywhere along the way, these faster digital
connections give you a faster download speed. Due to the many variables
involved, the average "56k" connection actually falls in the range of
42k to 48k. Uploads from your computer are still limited to 33.6k,
however, because data moving from analog to digital lines cannot take advantage
of the faster speed. Here are some things to troubleshoot when this process
breaks down:
-
If the data is converted
to analog at any time before reaching your local CO, you will not get a
56k connection. Your modem will connect using the next best protocol, V.34
(28.8k / 33.6k). Phone companies are free to change your call routing at
any time, so you could go from a 52k connection one day to a 28.8k connection
the next day.
-
If you are in an office
environment, dialing through a PBX system may also add an extra digital
to analog conversion. Try dialing on a direct line instead of one that
requires an 8 or 9 to reach an outside line.
-
The distance between
you and your local CO affects whether you get a 56k connection, and the
actual speed you get. In general you need to be within 18,000 feet, or
about 3.5 miles. This is not physical distance but the total length of
phone wire, which may not travel in a straight line. The closer you are,
the better. If all other factors are equal, someone living next to a CO
may connect in the 50's, while someone at the edge of this limit may connect
only in the 30's.
-
The quality of the
phone line between you and your CO also affects your chances for 56k, and
your actual connection speed. The phone line is not just what's in your
house, but the lines on your street and in your neighborhood. Some phone
companies will use multiple trunks in an area, and when the first, higher-quality
trunk is full, calls may be moved to a second, lesser-quality trunk. Using
a short length of phone cord between the wall jack and the modem, and disconnecting
other devices from the line (cordless phones, fax machines, answering machines,
surge suppressors, splitters, etc.) may improve your chances slightly.
There are several ways
to test and troubleshoot these issues. If you are using a 56k US Robotics
modem, follow these
instructions from the V.Unreliable web site to check for multiple digital-to-analog
conversions and other line problems.
-
If you are not using
a US Robotics modem but have at least a 28.8k modem, you can simulate the
same test in reverse. Call the US Robotics Bulletin Board at 1-(847)-330-2780
with your modem and a terminal program. This is a long-distance number,
but the test takes only a minute. Windows 95/98/NT 4.0 users can use Hyperterminal
by clicking the Start button, then Programs, then Accessories.
If you have Windows 3.x you can use Terminal, which is accessed
from the "Accessories" group. Macintosh users may download a program like
ZTerm
or use the built-in window available in some dialers. For example, to display
a basic terminal window in FreePPP, edit your Account to connect
Manually instead of Directly. This test is not foolproof, since the call
routing to your long-distance company's phone lines may vary dramatically
compared to the routing to our local modems. For the best results, try
the test several times and during different times of the day.
-
Dial 1-(847)-330-2780 using your terminal program. If you are dialing directly from the terminal
window, type the command ATDT1-847-330-2780 and press Enter.When
asked if you want graphics, type n and press Enter.
When asked for your
first name,
enter line test and press Enter.
After a brief pause,
the test returns its results.Press Enter several times to display
some more statistics and then end the call.
For more information,
see these instructions
on the 3Com web site.
If this test is
inconclusive, you will need to contact your local phone company. They will
be able to check your line for basic problems like noise, voltage, and
stress, and for modem-specific issues like the distance from your house
to your local CO. They can run basic tests from their office, but to thoroughly
test your line, a serviceman will need to come to your house. Keep in
mind that your phone company is mandated to provide only a voice network,
not a network supporting "56k". Bee.Net has no control over the quality
of your phone lines.
If you live in an
area where more than one dial-up number is a local call, try dialing the
other number. Make
sure your modem is using the most recent firmware or driver. This is done
by contacting your modem or computer manufacturer or by checking their
web page for updates. 56k technology is still evolving and some manufacturers
release new code every couple months. As Bee.Net upgrades its modems, you
need to upgrade yours as well. Failure to do so could result in slower
connection speeds, disconnections, and possibly the failure to connect
at all. Check
if your modem supports the V.90 standard, or K56Flex or X2. Bee.Net supports
V.90 and X2. If your modem supports just K56FLEX, you will only be able
to make a V.34 connection (28.8 / 33.6). You must upgrade the firmware
or driver to V.90 to attempt 56k speeds. Sometimes
using initialization strings will improve your connection. ATZ, AT&F,
AT&F1, and AT&F2 are ones to try initially. Check your modem's
documentation for other specific strings and settings. You can also try
explicitly forcing
V.90, instead of another protocol the modem may choose instead.
|