dhcp
Latest
Ivy Leaguers asked to lay off the iPad
No iPads for the Tigers. Princeton University's Office of Information Technology is asking students to please stop using Apple's latest wonder gadget on the campus wireless network. According to the OIT, the issue is as follows: "Network monitoring has shown that many iPad devices are causing a problem on the campus network. These devices are continuing to use an IP address they have been leased well beyond the time they should." The university tech types say they've seen the quirky DHCP behavior from the majority of iPads connecting to the campus WLAN. They blame a bug they believe exists in the iPad OS. The Princeton tiger team has hit Apple up for help but, until the fix is in, the OIT recommends not connecting an iPad to the campus network, as it is likely to malfunction. The OIT says users who keep trying to connect may find their devices blocked, so that the stability and reliability of campus network services can be maintained. This is not the first time iThings have run afoul of higher learning's network wonks. Duke University suffered network outages around the release of the iPhone in 2007 and blamed those on the iPhone invasion; those hiccups eventually turned out to be a problem with Cisco routers, not Apple's phone. [via MacNN]
Why your school doesn't want boot camp
A trend I'd like to see go the way of the dodo: every time Apple introduces something new that doesn't seem to appeal to the average home user, the net lights up with wild speculation that it's for the education market. Most of the time it's not, and Boot Camp is no exception. The reaction to Boot Camp from MacEnterprise and other education and business Mac communities has not been positive. It's ranged from "wait and see" to "why me?" with most of the responses at the "why me?" end. Boot Camp is, in the words of University sysadmin and TUAW reader Jason Young, quite possibly "any IT staff member’s worst nightmare come true." And here are just a few of the reasons I think he's right:First, we live in a very imperfect world. Heterogeneous networks are messy, messy things. Sure there are protocols for Active Directory, Open Directory, LDAP, DHCP, etc., but vendors do one of two things: fail to implement the spec properly, or add a bunch of proprietary bells and whistles that aren't part of the spec, are technically add-ons, but still seem to mysteriously cause hardware or software to fail when they aren't present. Throw a couple of DNS forwarding issues, some CISCO equipment and maybe a Radius server into the mix, and things get ugly fast. What's the admins final line of defense against complete network chaos? Hardware addressing. Figure out what hardware is sitting at which MAC address, and build policies based on that. It's not ideal, but it's the the way the real world works. If you can't predict the OS type from the MAC, your job becomes 10 times harder in a flash.Second, nobody actually wants to reboot. It's time consuming, stressful on the hardware, and just generally not too much fun. It also means getting users in the habit of interacting with the firmware, which is something sane sysadmins want to avoid at all costs. What admins, and others, want is real virtualization. Not dual booting. Not emulation and compatibility layers. Real virtualization. When Apple delivers that, there will be partying in the streets.Third, there's no support and it doesn't look like there's ever going to be. Unlike the rest of us peons, large education and enterprise clients spend a lot of money on premium AppleCare services. They have reps who know them by name, and part of what makes Macs appealing is that you call one number and get integrated hardware and OS support. If Apple won't support Windows, dual booting will mean buying a second support contract for the same machine. hat more than negates the cost benefit of a single machine solution. Beige boxes are cheap and procurement already has contracts with HP and Dell. There is, of course, a potential for third parties here to step up and become Apple Authorized Resellers offering pre-configured machines with support, but that's a niche market. Most organizations that buy Macs want to deal directly with Apple.And then for education tech support, there's the added fun of personal machines that people use to connect to the network....Individual admins, of course, are thrilled. Being able do dual boot, say, a MacBook Pro means only needing one machine to administer everything. But supporting it for users? That's a different story.
