was working fine, just ran latest system updates, rebooted from updates and i cant connect to the internet anymore, its connected to wifi, has an IP. it connects to skype though. no browser connectivity or other programs, itunes, app store, ect. anyone have any ideas?
not really an option, im at work with 120+ connected users, doubt they will dump the internet connection for me.
i also tried connecting to my droid as a wifi hotspot, no good, its not hardware related because neither wifi or wired internet will work.. its gotta be something in the software.. dont have time to rebuild the machine because i have to take it to nyc to do a live webcast on sunday.. too many apps i need to use there to do a rebuild.. this is soo frustrating.
Please put one of the following IPs into your brower (all cnn.com) and if you reach cnn.com, you definitely have a dns issue:
cnn.com. 0 IN A 22.214.171.124
cnn.com. 0 IN A 126.96.36.199
cnn.com. 0 IN A 188.8.131.52
cnn.com. 0 IN A 184.108.40.206
cnn.com. 0 IN A 220.127.116.11
If so, you need to get into the Network Properties, Advanced, and see what's in there for your DNS server. Ask your sys admin for the correct information.
ok, those last 4 connected.. i went in and cleared out my dns settings. put in some good ones from the network config on my ipad, its connected to the same router, and it still wont get anywhere this is so wierd..
but it doesnt work on my droid wifi hotspot either.. i guess i'll take the system and software disks home with me and test it on my home network where i have more control. i still dont get why it would work this morning, but then crap out after the restart... thanks for your help guys.
This is a rather common and annoying problem with Macs that connect to a number of networks. It seems particularly common when connecting to corporate networks like you seem to be. There's a very good chance it was your computer's Directory Services cache inhibiting your computer's ability to correctly resolve IPs.
Several Mac multi-utilities (like Cocktail or TinkerTool System) allow you to flush the cache. I use the latter, but the former is good too. You could also pay nothing and figure out how to do it with the command line, but I'm lazy. I find that doing this every few months helps keep my connection reliable at work.
this seems to happen when comcast sends bogus dns info to help redirect your browser to their activation dialogs as well, quite annoying, it doesn't seem to fix itelf easily, it loves to hang onto the bogus dns info
but, there is a windows 7 virtual machine on there, using fusion, that can connect to the web just fine
i tried the flushcache command in the terminal and it did not fix anything... should there be some kind of confirmation that it worked after i put in the command? it just goes to a new line on the terminal window..
Apple has released a knowledgebase article (reprinted here) that covers details regarding DNS server handling in 10.6 and the 10.6.3 update. In Mac OS X v10.6 and later, the search order of DNS servers specificed in Network preferences is dynamic, so that servers that don't respond are moved to the end of the search order. This provides performance and reliability improvements over previous Mac OS X versions, but it can lead to unexpected results where a strict search order is required in Mac OS X v10.6.
With Mac OS X v10.6.3 and later, DNS servers can be searched in a strict order by making a change to the mDNSResponder plist as an administrator. Learn how in this advanced article.
To search DNS servers in a strict order in Mac OS X v10.6.3 or later
Note: Making this change will result in DNS servers being tried in the specified search order for all queries, even if a server is not responsive. This may affect performance and reliability.
Log in as an administrator if you aren't already.
Back up the mDNSResponder.plist file if you haven't. To do this:
Open Terminal (in /Applications/Utilities)
Execute this command on a single line:
sudo mv /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist /System/Library/com.apple.mDNSResponder.plist_previous_LaunchDaemo n
(NOTE: Apple's article says to use "mv," but you should use "cp" in this command. Alternatively, just go to the mentioned folder via the Finder and copy the file to an alternate location.)
Open the com.apple.mDNSResponder.plist file in a text editor (the file is located in /System/Library/LaunchDaemons/ ).
In Mac OS X v10.6, the default DNS server searching behavior is that when a server does not return a result (returning SERV_FAIL for a query), and other servers are available to query, the server is temporarily disabled in the search order for about thirty seconds. If there is more than one server for the query and all of them have returned SERV_FAIL, the servers will be queried in the order that they were disabled (that is, the server that has been disabled the longest will be used first).
and now its happening to my own mac book pro, but only on the wifi, when i use a ethernet cable its fine! what gives with this! as many times as i have had it happen to me i cant believe its not a more common problem.