commentary Apparently doctors make the worst patients. Following that logic, technology journos have got to be among the most stubborn tech support callers.
I recently decided to pack in my 512kbps Unwired Internet service and get in on some iiNet ADSL2+ action so that my Scrabulous games on Facebook might load that little bit faster.
Yes, I know. I work at CNET.com.au, Where Tech Becomes Life. But home Internet has never been a big deal to me. It'd be like working in Willy Wonka's chocolate factory and coming home to a pantry full of Mars Bars.
Anyhow, after boasting of this indulgent scheme to anyone who would listen -- and receiving responses such as "Welcome to 2004" and "How did you get into this building?", I picked a plan online, selected a 4-port Belkin modem/wireless router (model F1PI241EGau) and handed over my bank details. Three business days later the promised device arrived, its dual antenna pointing toward heaven in a manner so endearing as to incur an affectionate -- though surreptitious -- pat from my trembling hand.
After swaddling the modem in blankets and love and carrying it home, I tore the box open with fumbling fingers and fed the requisite plugs into eager sockets. This was it. Access to the Web tubes at friction-free speeds and no need for my laptop to be tethered.
Only it was not to be.
Though my MacBook Pro engaged in friendly, animated conversation with Mr. Belkin via Ethernet, things got decidedly less amicable when I attempted to get the wireless component up and running. My Mac could see the network, but every time I attempted to connect I would receive a "There was an error joining the network" message.
There is nothing wrong with my AirPort. I know because I can -- theoretically -- connect to my neighbour's unsecured Wi-Fi network and download hundreds of megabytes worth of data.
I tried connecting via WEP encryption. Then WPA. Then none. Still the errors came.
I downloaded the latest firmware. I acquired every Mac software update available. I rebooted. I power cycled. Nada.
Reconfigured DHCP settings. Changed the router channel. Switched from mixed 802.11b/g mode to just b, then just g. Still getting the error message.
The next day at work I reluctantly picked up the phone and called iiNet's broadband support line. Being a tech head, I felt dirty -- the bad kind -- but what other options were there?
Ring ring. Press one; press five; please hold; your call will be monitored. Hi, my wireless isn't working. Oh, you don't offer support for wireless? I need to call Belkin? Dude, seriously. I've tried everything. Can I just send this thing back? I need a reference number from Belkin to prove that it doesn't work? I see. Oh no, the phone line's not faulty, that's just the sound of my teeth grinding. Righto. I'll be calling Belkin now.
Ring ring. Press one; press three; please hold. Hi, my wireless isn't working. OK, please don't send me an e-mail until I tell you the steps I've taken so far. No I mean it. I wrote a list. Let me throw some acronyms at you. WPA, DHCP, PPPoE, DNS -- I have waded through this alphabet soup and yielded nothing. Oh, I see. So there are known issues with this router and MacBook Pros? Why haven't these issues been publicised, even just a smidge? I reckon MacBook Pros are kind of popular. I could stand up from my desk chair and swing a cat right now and I would hit three MacBook Pro owners square in the face. Not including me. You'll send me an e-mail that will solve all my problems? Bonza. It will definitely work? OK, grand. Let me at it.
The e-mail arrives. The Word attachment looks familiar. I have followed these instructions before. They still don't work.
I still don't have a functioning wireless network. All I want is to be able to watch YouTube videos of penguins punching each other while I'm lying prone in bed with a bag of M&Ms on my abdomen. Is that such an unreasonable dream?
This whole episode has made me wonder how a non-tech person would have reacted when faced with similar wireless woes. If 802.11g won't work for me -- nor the two CNET.com.au editors I begged for help, both of whom are tertiary-educated in IT -- what hope does your granny Beryl have?
By the way, if you know the trick for getting a MacBook Pro to play nice with a Belkin wireless modem/router, please comment below. If it gets my Wi-Fi working, I will send you a prize. I wish I was kidding.
Like this article? Click below to send it to your mobile for free!
Super Bob
18/10/2007 01:49 PM
After looking at the apple support forums, the only thing that i saw could help is turning airport off and then back on. But as it seems, not many people post about their belkin?
Report offensive content
Andy Pandy
18/10/2007 02:05 PM
i think the original mistake was made when you chose the Belkin modem/router. Stay clear of Belkin. My suggestion is to reset the router to its default settings and start over again. Oh and forget out WEP too. Too hackable nowadays
Report offensive content
anthony
18/10/2007 02:18 PM
Sell the Belkin on ebay and buy a Netcomm NB6W. Not at all familiar with the Belkin but enabling encryption can be a hit and miss affair when using non apple products with a mac. You may have tried this but use WPA-personal on the mac and wpa-psk with tkip and ascii password on the router.
Report offensive content
username
18/10/2007 02:26 PM
Try adding your Airport ID to the Belkin's MAC address filter list, specifically setting it to allow
Report offensive content
Rob
18/10/2007 02:50 PM
I had exactly the same problem with a Linksys Modem/Router and my MacBook. If I saw that "There was an error joining the network" message again I would have thrown the thing through the window (the modem, not my Mac!). I eventually decided to buy an Apple Airport Extreme. I plugged my modem into this and bingo…wireless bliss in minutes! Although my modem’s wireless router function is now completely pointless, I take comfort in the fact I don’t have to read through anymore acronym filled blogs about how to fix that bloody error message…why doesn’t Apple make a modem/router!
Report offensive content
Mike
18/10/2007 03:17 PM
To begin with. When connected via Ethernet have you attempted to login to the 10.1.1.1 router gateway and ticked the 'enable wireless radio' option? If not this will then activate your modems wireless output. However the Belkin will not be transmitting securely. From here try the wireless tab on the left nav bar, select filtering I think whereby you can filter by your PCs Mac Address, which you can find by running the cmd prompt, typing ipconfig /all and looking for the wireless cards 'physical address'. Hope this helps
Report offensive content
kirbykia
18/10/2007 04:18 PM
Dont buy Mac. Problems solved. Sorry cant help myself See Mac have to make that comment.
Report offensive content
Ella Morton
22/10/2007 02:07 PM
Thanks for the suggestions, everyone. After trying them to no avail and then going another round with Belkin tech support -- who, it must be said, did their best to sort out the problem quick-smart -- it turns out I had a dodgy device. (I did do a double take when I first opened the box and saw "Ozemail" stamped on the modem, given the company was bought out by iiNet in early 2005. I reckon it was a lemon that someone else returned.)
Report offensive content
Paul
26/10/2007 09:43 AM
I think I have exactly the same problem with a lemon router as you: an Ozemail branded one I received from iiNet. An older iBook G4 connects perfectly, but my new MacBook Pro just does not want to play. Did iiNet replace your router ( or did you have to shell out for a new one? )
Report offensive content
Paul
27/10/2007 09:47 AM
My MacBook Pro now works! I upgraded the firmware to version 0.41 from this webpage: http://www.belkin.com/au/support/article/?lid=ena&pid=F1PI241EGau&aid=6242&scid=846
Report offensive content
dbmoodb
15/12/2007 04:10 AM
Hello, I recommend you try a live cd of linux. I would be interested to see what happens. Also, the belkins are sucky units. I know - i don't even have the wireless one and it is sucky (for everything other than voip).
Report offensive content
Ah, I just left a job working at an ISP's tech support call centre and yes, techs are hardiest to he
01/05/2008 04:25 PM
Ah, I just left a job working at an ISP's tech support call centre and yes, techs are hardiest to help, they always miss the simple things and don't listen, I know, I'm the same. :) Few points: 1) NEVER buy your modem from you ISP, unless you can get support after you leave that ISP. 2) Forget using wireless until you got working via the wired connection. Rules everything but wifi as being the problem. 3) All Netgear modems are trouble, so are most Belkin and Netcomm modems (for old netcomms see point 5) . 4) Dlink and Open Network make great modems, I have Open Networks myself, (clever ISPs sell Open Networks, they are well tested and never fail, which means less working supporting them, also made by an Aussie company) 5) NEVER use a usb based (instead network based) ADSL modem, sand in the eyes is more fun.
Report offensive content
violet
18/08/2008 08:51 PM
Well Ella, your story has been my world for a number of years, I'm often helping my mac friends and businesses to become connected via the assorted ISP's. When it comes to wireless and airport cards, get am Airport Extreme or Express, a basic modem and at least there's all the information related to using the Mac airport gear at apple.com. That way you just have to sort out the modem with the iinet, the wireless is handled by extreme/express. Send back the Belkin, get a simple dLink & Express, it'll wireless print which I love. have 4 macs connected to the d-Link and epson via extreme, it's working a treat. When I upgrade to macpro, I'll get an Express for wireless itunes as well. Granted took a bit of brain power to get it all up and running, there are far too many #@??/#ing security options. They should have a series of radio buttons for level of complication. Just give me the - Up and Running button please. Regarding the poor old granny on wireless, they have seen it all and just find there kicks elsewhere, we are joyful techo head bangers.
Report offensive content