>
> Do we live on the same planet?
Possibly, but maybe a difference is that I don't do senior centers,
retirement homes, etc. These are all people who live on their own.
> Because modems have been around since the 1970's. I had a nice
> discussion with one retired architect, that remembers a modem as a
> wooden box that you put the handset inside.
I hate to say it but I remember those, too. I also remember the sound
baffles you needed to be able to sit in the same room with a Diablo 630
printer. Oh gee, nostalgia here we come...
> My worst problems seem to arrive from the
> visits by the grand kids, who are all computer experts, and invariably
> leave a security hole, virus, or config problem behind.
I've told folks to please phone me before their grandkids do anything, and
DON'T buy any software that is offered to them. The computer works fine as
it is and won't be improved by any new software.
Actually they have phoned me and I've actually talked with some of those
grandkids and talked them out of "fixing" the computers.
<snip>
Some pictures from inside the house:
http://i429.photobucket.com/albums/qq17/dukeofurl01/Not%20Assigned%20to%20other%20albums/DSL-Modems.jpg
The short version is: I have taken the modem, and phone cord out to the
demarc outside the house, it worked find, green light and everything,
but no "internet" light. I wanted to take a picture, but all I had was
my 3GS, and the picture would not turn out, no matter what I tried.
There was some kind of voltage leak, I could feel it when I touched the
lines. It was kind of disconcerting. I don't usually feel voltage
unless someone is calling the line while I'm working on it.
I checked all the phones for the microfilters, and each phone only has
one of those pass through filters, with one port, and then phone plugged
into that.
EXCEPT the one in the office where the modem is plugged into, that one
has the two outs, phone and data, and it is set up correctly.
This tells me that the problem is somehow related to authentication.
Does that sound right?
She said that she called ATT, and that they are sending out a technician
on Wednesday.
I'm very tempted to wash my hands of the whole thing...
>Some pictures from inside the house:
>http://i429.photobucket.com/albums/qq17/dukeofurl01/Not%20Assigned%20to%20other%20albums/DSL-Modems.jpg
Westel 6100 DSL modem.
>The short version is: I have taken the modem, and phone cord out to the
>demarc outside the house, it worked find, green light and everything,
>but no "internet" light. I wanted to take a picture, but all I had was
>my 3GS, and the picture would not turn out, no matter what I tried.
Don't worry about the "Internet" light. What it does is try to ping
some server on the internet. If the ping is successful, the light
comes on. If not, it stays off. The problem is that connectivity to
this server is somewhat erratic. I've seen working modems with the
"Internet" light both on and off. Concentrate on the DSL light.
>There was some kind of voltage leak, I could feel it when I touched the
>lines. It was kind of disconcerting. I don't usually feel voltage
>unless someone is calling the line while I'm working on it.
Do you have a DVM (digital volt meter)? If so, measure from each wire
(red-green) to earth ground at the Demarc. You should see 48VDC
across the line, and nearly zero between each wire and ground. If you
get the full voltage from one of the wires to ground, you have some
device on your line shorted to ground. That will cause an imbalance
and problems. However, you will also hear such a problem in the phone
as 60Hz hum, so that's improbable.
>I checked all the phones for the microfilters, and each phone only has
>one of those pass through filters, with one port, and then phone plugged
>into that.
>
>EXCEPT the one in the office where the modem is plugged into, that one
>has the two outs, phone and data, and it is set up correctly.
Ok, it's wired correctly. So much for the easy fix.
>This tells me that the problem is somehow related to authentication.
>Does that sound right?
Maybe. Please re-read my previous message, where I asked you to look
at the line statistics and connection status.
One of the common problems I keep blundering into is that the password
has mysteriously changed. The symptom is rather odd. Instead of the
desired web page, you get the AT&T troubleshooting web page, with
offers to install tons of ActiveX controls into IE, and never mentions
that all that's wrong is the password.
>She said that she called ATT, and that they are sending out a technician
>on Wednesday.
It's going to cost. No clue how much.
>I'm very tempted to wash my hands of the whole thing...
Probably a good idea. Your responses to my suggestions and your
troubleshooting methods could use some improvement. Good luck.
>On 10/8/2011 6:18 PM, Jeff Liebermann wrote:
>> On Sat, 08 Oct 2011 17:18:50 -0700, Anthony <duke...@sonic.net>
>> wrote:
>>> [...]
>>> She said that she called ATT, and that they are sending out a technician
>>> on Wednesday.
3-5 days is now typical. Oh well.
>> It's going to cost. No clue how much.
>> [...]
>
>Really? Even if it's AT&T's problem? If it *IS* an AT&T problem
>the cost should be zero. Someone knowledgable should be there
>with the woman to assure the tech doesn't do a snow job.
Well, possibly. I'm assuming that the tech will miraculously "find"
something wrong with the installation. Unless the owner has inside
wiring (WirePro) insurance on her bill, anything the tech finds inside
the house is billable. I try to keep the tech out of the house, but
even that doesn't always work. One customer received a rather
elaborate bill from AT&T though the tech never showed up. Fortunately,
she had called complaining about the no-show, and the problems wasn't
fixed, so she was able to convince the billing office to drop the
charges.
However, you're right. Someone knowledgeable should be present.
Unfortunately, I don't think the OP is sufficiently experienced or
knowledgeable to qualify. Still, better than nothing. If he's
nearby, then he gets to wait around for the 4 hr window (assuming AT&T
shows up on time).
>I worked in San Mateo and San Carlos from 1993 to 2008 with multiple
>clients and though it took about a year to establish credibility with
>PacBell (mostly with the CO at 28th Avenue and El Camino in San Mateo)
>from that point on they always rolled on my calls because my analysis
>of the problem always proved to be correct *AND* Pac Bell's fault. I
>used to get a lot of preferential treatment from them including direct
>phone access to their NOCs for DSL, long-haul and other data problems.
That's a good arrangement. I only know one of the local DSL techs.
He's fairly new and doesn't want to risk his job by leaking useful
info. Oh well.
>I'm retired now and don't have those numbers anymore, so don't ask. :-)
How did you know what I was going to ask? I have a few numbers, but
have never needed to use them.
> I worked in San Mateo and San Carlos from 1993 to 2008 with multiple
> clients and though it took about a year to establish credibility with
> PacBell (mostly with the CO at 28th Avenue and El Camino in San Mateo)
> from that point on they always rolled on my calls because my analysis
> of the problem always proved to be correct *AND* Pac Bell's fault.
I've also had no problem dealing with AT&T's techs. Thing is, when I first
get on the line with someone I tell them in detail exactly what I've done so
far. This usually impresses them enough to either dig deeper or hand me to
someone who can. In most situations I can get AT&T's help onboard in 15
minutes or less.
I think I mentioned here the time I had a customer with erratic DSL. The
tech and I came to the conclusion that my customer was too far away, so she
slowed down the DSL transport a little and the clashes stopped. That was
another one that got solved in less than 15 minutes.
The line is nominally 48VDC; ringer voltage is ~ 90VDC.
Wet hands and a bare foot against a cold water pipe is another way
to test in the absence of a DVM; it's also a good way to induce
heart fibrillation. If the phone rings, be sure someone else is
nearby to laugh when your muscles contract and you go flying across
the room -- said person can also call 911 on your behalf if the
phone still works. :-)
Before anyone complains about the above, humor is a good way to
make a point among intelligent people. For example, I once saw
a sign over a urinal at Tymshare on East Meadow Drive in Palo
Alto in the 1960s:
Please don't throw cigarette butts in the urinal.
It makes them soggy and hard to light
Here's another one:
<http://www.flushedup.com/a-message-from-your-personal-bartender/>
and another:
<http://www.flushedup.com/that-is-a-bad-kind-of-infestation/>
While we're on humor, here's a replacement for High Speed Rail:
<http://www.theonion.com/video/obama-replaces-costly-highspeed-rail-plan-with-hig,18473/>
Believe it or not, it's not really fiction; here's the real one, a bus that
goes 160 MPH on public roads:
<http://www.youtube.com/watch?v=K7wEaG2u-BY>
<http://www.youtube.com/watch?v=yS7idJnIbVA>
<http://www.youtube.com/watch?v=1zQGCkxCFV0>
<http://www.huffingtonpost.com/2011/04/08/dutch-superbus-debut_n_846678.html>
Here are some other URLs with funny and bizarre stuff (all from the
same team):
<http://www.peopleofwalmart.com/>
<http://www.latenightmistakes.com/>
<http://www.beachcreeps.com/>
<http://americaninbreds.com/>
<http://www.latenightmistakes.com/category/wild-girls/>
<http://www.weddingunveils.com/>
<http://freaksoffastfood.com/>
<http://jawdrops.com/>
<http://www.whitetrashrepairs.com/>
<http://girlsinyogapants.com/>
<http://www.flushedup.com/>
<http://sillymillions.com/>
<http://drfugly.com/>
<http://www.wtftattoos.com/>
<http://www.thatsmyboss.com/>
<http://thatsmyroommate.com/>
<http://damnthatlooksgood.com/>
<http://hottestgirlsoncampus.com/>
<http://youdrivewhat.com/>
<http://www.memoryglands.com/>
I don't know how it works now, but years ago you could call in and add
the Inside Wiring plan to your bill, then *immediately* request a
service call, and the call would be covered by the Inside Wiring plan.
They count on you being too lazy to call back after the problem is fixed
to remove the Inside Wiring surcharge from your monthly bill.
So... I'd have her add the Inside Wiring (apparently WirePro now?) plan
immediately. Maybe, just maybe, it might pay for the upcoming service
call. Then you can remind her next week to remove that plan from her
bill so she doesn't get billed for it month after month...
jc
>I don't know how it works now, but years ago you could call in and add
>the Inside Wiring plan to your bill, then *immediately* request a
>service call, and the call would be covered by the Inside Wiring plan.
>They count on you being too lazy to call back after the problem is fixed
>to remove the Inside Wiring surcharge from your monthly bill.
I don't know. That might work. It's certainly worth a try. I think
(not sure) that you can add WirePro service with just a mouse click
using their online account management thing. However, I do know that
it's impossible to remove WirePro, as that requires talking to a
human.
I'm one of those that was too lazy to drop WirePro. When it was
$3/month, it was not a big deal. I think it's now $7/month, which
adds up. My problem is that I've tried to drop WirePro and some other
added services something several times in the last 15 years. Each
time, the result was a variation on loss of DSL, strange services
added to the bill, and about a year ago, a mysterious disconnect order
which took about a month to untangle. I guess I should try again.
I also tried to get AT&T to install a new NID on the assumption that
paying 10+ years for WirePro would entitle me to getting something
useful for the money. I succeeded in doing that for other people, but
not for my line. When the AT&T tech arrived, he claimed (lied) that
he didn't have an NID boxes with him.
>So... I'd have her add the Inside Wiring (apparently WirePro now?) plan
>immediately. Maybe, just maybe, it might pay for the upcoming service
>call. Then you can remind her next week to remove that plan from her
>bill so she doesn't get billed for it month after month...
She may need to have it remain for about 2 months, until the service
call clears the billing maze.
>How much is full voltage.
Nominally 48VDC. Don't expect it to be exactly 48VDC. It will vary
and might be as low as 35VDC.
>But at the same time, what
>is measuring it going to even accomplish?
Check for a ground fault on the phone lines.
Check for possible 117VAC line leakage to the phone lines.
>I know that usually, I can't
>feel anything while touching phone wires (unless somebody is calling)
>but this time I could.
Don't step on the wet ground and you won't get fried.
>Well, as much as that sounds related, there is NO webpage. None at all.
OK, then you don't have an ATM circuit. If the DSL light is on, and
the POTS phone is functioning normally, but it fails ATM ping, then
it's probabaly something wrong at the DSLAM. Not much you can do
about it. I would replace the DSL modem just to be sure it's not the
modem. It's not the PPPoE login/password as that first requires an
ATM circuit to function.
>Well, I'm not paying for it, so it doesn't matter. I was just trying to
>help out my neighbor across the street.
Do unto others, as you would like them to do unto you. If someone was
helping YOU with YOUR problem, it would be considered helpful if they
would make an effort to save YOU some money. I suspect your neighbor
expects the same treatment from you.
You have until Weds to find a solution or at least identify the cause.
>I would like very much to be better. If I lived closer, I would ask if
>I could shadow you for a little while. Though I'm curious (it will only
>help me out), what specifically makes you say that?
Sure. We'll start with you asking questions in a Usenet newsgroup
that's suppose to be specific to San Francisco and Monterey Bay area
issues. Read before you write.
Your descriptions were moderately ambiguous, devoid of specifics, and
lacking in any numbers (numbers are always useful). When I attempted
to deduce some of the conditions and the modem model number, you again
answered in a vague manner, and did not verify or contradict any of my
guesswork. When I asked you to check for line conditions and
connection status on the modem web page, you apparently forgot to do
so.
Shadowing me won't help. I only get about 3 DSL related problems per
month these days. Most of them are related to wiring problems. I
have to do one this afternoon, that I suspect is a mouse or rat chewed
cable.
It may sound horrible, but the above is about what I would expect from
someone unfamiliar with DSL and telco operations. The buzzwords and
tests will come with experience. However, the marginal descriptions,
lack of numbers, and apparently disorganized troubleshooting
procedures are not going to be fixed without a concerted effort on
your part. You may want to proof read your postings and ask yourself
if anything can be misinterpreted, is ambiguous, or lacking in detail.
If I may be so rude as to offer personal advice.... I've noticed that
many people, who are not quite sure of what they are doing, tend to
both ask and answer questions in the most vague manner possible. You
seem to be heading in that direction. While politicians do this
automatically, but it's not really good practice for problem solving.
If being vague is your idea of a defense mechanism, may I suggest you
lose it and try something else.
>"Jeff Liebermann" <je...@cruzio.com> wrote
>
>> One of the common problems I keep blundering into is that the password
>> has mysteriously changed.
>
>I've done this myself, resetting the modem and then realizing that the
>password was stored on the modem and the customer has no idea what the
>password was because they never use it for anything.
You're not suppose to admit to doing that. The illusion of
infalibility must be maintained at all cost. However, now that you've
mentioned it, I've done the same thing all too often.
However, there's a new wrinkle on the AT&T password mess. The same
password was previously used for both the AT&T PPPoE login and the
Yahoo outsourced email. For about the last year, they can now be
different passwords. That's a good idea, but does cause some issues.
I once got myself into a mess with changing the passwords. Calling
AT&T support on the phone was like admitting defeat, so I decided to
be creative. I went to the DSL signup page at:
<https://attreg.att.net>
and logged in with an existing account. If the PPPoE login fails,
that's the only page you can view anyway. It eventually produces a
web page with all the logins, passwords, security questions, and
details. It won't print directly, but a graphics screen dump is
sufficient to make a permanent copy for the customer. That was about
6 months ago and I don't know if it still works.
>So, I have them going
>through their "records" (aka drawers full of meaningless flyers for AOL
>dial-up offers and instruction manuals for TVs they haven't owned in
>years...) and try to come up with a password.
Yellow post it note on the bottom of the DSL modem?
>Usually I have to then phone AT&T and get the password reset, but they, of
>course, want the customer ID from a phone bill and then I have to wait until
>the customer can even find a bill ("Oh, my husband/wife takes care of
>that...")
Been there, many times. You can usually get around the problem by
answering the security questions.
>Thank goodness I charge by the hour...
Give the customer the fix for free, but charge for the travel,
equipment depreciation, parts, etc? It should be about the same.
"No good deed goes unpunished".
Pro-bono work for the elderly is nice and all, but unless they're
truly broke, i.e. not-a-homeowner, there is nothing wrong with
encouraging them to (a) subscribe WirePro @ $84/year and (b) schedule
a technician visit, even if charges result, including the "new modem"
sale. Its OK for them to spend their money.
If you truly want to help them, do the obvious: have them mark their
calendar for the contract renewal date, and migrate them to Sonic or
the local cable company - the latter is usually more forgiving on
service calls.
I will check for all that.
> Don't step on the wet ground and you won't get fried.
Yeah, that would make sense. Unfortunately for me, the demarc box is
surrounded by vegetation in a radius of at least 4 feet.
> OK, then you don't have an ATM circuit. If the DSL light is on, and
> the POTS phone is functioning normally, but it fails ATM ping, then
> it's probabaly something wrong at the DSLAM. Not much you can do
> about it. I would replace the DSL modem just to be sure it's not the
> modem. It's not the PPPoE login/password as that first requires an
> ATM circuit to function.
> Do unto others, as you would like them to do unto you. If someone was
> helping YOU with YOUR problem, it would be considered helpful if they
> would make an effort to save YOU some money. I suspect your neighbor
> expects the same treatment from you.
Well, I am at least trying to help out this lady. Nobody else is doing
that.
> Sure. We'll start with you asking questions in a Usenet newsgroup
> that's suppose to be specific to San Francisco and Monterey Bay area
> issues. Read before you write.
I used to live in Santa Rosa, now I live in Chico. I know the scope of
this group, but I'm still in Northern Cal, and things can't be that
different here, it's really not THAT far away, and still ATT territory.
For a long time, I've been a lurker and very occasional participant in
this group. This group is the only place I know of that has people that
are actually helpful, regularly reply, and somewhat local-ish, so even
if I wanted to, I'd actually be hard pressed to find a better source of
information. Plus since I've been a lurker here for so long, I actually
feel comfortable with most of the regular names involved.
> Your descriptions were moderately ambiguous, devoid of specifics, and
> lacking in any numbers (numbers are always useful). When I attempted
> to deduce some of the conditions and the modem model number, you again
> answered in a vague manner, and did not verify or contradict any of my
> guesswork. When I asked you to check for line conditions and
> connection status on the modem web page, you apparently forgot to do
> so.
I was going back over the posts in this thread, and I don't see anything
where you asked for any line statistics. Please correct me if I'm wrong
about that though. I seem to recall saying in one of my earlier posts
dated 10/5/11 5:51 PM "there is no model number written on it" though.
In my mind, I was trying to be vague, I was trying to describe things as
best I knew how. I don't recall seeing any actual statistics on the
line, but I'll double-check on Monday. Just in case, what are the
numbers you want me to check?
> Shadowing me won't help. I only get about 3 DSL related problems per
> month these days. Most of them are related to wiring problems. I
> have to do one this afternoon, that I suspect is a mouse or rat chewed
> cable.
>
> It may sound horrible, but the above is about what I would expect from
> someone unfamiliar with DSL and telco operations. The buzzwords and
> tests will come with experience. However, the marginal descriptions,
> lack of numbers, and apparently disorganized troubleshooting
> procedures are not going to be fixed without a concerted effort on
> your part. You may want to proof read your postings and ask yourself
> if anything can be misinterpreted, is ambiguous, or lacking in detail.
> If I may be so rude as to offer personal advice.... I've noticed that
> many people, who are not quite sure of what they are doing, tend to
> both ask and answer questions in the most vague manner possible. You
> seem to be heading in that direction. While politicians do this
> automatically, but it's not really good practice for problem solving.
> If being vague is your idea of a defense mechanism, may I suggest you
> lose it and try something else.
Just chalk it up to inexperience and inability to find anyone that I
really click with to follow around. As I've said, I'd really like to be
better, I really would. If I post anything that can be misinterpreted,
I don't have anything to back it up with, I don't have any more detailed
information without going back to the customer's house, which I'm sorta
trying to lay low on. I'll try to do better next time I'm there. This
cheapo DSL modem may not give the statistics that you want. I don't
recall seeing anything like that.
>Yeah, that would make sense. Unfortunately for me, the demarc box is
>surrounded by vegetation in a radius of at least 4 feet.
I just did a Sunday afternoon DSL service call. The demarc was
located in the middle of a dog run. Before I could start, I had to
shovel the dog droppings out of the way. As soon as I got close to
the dog run, the mutt went nuts. However, it wasn't a territorial
problem. The dog doesn't like anyone that wears a hat. Nothing wrong
at the demarc.
Incidentally, todays modem was a shiny new Motorola NVG510 U-verse
modem. 10Mbits/sec down, 0.9Mbits/sec up. 10 msec latency. 10K ft
from the CO. Zero jitter. I was impressed. After 3 different AT&T
techs couldn't make it work right, I found the intermittent ethernet
cable, bad wireless driver, wrong place for a proxy server, and a
trojan.bho virus.
>Well, I am at least trying to help out this lady. Nobody else is doing
>that.
That's the way it usually works. Many people are afraid to ask for
help. Some also forget to say thanks (like me). At least you're
trying.
>For a long time, I've been a lurker and very occasional participant in
>this group. This group is the only place I know of that has people that
>are actually helpful, regularly reply, and somewhat local-ish, so even
>if I wanted to, I'd actually be hard pressed to find a better source of
>information. Plus since I've been a lurker here for so long, I actually
>feel comfortable with most of the regular names involved.
I don't think anyone is overtly concerned exactly where you live. The
problem is that many discussions involve ISP's, topics, and politics
that are unique to the area. I guess you do read before you post.
This is good.
>I was going back over the posts in this thread, and I don't see anything
>where you asked for any line statistics.
Quoting myself:
Dive into the web based config at 192.168.1.254 and see if there's
a page showing DSL connection status. I'm fairly sure you don't
have an ATM circuit, and certainly not an IP address. While you're
there, look around for unplugged phone cables and new devices.
Check AGAIN for dial tone at the DSL modem. Bring your own POTS
instrument to be sure.
I guess you're right. Connection status means what are the numbers on
the DSL connection page. Things like SNR (signal to noise ratio) and
line levels.
<http://www.dslreports.com/faq/7036>
<http://www.dslreports.com/faq/6096>
<http://www.dslreports.com/faq/11010>
Note that these are from SE Bell, which will have different settings,
models, firmware, etc.
>about that though. I seem to recall saying in one of my earlier posts
>dated 10/5/11 5:51 PM "there is no model number written on it" though.
>In my mind, I was trying to be vague, I was trying to describe things as
>best I knew how.
I got the number from the 4 photos you posted. The problem is that
the one of the serial number tag was out of focus and very small. I
only decoded the number because I had a 6100 in my hand for
comparison. The model number is buried in the middle of a longer part
number. Typing that number into a Google search should have yielded
the model number. Also, typing my guess of a Westel 6100 into Google
Images should have returned many photos.
>I don't recall seeing any actual statistics on the
>line, but I'll double-check on Monday. Just in case, what are the
>numbers you want me to check?
These:
<http://i.dslr.net/pics/faqs/image92621.gif>
Here's a table for what the numbers mean.
<http://www.dslreports.com/faq/16220>
<http://www.dslreports.com/faq/6734>
I don't expect problems here, but I've seen some surprises, so it's a
good idea to check line levels.
>This
>cheapo DSL modem may not give the statistics that you want. I don't
>recall seeing anything like that.
There's quite a bit under the "statistics" section. Look for anything
that looks like an error or an error rate. I don't have a 6100 handy
to offer a specific web page. The basic plan is to determine why it's
failing ATM ping. (Hint: Always start troubleshooting from the
BOTTOM of the protocol stack).