- 595 immigrants arrested at electronics plant
- Techiest celebrity endorsements
- Network failure delays flights across U.S.
- Alcatel-Lucent intros Gigabit Ethernet switches
- Firefox browser gets security boost
Newsletters | Podcasts | Chats | Opinions | RSS Feeds | This Week In Print | IT Careers | Community | Reports | Downloads | Slideshows | New Data Center
Partner Sites:App Performance | On Demand Security | Networking Solution | SOA | Value of WDS
Our good friends down the road got DSL a few years ago so we installed it for them and recently they decided to upgrade to the 2Wire HomePortal 1000HW, an asymmetric DSL modem with built-in 802.11b support.
So given that the ADSL circuit had already been set up (the account had been enabled with a PPP over Ethernet name and password defined, and the service had been running) how could this not be easy? One word: SBC.
According to the outsourced tech named Bob (whose lousy training, unctuousness and lack of understanding of his job will probably wind up in a future BackSpin column), the problem was caused by a malfunctioning registration server. Three days later, according to other outsourced techs with nice, familiar names like Mary and Joe (but who all sounded distinctly foreign) there was still a problem with the authentication server. Now we got suspicious.
The next time we called we demanded second-level support (who are real support people and not, as far as we know, outsourced) and spoke to Eric (not his real name), who was delightfully frank with us about the outsourced techs - "they suck" was his considered judgment. He said the problem had nothing to do with the faulty registration server but with the authentication server, and after resetting the password everything worked. It was a near miracle.
We suspect somewhere is the labyrinthine SBC Yahoo DSL installation, something to do with the PPPoE account setup got reset and stopped us from logging on.
So with the DSL service up and running and one PC connected by USB, we tried to connect via wireless a Macintosh PowerBook G4 running OS X 10.3. This was another complex and tedious exploration into the nether regions of the deranged ideas vendors have about networks.
The first problem was not being able to enter what Apple calls the "password" - what everyone else calls a "WEP key" - because OS X kept telling us we couldn't get authorized.
The default WEP key is printed on a label on the underside of the 2Wire device - it is just a sequence of digits.
It turns out that to enter the WEP key in the OS X 10.3 configuration utility you need to enter the key on the label preceded by a "$" so that OS X knows it is a hexadecimal value.
Had SBC included the 2Wire manual in the box the company shipped to my friends or even included the instructions in the hideous installation software, life would have been simpler. But no, we had to waste 20 minutes assuming we were doing something wrong then realize we weren't and had to go searching for an answer online.
Partner Content
Simplify Your Branch Infrastructure
Learn how to simplify your branch infrastructure while dramatically increasing app performance with Citrix Branch Repeater.
Download the Free Info Kit
Next-Gen Load Balancing
Free Guide: "Next Gen Load Balancing: 8 Things You Need to Handle Today's Network Traffic" shows you the functionality needed in your next load balancer.
Download the Free Guide
Accelerate Your Web Apps by up to 5x
Free Guide: "The Secret to Getting Maximum Speed from your Web Applications." Learn how you can deliver Web apps up to 5x faster.
Download the Free Guide
Comment