• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DSL-ISP workers... Could you describe the hardware in between a Modem and the Gateway?

W

WoundedWallet

Platinum Member
I've just switched ISPs (thanks Verizon for making me wait FIVE weeks to do so!), and I can't connect to the gateway.

My old ISP used a frame-relay and the new one uses an ATM.

I managed to connect twice on the first day but for a very short period of time and using my old modem(frame-relay related). I've never been able to connect with my new modem.

Somehow I think the problem is within Verizon(it always is), but I would like to know exactly the diagram of the hardware connections, so that I could guide the blind people that work there.

Even a rough description would put me a step above them. 😉
 
Thanks goldboyd, I learned something there. But I think I need a little more. Like where does the dslam fit? How about the difference between frame-relay and ATM? What is the first piece of hardware that receives my frames? And so on... But thanks anyway, I never thought of looking at dslreports for that.

Shadow, what do you mean csu/dsu? For me csu means Cal State University 🙂

Thanks guys.
 
Two ways to locate a DSLAM: at the CO, or backhaul and locate at the ISP. Given it's Verizon I would venture that they have the DSLAM located at the CO.

As far as explaining all of this, especially given that it's ATM...I don't feel like posting something that's gonna be a couple of screens worth of typing that will probably only serve to confuse you, AND if you get a tech who knows anything, will think that you're a dumbass who doesn't really know what he's/she's talking about.

That, and I have no clue as to the rest of their network configuration.
 
Thanks Damaged. I think tomorrow I'm gonna call a Verizon tech that came to my place once and had the problem solved before he even got here. And that was after me talking to their phone support for two weeks and no one being able to fix it. He just new what to ask them to check. And sure enough there was something that they hadn't checked before.

I assume the problem is of the same nature now, that being an incomplete ISP change. Boy, I hate Verizon.:|
 
Two weeks! I work for an ISP that provides DSL service, though we are not facility based in all places, so that means we have to deal with providers like COVAD. But in two weeks time we know it's not us, and we usually know (like 99.9% of the time) that it's not COVAD either. Which leaves, tada...the ILEC/CLEC (Incumbent Local Exchange Carrier/Common Local Exchange Carrier (e.g. Ameritech, GTE, et al)).

Usually they've missed a cross connect, or there's a problem with the pair being improperly conditioned (i.e. bridge taps on the line, etc.), or, sometimes it turns out to be a distance issue. Yes, sometimes AFTER the install distance is an issue. Why? Because the what the provider does is only an estimate of the length. Sometimes you get it installed, you know the line is properly conditioned, but the signal strength is still too weak.

Not trying to bum you out, just the facts.

I don't troubleshoot DSL for customers much anymore, mostly I'll look at our ATM swithces and make sure the PVC is built correctly, etc. and look at our DSL equipment (Redbacks of varying sizes from SMS 500s to SMS 1800s) and make sure everything is kosher there.
 
Just wanted you to know Wounded, that that sort of thing is not exactly unknown. I get DSL from QWest, and, after having it work fine for about 6 months, my DSL went out for *1.5 months* with no explanation other than that they were "working on it". I sat on tech support 8hrs a day on the weekends, and whenever I could during the week, and nothing ever happened. Finally they got some techs out here after I told them I was leaving their service, and they fixed it in 4 hours. Turns out that someone had kicked the DSLAM out of its socket at the CO, or some such.

I hate QWest. 🙁
 
Thanks for the encoragement guys. I've been on the slow lane since the first of the year... It's killing me!!!

Of all these possibilities, I know at least one of them is not true. The signal strength due to the distance. The CO is only 6 city blocks from me, and a tech once told me I was good to 8Mbps.

But the other stuff could all be true. What could be true as well is what the latest Verizon tech suggested, which is that "my Westell modem is not a Fujitsu" and thus incompatible with Verizon.

I'll throw in this question to my ISP tomorrow morning.
 
:|:Q:disgust::frown:....:|:Q:disgust::frown:

No wonder those mofos are being sued for lousy service.....

:|:Q:disgust::frown:....:|:Q:disgust::frown:

Can you believe that the last reason for my problem is an outage at Verizon's CO that's been going on since my problem started(5 days)? And none of the four Verizon's techs that I talked to had any knowledge of it, or even tried to find out about it.

On top of that the new Modem that Verizon sent IS the wrong one as well.

What a bunch of incompetents!!!

Did I say that in January I lost my dial tone and they said a repair person would be here the next day or they would pay me for the lost service? It took them 3 weeks to show up!!!

Maybe I should start a west coast lawsuit against those #%&@!*#
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top