I’ve been using Cafenet for years and connect quite happily with my various Macintosh laptops. Recently I bought an iPod touch with 802.11b/g wireless. The other day I took it down to Readings in Courtenay Place and tried to get online via Cafenet.
While it finds and joins the wireless network, I just can’t make it load the Cafenet home page so I can log in and surf. I’ve tried a hard restart (actually restarting, not just sleeping), but it’s just defeating me. I’ve just emailed Cafenet, seeking their help.
I checked the settings — it was using DHCP and seemed to have similar info to the MacBook I was using at the same time.
The error message it gives me (with an OK button) is:
Safari can’t open the page.
The error was “Operation could not be completed. (POSIX error -12 cannot allocate memory)” (NSPOSIXErrorDomain:12)
According to Cafenet’s What Do I Need?, my iPod touch meets the specs:
All the computer hardware you need to access the CaféNET service is a wireless (WiFi, 802.11b/g or WLAN) enabled laptop, PDA or phone.
If and when I get a response, I’ll post it here.
Popularity: 28% [?]
Confused? You've found you're at KnowIT when you expected to be at TiKouka at MacTips? The blog has been moved over here and you were automatically redirected. Found something broken? Please let me know.
is jointly authored by Miraz Jordan and Maria Langer.
{ 13 comments… read them below or add one }
Hey Miraz,
That’s strange - we’ve had a touch (1.1.1 firmware) working on a cafenet access point in the wellington hospital. Let us know what they have to say (if they actually reply)
Brian
Hey,
This is a “server” side issue. The error message has nothing to do with the touch. The only thing that can be is that some JavaScript has mucked up and forwarded you to a wrong page of some sort. Then it would be a touch issue. But that’s highly unlikely.
So my hunch is CafeNet has to fix this.
cheers
Oliver
Hi there,
I came across this post after having a similar issue at home. I actually fixed it by going into the settings and resetting my Network Settings. Maybe give that a try?
Hope it helps!
Success: today I was using a different Cafenet access point on Featherston Street. I first told the iPod touch to ‘forget’ Cafenet, then joined the network again and this time was able to log on to the Cafenet home page, enter my password etc and surf around.
I just started getting this error this morning on my wife’s Touch. We get it on EVERY webpage, Google, etc….
Hi
All you need to do is from network settings, select “FORGET THIS NETWORK”. After than you can try logging in again and it should definately work!
Regards
Reza
thank you so much for your comments totally helped me in my first day as ipod touch owner
Thanks very much for the information i recently had this problem and resetting from the ipod Actually worked, cheers once agen Brad
hey i have a ipod touch and my safari and youtube are not working , can anyone help me, what do i do?
Miraz: I too have been having this issue with CaféNet in Wellington. It’s very variable, but one thing I have observed is the “Router” address in the DHCP settings seems not to be passed down to / stored by the iPod Touch. But when you can make a good connection, you’ll find the router address is in there.
This is why putting in a static, open DNS server address into the “DNS” settings in the iPod touch doesn’t seem to help in this situation - there is no connection past the Access Point.
Now what I don’t know is why this might be: is it a function of the distance from the Access Point, and/or its signal strength, or is it a function of the Access point hardware and its interaction with the iPod? I’m wondering whether I should do some more testing.
Telling it to “forget” the network then rejoining is a good strategy. Worked for me.
could you have jailbroken you ipod using ziphone? I read the hack also sets your ipod or iphone MAC address to the author’s name - if you’ve got the same MAC address and there’s enough of you… then there’s the resaon
Brenda: I’m not really into the jailbreaking thing.
‘Forgetting’ the network solved the problem.
Leave a Comment