Since I am a student at the University of Minnesota I am constantly using my laptop on campus. The SSID for the University of Minnesota is" U of M Wireless" and I have it set in my wireless settings to automatically join this network. Just the other evening, when I was in my apartment and I turned my MacBook Pro on, I saw that it was trying to connect to an adhoc network also named U of M wireless. This scares me because someone could think that they are on a legit U of M wireless network but really be connecting to a rogue device. One would think that Leopard would be able to differentiate between connecting to a regular AP and an adhoc device. I am pretty sure that I saw that Tiger could do this differentiation and I am wondering why Leopard isn’t doing this.
If anyone else has had this same issue, leave a comment.
Entries (RSS)
November 25th, 2007 at 5:48 pm
I’m having a heap of issues with Leopard and wireless network since the upgrade to 10.5.1
Is hard to pinpoint what triggers it but it will randomly drop my preferred network and when I choose it, it’ll not accept the password.
I’m also having issues with servers just plain not being reached. Then I’ll copy paste the url into a new browser and it works. It’ll stay like that for that session till I logout or restart.
Annoying. Tiger anyone?
March 5th, 2008 at 3:12 pm
That’s a very odd issue I agree. You might want to try locating where the rouge signal is coming from, where it’s the strongest, to notify the owner. alternatively the school might be able to assist you if you contact tech support. They may just have a misconfigured access point.