Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Apple Inc. -- Ignore unavailable to you. Want to Upgrade?

To: Doren who wrote (83660)	7/7/2009 4:56:53 PM
From: clean86	Respond to of 213177

He found a legacy chipset attached to it that was causing the problem. Since it was on their side of the interface they paid. We had a similar problem in my neighborhood with Verizon FIOS. When they upgraded their system the old equipment couldn't handle the new software and they had to replace a bunch of old routers that fried. It was one of only two times I had extended outage of more than 12 hours. The other time was because a repair man came in the middle of the night to the main hub and replaced a patch cable and put it back in the wrong slot cutting the signal to my house. They fixed both quickly and gave me credit of lost time.

To: Doren who wrote (83660)	7/10/2009 1:51:43 PM
From: shlurker	Respond to of 213177

i've had similar problems with ATT, but it was with the whole landline, circa 1960 cables/connections on our street, never issues with the static address DSL on top of it. Early times(up to 2002-3) with DHCP were bad, so i've been told. Right now, I'm leaning toward taking Cogito's advice and just Xfer everything to Comcast, but i bet i will have scenarios like you described with ATT. Different faces, different hassles, but the same frusration and time spent to get it right.