Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.5: Work around a potential AirPort connection glitch Network
In trying to use our Macbook (with Leopard) wirelessly at the local University library, we encountered a problem. They have a captive portal such that the connection to the wireless system has no password, but you must authenticate via your web browser. The Macbook connected to the wifi system, or at least it claimed it did, but no actual connection was established, and of course, the captive portal was never activated. After some trial and error with the university's IT people (who told me that they had seen this same problem with a few Leopard Macbooks and Macbook Pros, but never with Tiger or with non-Macs), we figured out a workaround.

What you do is create another Location (we called ours "Kludge"), and leave it at the default settings. With that location selected, the airport worked flawlessly, the captive portal activated, and everything was wonderful again.

My suspicion is that the Automatic location can get munged somehow, possibly if third-party network devices are installed. We had installed a Novatel CDMA modem on that machine in the Automatic location. Anyway, once Automatic gets broken, then it could fail in subtle ways such as what I described. Setting up a new location gives the system a tabular rasa to work with, and in this case, it was sufficient to solve the problem.
    •    
  • Currently 1.83 / 5
  You rated: 4 / 5 (6 votes cast)
 
[9,289 views]  

10.5: Work around a potential AirPort connection glitch | 6 comments | Create New Account
Click here to return to the '10.5: Work around a potential AirPort connection glitch' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: Work around a potential AirPort connection glitch
Authored by: goblyn13 on Dec 14, '07 05:25:37PM

I've have that problem all the time with t-mobile hotspot. The problem i had was that i ahd specified DNS. with T-mobile hotspot their captive protal requires that you have to log in via hotspot.t-mobile.com. This a dns kludge locally on the wireless network, so when i had dns specified, it would never get to look it up, because i was trying to resolve DNS from another dns server and not the one that was specified via DHCP on the wireless network. I had to create a location for T-Mobile specifically for to accept not only DHCP for the IP address but also for the DNS servers so that it would get the current IP for hotspot login. so its not really a 10.5 problem its more a problem with how the network interface is set up in the netwrok preferences.



[ Reply to This | # ]
10.5: Work around a potential AirPort connection glitch
Authored by: senseigmg on Dec 16, '07 09:09:51AM

I had the same error at my work. After being on the phone with our network guy, he told me it was Back to My Mac, and it was flooding the firewall with a port scan, so I was blocked from access. Hopefully this info can help if the first fix doesn't.



[ Reply to This | # ]
10.5: Work around a potential AirPort connection glitch
Authored by: pauljlucas on Dec 16, '07 09:43:11AM

AFAIK, you can delete the Automatic setting -- there's nothing special about it -- and then rename Kludge to Automatic.

---
- Paul



[ Reply to This | # ]
10.5: Work around a potential AirPort connection glitch
Authored by: BuckarooToo on Dec 17, '07 06:27:37AM

YMMV. I tried it, and it didn't work. There is a voluminous post on Apple Discussions regarding the problems with AirPort under Leopard. Apple has yet to acknowledge the problem.



[ Reply to This | # ]
10.5: Work around a potential AirPort connection glitch
Authored by: Sven G on Dec 17, '07 11:13:01AM

A very annoying Leopard AirPort-related bug is, among others, that when you click on your AirPort base station icon in the Finder sidebar, often it only mounts the shared part of AirPort disk (and then only with a generic network drive icon), while the account-protected part doesn't mount (but the Finder seems to look for it forever). Force-quitting the Finder, unmounting the first disk and re-clicking on the two AirPort volumes usually fixes this problem: the volumes now both mount with their proper AirPort icon.

If one tries to automount the AirDisk at login by adding its volumes to the Login Items in Accounts (System Preferences), it usually automounts OK, but with the generic green network drive icons instead of the blue AirPort icons: another very strange bug!

Really, lots of bugs in this front...



[ Reply to This | # ]
10.5: Work around a potential AirPort connection glitch
Authored by: Sven G on Dec 17, '07 11:17:35AM

Ooops: the generic network drive icons are grey, of course (it's the Time Machine drive icon which is green).



[ Reply to This | # ]