Can't connect to my company's wireless network after 10.6
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I was connected when I upgraded, but as soon as it restarted I can't re-connect, or I do get connected and it says "No IP Address".
The network is a WPA network. I've removed it from the list of saved networks, deleted the com.apple.airport pref file and rebooted but it is not picking up the settings for the network correctly. When I change them to what I think are correct it still doesn't work.
Also, while in the Network pref pane It added the network as a 802.1x network, but when I click connect it just hangs.
A couple times it has connected but about 10 sec later an "!" appears over the indicator and then it keeps disconnecting/reconnecting.
Any ideas?
15 replies
Sign in or join Beachball Help to reply.
- 0
Körnchen ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Same Problem here!
Somebody?
- 0
phammen ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Similar problem here on two different computers. Both worked before upgrade, neither works after. Both are attempting to connect using WPA2 Enterprise. Connection fails and the "!" appears over the indicator. "No IP Address" changes to "Self Assigned IP" after about 10 sec.
- 0
adsized ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have the same problem. As soon as I try to connect to my network (Fritz Box Fon 7140 with WPA encryption), it will either connect and not get an ip address, not connect and give me a connection timed out error or not my network won't show up in the networks list. I connected to a public hotspot it connects and managed to get access to the internet, however after a few minutes the connection dropped.
Someone got a possible solution?
Message was edited by: adsized
- 0
SDuque ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Just had a similar problem; after upgrading to Snow Leopard could not get online via Airport even though the signal indicator suggested that I was connected. The weird (and lucky) thing is I have access to another wifi source and this does work! So heaven knows what is going on. Could it be that the network being used immediately prior to upgrade somehow gets compromised. Anyway, if you try another network, it might work. Sorry I could not be of more help.
SD
- 0
Mark Burris ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
My problem: I cannot connect on my laptop, though I can connect with no issues with my desktop.
MacBook is connected to the Airport network, but no internet connection.
- 0
adsized ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I can now connect to my network! All it needed was for me to plug an ethernet cable in for a few minutes and then unplug it. I then tried to connect to my wireless network again and it worked.
Hope this helps someone.
- 0
- 0
Per Ola Clemedtson ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I had the same problem, uppgraded a MacBook Unibody, but I found out that by renewing the DHCP in advanced settings for Airport solved the problem and gave connection to Internet. Might work for more?
- 0
Körnchen ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Didn't work for me! (Renewing DHCP Lease)
When I
manually configure IPv4, I shortly connect to the Network but the connection is lost immediately!
When using
DHCP, that doesn't work at all!
When using *DHCP with manual address*, it's the same problem as with
manuallyLooking forward to hear something, but i'm sceptical!
Hope we don't have to wait for the first update!Greetings
- 0
SDuque ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
OK, I think I may have a solution. Check the airport indicator to see if padlock icon is next to the ticked network name, if it is, the security system is denying access. I reset my security settings on the router using WEP PASSWORD and now it works. Good luck! SD
- 0
Körnchen ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
This doesn't sound like a good solution - decrease the security of the network by using WEP - only to get connected!
Had those kind of problems with Ubuntu some
years ago!
I mean only be able to connect to WEP secured Networks!Good for you, but I'm not happy with that!
Or did I misunderstand you? - 0
SDuque ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hey, it may not be perfect but at least it gets you online. If you have a better idea let's hear it!
- 0
tndirishfan ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Well, I don't know what the issue is, but after just leaving it alone for an hour or so I came back and selected the network from the airport list and it worked. I don't know what the problem is but when I restarted I had the same problem as before, waited about 15 min and tried again & it worked.
Since others are having the same issue seems like it's an OS issue and not a network issue?
- 0
dannyboy.longstreet ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Yup, I am having the same problem, I just assume go back to regular Leapord but that means a clean install and I don't really care to do that. The solutions seem rediculous, just wait and meaybe it will work after an hour? Really? Or restart my router, tried that and nothing. Changed the security to nothing and I still couldn't connect. This is redicuolous, Thanks Apple for your attempts to be like Microsoft and put out a crap product. To me, this is unacceptable. Beta testing should have identified the problem and they should have fixed it before release. Now, apparently, there are a bunch of users who have airport issues. If anyone has a real solution, please provide it, otherwise, Apple needs to get their, you-know-what together and fix the problem asap.
- 0
routertyty ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Seems I found a workaround. I edited the network location by adding a new one. network came up instantly. DHCP took a bit but eventually came. Hope this helps.