Microsoft struggles to stay relevant in face of Apple’s myriad successes
The bear case for Microsoft can be summed up in one word: Apple...
Expectations for Apple hit new heights after record iPhone sales
Apple's 8.75 million iPhones sold in the March quarter combined with a better-than-expected launch of the iPad has led analysts to increase their already bullish views on the company's stock.
Princeton University Identifies iPad DHCP Flaw
Princeton University's Office of Information Technology has posted a document describing networking problems suffered by roughly half of the 40 iPads on campus. The problem isn't so much experienced by the iPad as caused by it - here's what's happening.
The iPad uses DHCP (Dynamic Host Configuration Protocol) client software (in the iPhone OS) to request network configuration information - most notably an IP address - from a DHCP server. That IP address is typically "leased" to the DHCP client for a period of time; once that lease expires, if the DHCP client is still online, it asks to renew the lease and retain its IP address. If the client is not online when the lease expires, the DHCP server is free to assign that IP address to another device. When the DHCP client returns to the network, it requests and receives a new IP address.
The problem seems to be that the iPad, in some situations, is failing to renew its DHCP lease but continuing to use the previously assigned IP address. Because the lease wasn't renewed, the DHCP server believes it is free to reassign the IP address. If that IP address is reassigned to another device while the iPad continues to use it, both devices end up using the same IP address, which can cause loss of network connectivity, confusing dialogs as operating systems attempt to handle the error condition, and more.
Princeton is working with Apple to resolve the problem, which is believed to lie with the DHCP client in iPhone OS 3.2, and which should be easy to fix with an update to iPhone OS 3.2. In the meantime, Princeton recommends that iPad users not connect to the campus network because if the iPad malfunctions, they may need to be blocked to prevent them from causing problems for other network users.
Who's likely to experience this problem? Primarily institutions with large networks that rely on DHCP for a constantly changing collection of network devices. Home users and those with small networks aren't nearly as likely to experience IP address collisions due to this problem.
If you do run into this problem on a small network you control, there are a variety of possible solutions:
- Assign a static IP address to your iPad and configure your DHCP server to avoid handing out that address to other devices. This fix isn't feasible on a large network with a lot of devices because it requires too much manual intervention.
- Configure your DHCP server to reserve a particular IP address for your iPad. I tried this in AirPort Utility using the client ID approach to identifying the iPad, but it didn't work; it's possible the MAC address approach would work better. This approach also requires too much manual intervention to be useful on a larger network.
- Set a very long DHCP lease time so the DHCP server is much less likely to reassign the iPad's IP address to another device. Trying this on a larger network would likely tie up too many IP addresses that weren't actually in use or require the use of NAT.
It is worth noting that, despite a quote in The Daily Princetonian article linked above, this DHCP problem is almost certainly unrelated to the Wi-Fi problems that have plagued some iPad users (see "Some iPad Users Suffer Wi-Fi Woes," 6 April 2010).
Nevertheless, here's hoping that Apple fixes this problem soon, not because it's necessarily causing all that much trouble even for large networks, but because it would be a shame if the iPad garnered a bad reputation among network managers based on what should be an easily fixed bug, given that DHCP is a long-established standard.
Read and post comments about this article | Tweet this article
READERS LIKE YOU! Support TidBITS with a contribution today!<http://www.tidbits.com/about/support/contributors.html>
Special thanks this week to Jan Dejmo, Andy Enzminger,
Ken Russell, and Jean Etcheverry for their generous support!
Copyright © 2010 Adam C. Engst. TidBITS is copyright © 2010 TidBITS Publishing Inc. If you're reading this article on a Web site other than TidBITS.com, please let us know, because if it was republished without attribution, by a commercial site, or in modified form, it violates our Creative Commons License.
Retro handset for the iPad is fashion-forward, techno-backward
Filed under: iPad
Here's something very high on the cool scale. The retro-cool Moshi Moshi 01 handset (MM01) can be used with mobile phones, VoIP via USB and yes, iPhones and iPads.
Old-timers like me remember back when talking on the phone meant standing next to the wall, tethered (physically, not Bluetooth) to a hunk of plastic and metal, speaking into a bulky handset that hung from a 2- or 3-foot length of cord. The folks at Native Union have brought the sexy back with the MM01. When fitted with the proper adapter, the MM01 can connect to most mobile phones including the iPhone.
Additionally, you can connect it to an iPad (again, with the proper adapter) to use with VoIP apps like Skype. It's like having a telephone at the end of a cookie sheet! Who wouldn't want that?
Seriously, we think this thing is great. For $US29.99, you get the handset and 3.5mm connector jack. Other adapters are sold separately.
[Via BoingBoing]
Retro handset for the iPad is fashion-forward, techno-backward originally appeared on The Unofficial Apple Weblog (TUAW) on Wed, 14 Apr 2010 20:45:00 EST. Please see our terms for use of feeds.
Retro handset for the iPad is fashion-forward, techno-backward originally appeared on The Unofficial Apple Weblog (TUAW) on Wed, 14 Apr 2010 20:45:00 EST. Please see our terms for use of feeds.
Read | Permalink | Email this | Comments
Swede’s iMac takes a burnin’ and it’s still turnin’
In what should be used by Apple as a testament to the solid construction of their computers, a Swedish man, Anders Norman, suffered a tragedy last Wednesday when his house burned down. To Norman's surprise, his iMac survived the conflagration despite being burned and partially melted.
Norman's experience (translated from Swedish) follows: "Unfortunately, the whole house and all things in there completely destroyed, so even the iMac. What's funny is that it is still in operation. While damaged from smoke and dust and partially melted, but yet, however in operation.
After I plugged in the burned power cord and wiped off the worst dust from the screen I pressed the melted start button. Imagine my surprise when the startup sound sings from the speakers! The screen turns on and the machine connects to the wireless network.
The mouse works flawlessly and the scroll wheel as well. Firefox starts and I take up the article from the local magazine about the fire ... Fantastic!
On Friday I bought a new iMac at the Apple Store here in Umeå, which I now rejoice."
To see just how bad the damage was, take a look at this second photograph by Anders Norman that was shown on the Feber.se website:
Thanks to TUAW readers Emil and Roger for the tip.
Swede's iMac takes a burnin' and it's still turnin' originally appeared on The Unofficial Apple Weblog (TUAW) on Mon, 15 Feb 2010 13:00:00 EST. Please see our terms for use of feeds.
Swede's iMac takes a burnin' and it's still turnin' originally appeared on The Unofficial Apple Weblog (TUAW) on Mon, 15 Feb 2010 13:00:00 EST. Please see our terms for use of feeds.
Read | Permalink | Email this | Comments
