Their routers should be able to work around a device incorrectly claiming an IP address... (Doesn't make it right for the device to do that, though.)
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Princeton University Details iPad Wireless Networking Issues
- Thread starter MacRumors
- Start date
- Sort by reaction score
Re: Apple remote app
Well when you put it like that, I can see what they mean. Personally I would not delete, just say I would not use it. Just in case I wanted to use it on another network.
Well when you put it like that, I can see what they mean. Personally I would not delete, just say I would not use it. Just in case I wanted to use it on another network.
That's what I was afraid of. At that point, it seems like for the cost I might as well get a macbook or even a netbook for much less for quick boot, note taking and document creation.
There always seems to be "work-arounds" when it comes to Apple products nowadays. I remember having to download all these different programs to make Windows 95 and XP useful. In OS X, it "just worked". So, I switched and never looked back. Until now.
With the iPhone and the iPad, it isn't like this anymore. Usually the user has to download some App from the App Store that has some convoluted "work-around" due to Apple's restrictions. I think Apple is going backwards. It doesn't "just work" anymore.
on a smaller scale, the same thing is happening at loyola university chicago. my iPad has been blocked from connecting to their network as well
Good call. We had a similar issue. We escalated to our Apple rep who told us our router was configured wrong
That's it, I can't take another "trust me".
The words "trust me" when used in face to face discussion, typically carry about a 75% probability that the user is talking out their azz.
Online, 99%.
Whether projecting your own preferences upon others, or using your psychic powers to predict what other people you don't know will like or dislike, you may want to refrain from using "trust me" as your backing argument. It has the opposite effect.
The words "trust me" when used in face to face discussion, typically carry about a 75% probability that the user is talking out their azz.
Online, 99%.
Whether projecting your own preferences upon others, or using your psychic powers to predict what other people you don't know will like or dislike, you may want to refrain from using "trust me" as your backing argument. It has the opposite effect.
The folks at Princeton have clearly taken some time to diagnose the problem,a and share their findings, so I'm going to side with them, until Apple shows evidence to the contrary.
I remember the original iPhone causing a similar issue such as this, with university networks having to deal with DHCP issues when users would connect via Wi-Fi to the network.
Fair point, I was pretty much just saying it for emphasis but it is truly just my personal preference. After spending almost a week with the device, I can honestly say that I, and other people that I know with the device, would greatly prefer a real keyboard for typing multiple pages.
There always seems to be "work-arounds" when it comes to Apple products nowadays. I remember having to download all these different programs to make Windows 95 and XP useful. In OS X, it "just worked". So, I switched and never looked back. Until now.
With the iPhone and the iPad, it isn't like this anymore. Usually the user has to download some App from the App Store that has some convoluted "work-around" due to Apple's restrictions. I think Apple is going backwards. It doesn't "just work" anymore.
Leave the Apple garden and see how much worse it is. At the end of the day, Apple's vertical model will always trump everything else out there (due to its very nature), even if only by a matter of degrees.
iPad issue? Probably.
But does this mean I can walk onto Princeton's campus with manual DHCP settings on any wireless device and cause confusion and mayhem on their network? Seems like they need to get something straight themselves. I could be wrong but it seems like an issue on both sides.
But does this mean I can walk onto Princeton's campus with manual DHCP settings on any wireless device and cause confusion and mayhem on their network? Seems like they need to get something straight themselves. I could be wrong but it seems like an issue on both sides.
This is obviously a bug in the TCP/IP stack in the iPad. However, not renewing the DHCP and continuing to use the same IP address after the DHCP lease has expired should not result in any problem for others as long as the DHCP server is implemented correctly. Any DHCP server must first attempt to ping the IP address that it is about to lease to a device requesting an IP address. If the IP address is alive, the DHCP server must not lease it to another device. From the problem description posted on the Princeton web site, the iPad continues to respond to pings even after the DHCP lease expires and it fails to renew its DHCP lease. Therefore, the Princeton DHCP servers must skip over that IP address and not use it in the DHCP leases to other devices. If they are not doing this, their DHCP servers are not functioning correctly. Only in that case, would there be an IP conflict.
However, Apple should definitely fix this issue.
However, Apple should definitely fix this issue.
Duplicate IP addresses are BAD JUJU
...and that's exactly what you can get with this bug.
Continuing to use an IP address after the lease has expired is indeed a bug.
I wouldn't say (because I don't know) that Princeton is anal about IT policies, but it's clear that they actually look at their logfiles and take the time to understand what's going on and how that can impact the network. Good on them.
I suspect this will be a very quick fix, but when we'll see it, dunno.
...and that's exactly what you can get with this bug.
Continuing to use an IP address after the lease has expired is indeed a bug.
I wouldn't say (because I don't know) that Princeton is anal about IT policies, but it's clear that they actually look at their logfiles and take the time to understand what's going on and how that can impact the network. Good on them.
I suspect this will be a very quick fix, but when we'll see it, dunno.
Read a more extensive article last night and it is more Princeton than what has been reported by other Universities.
You know the drill, IT doesn't want Apple hardware on their systems and are unwilling to trouble shoot issues with the network.
Article: The problem stems not from the iPad's popularity but from the way it connects to wireless networks. Princeton University in New Jersey has blocked 20 percent of the iPads on campus because of "malfunctions that can affect the entire school's computer system."
In a report, Princeton said the iPad causes DHCP client malfunctions, which basically means the tablet causes interference for other devices using the school's wireless network. In order to prevent that interference, Princeton has been blocking the offending iPads.
George Washington University, in Washington, D.C. has also experienced network problems with the iPad, though not related to DHCP malfunctions.
"Our current authentication system isn't supported by the iPhone or the iPad," Guy Jones, Chief Technology Officer for GWU, told TechNewsDaily.
These devices aren't blocked by the university, but the authentication issues mean users aren't able to log on with the iPad or iPhone.
That doesn't mean the iPad is anathema at all universities, though. Cornell University in New York has also expected iPad problems, mostly relating to the devices taking up wireless bandwidth. The same problem happened when the iPhone came out and the university network received an extra load of traffic. However, Cornell tested specifically for DHCP malfunctions and found no problems with the iPad.
"We didn't see any DHCP malfunctions in our network with the iPad, or any problems at all," Cornell Information-Technology Director Steve Schuster told TechNewsDaily.
Schuster said it was "the difference in DHCP configurations between us and Princeton," that has kept Cornell from seeing the same problems.
Cornell's university network currently serves around individual 70 or 80 iPads, and Schuster confirmed the university has not blocked any of them.
