10.6.4 Update broke my internet access

Some usual questions: When you open Network Utility--

Do you have an IP address?
Does it say "Active"?
Can you Ping Apple.com?
Can you Ping 17.149.160.49? (also apple.com)

burgons --

What 3rd party apps/plugins do you have on there?
Also, did you ever download a special toolbar for a specific sit?

If you went from 10.5.8 to 10.6.4 Did you use the 10.6.4 combo?

Would upgrade in Safe mode with the combo and see if that helps

I had the same problem. I noticed that after the update Airport Utility was also broken - it did not see my two Airports (Express + Extreme) at all although in Network Preferences both were seen. I eventually decided to reinstall 10.6 from the retail Snow Leopard disk and applied the combo 10.6.4 updater in safe mode. That solved it.

Simon, if you’re trying to use your AirPort to connect to the outside world, try opening System Profiler, then click on Network: what does it show for the IPv4 Router and Subnet Masks fields? Do they correspond to the equivalent values on your Mac Pro? Do your MacBook Pro’s DNS Server Addresses, DHCP Server Responses Domain Name Servers, Routers, Server Identifier, and Subnet Mask all have reasonable values?

If your hub has the ability to filter access by MAC Address, is this currently enabled?

Do you happen to connect with a "MAC" address security access. when I upgraded teh address was wped and I needed to reenter it.

I had the same problems (self-assigned IP in the range 169.254.x.x and no internet connection) and tried everything suggested in the forums but none solved it.

I resorted to reinstalling 10.6.0 from my original SL install disc - it reinstalls all the system files but seems to keep all your files, folders and apps intact (BACKUP YOUR SYSTEM). Then I installed 10.6.3 combo patch and all works fine again. Took me about an hour (excluding full backup).

This describes the same problem I am having with no IP via DHCP when connect ethernet to corporate network. Mysteriously it will work on corporate network if connected wireless through airport or ethernet via a switch between computer and the wall. Looks like next step is to reload 10.6 from original disk!

I cheered too soon - at home, my wifi still doesn't work. Same problem as before. At work, however, it can connect perfectly fine. Is it a router issue then? I really don't understand anymore.

I've had this same issue since 10.6.4. At first I thought it was our Cisco AP's at work, then noticed every Windows laptop and my iPhone have no WiFi connection issues whatsoever.

At home I have an old Airport and had the same problem. My pings to the APs at both work and home jump from 1ms to 2000ms. This was a nonissue previous to 10.6.4.

It's become unusable at work and bearable at home.

Dear All

I wish to thank everyone (and others) for their feedback on this (and other posts on this topic) as my wife and I were also afflicted at the home office.

*My situation was also very curious*. Two macbook pros (MBpro) updated to 10.6.4 were not able to connect to the internet following the upgrade, however on the same home/office networking system, the one iMAc that *did not upgrade* was able to continue to work flawlessly. The 10.6.4 machines continued to work on our corporate exchange-based network without any problem.

I have some interesting observations from the home/office that might assist others:

*Scenario Home/Office:* Router D-Link 604+ connected by ethernet to two time capsules (TC). All hardware (MBPro x 3, Axiotron modbook, iphone x2, PS3, PSP etc) connected wirelessly to either of the TCs working flawlessly prior to upgrade.

*Situation post upgrade of 10.6.4 of macbook pros only:* iMac continued to work, macbook pros did not. They showed connection to TCs AND and active IP, but no traffic! No other signs of traffic at all through browsers or upload/download apps, *with the exception of skype* (very weird).

I could get MBpros to work using iMAC ethernet sharing (proxy hardwire- i.e. talking via 10.6.3). But I could NOT get MBPros to work with ethernet to either TC or D-Link directly (also very weird)- i.e. *NOT just a wireless problem, but a potential 'protocol' talking issue*

For MBPros I tried the following WITHOUT success:

Hard reset (power-down for 60mins) of all equipment (at numerous stages of the below)
IP reset from provider
Bypass TCs and direct wireless/hardwire to D-Link
Manual configuration of IP address (range) and router with/without DHCP
Deletion and soft re-installation of airport 'service' from network settings
Repaired permissions on wireless, altered security settings, renamed wireless network
MAC address enabling on/off
Delete system configuration folders
Backup from earlier Time Machine (prior to 10.6.4 upgrade)
Downgrade to 10.6.3

*My interpretation:* 10.6.4 changes the 'protocol' for IP traffic for select (but common) apps only with select (older?) routers and renders a working and apparently functional system with the inability to 'talk'.
(Curiously the 'change' cannot be re-instated with a downgrade of OSX and maybe related to user-specific settings/files that are not deleted during this process).
The consequence and presentation of the problem is also potentially specific for each Mac (as the 10.6.4 upgrade is specific for each hardware configuration) AND I believe is dependent on the make and model of the internet router (and/or possibly the configuration of the local network). At present this theory would fit most posts and observations I have read thus far.

*My solution:* Provider upgraded the router to Siemenns Gigaset SE567 and now everything works flawlessly in 10.6.4 (this was after false starting with an upgrade to another D-link model).

I hope this of use.

Regards
xSDP

Delete and then recreate your network servics in Network System Preferences.