Slashdot Mirror


AOL To Be Purchased By T-Online?

Sique writes "The german newspaper Sueddeutsche Zeitung reports on its website, that the german ISP T-Online wants to buy AOL. The article is titled American Dream, but the actual wording is german. Ask the fish for help." There's also the article in Der Spiegel about the potential purchase as well; you can also check out T-Online's site.

2 of 232 comments (clear)

  1. Re:Not surprising... by gfxguy · · Score: 4, Interesting

    Yeah, but that's ALL they did... it was a name change only, it's not like the company split.

    As an employee, I wish they would - AOL consumed Time Warner because they had artificially high stock prices and decided it was time for something with real value. They've been dragging us down ever since.

    Don't get me wrong - the press is really hard on AOL. Yes, customers are leaving, but they still have the most customers and charge the highest price. They are still making tons of cash, they're just making less and less of it.

    While I wish the company would split, I don't see how another ISP could buy out the largest ISP in the world. Wishful thinking.

    Full disclosure: I don't read German, I didn't read the article, so maybe I'm missing something.

    --
    Stupid sexy Flanders.
  2. Re:They're all alike (was: Re:hacker haven ...) by Shakrai · · Score: 4, Interesting
    I don't mean to pick on you, but when they ask what you're running, humor them and say "Windows XP".

    It's the principal of having to jump though hoops to report an outage on a commercial-grade account that my company pays several hundred dollars a month for. I do feel bad for the Level 1 techs themselves (I used to be one), but not the company that hires them.

    I had a similar problem with a Verizon ISDN circuit once. My router (Cisco 776) was reporting an error of "Error 3 - no Route" every time it tried to dial. The idiot that I spoke to told me "We'll send someone out to test the line, but if there aren't any problems, we are going to charge you".

    They dispatched someone who did loopback tests and pronounced the line clean and functional. I told them I would try a spare router (another 776) the next day and see if it worked or not -- I wasn't discounting that it could be our equipment, even though I doubted it. No shock, the spare router had the same error message.

    They then proceeded to tell me it was my configuration and they didn't support my router (they'd be too happy to support it for $75/hr). I told them this was bullshit -- said configuration had worked fine for years, and wasn't changed prior to the router not working.

    This went back and fourth for the next two days (at one point they even claimed that they LOST my ticket and all the notes attached to it) before (after yelling at nearly every person I talked to -- every shread of patience I had was gone at this point) I got a co tech on the line who worked with me on solving the problem (she had me initiating ISDN calls to various numbers while she traced them). Turns out, somebody changed the reroot order in one of their tadem switches (? that means nothing to me, but I'm not a telco weenie) and that caused the calls to disappear into the ether. Why they didn't make this connection earlier is beyond me. If one of my setups stops working the first thing I do is look at anything that has been changed over the last couple of days....

    By this point it had been down for 72 hours. I had three different tickets open on this issue before I finally got the knowledgeable CO Tech on the phone. She was helpful and actually knew what she was talking about. Every other idiot told me the problem was on "my end", accused me of "not knowing how to configure your own equipment", (my retort to that being "I guess Cisco's CCNP certification is overrated then"), and "We'll fix it, but it'll cost $75/hr." Three weeks after this problem was solved we received an invoice for the initial visit that did not solve or even diagnosis the problem. Needless to say, we did not pay said invoice...

    It's even more amusing to me that the little Mom & Pop ISP I worked for could go three years without a major outage (the outage that did occur was due to a car hitting a telephone pole outside of our building -- beyond our control) yet major national ISPs with (for all intents and purposes) infinite resources can't manage the same feat, even for their commercial customers. The situation has stabilized somewhat now, but initially the DSL account in question would go down at least once every two weeks for half an hour or so. And that doesn't count the little 30 second "hiccups" that occurred from time to time.

    I did eventually speak with the manager of the tech support and got a satisfactory answer out of him -- too few techs employed for the number of calls, company refusing to give out another contact number for non-tech support problems, stressed out customers blaming his people, etc etc. We had quite the mutual rant session for awhile.

    Bottom line: I understand outages occur and they are beyond the control of the avg guy at tech support. Just don't read to me from your sheet about router lights and operating systems when you have a known outage on your screen and an estimated time of repair for said outage. If you do, I'm going to rip you a new one, and rip your supervisor a

    --
    I want peace on earth and goodwill toward man.
    We are the United States Government! We don't do that sort of thing.