Safari is the only browser that Microsoft officially supports for use with SharePoint on OS X clients, and offers the best experience. For limitations on Microsoft's support of SharePoint with Safari, see Plan browser support (SharePoint Server 2010). Jump to On Mac OS X - Open the Dashlane application and select Dashlane → Install Browser Extensions in the menu bar at the top of the screen.
I also have the same problem. Using a 2009 Macbook Pro 17'. I7/4gb/500gb OSX Mountain Lion updated to 10.8.5. I tried to fix it by reinstalling to Snow Leopard (Factory Settings), The problem disappeared at Snow Leopard but after going for Mountain Lion 10.8, the same problem appeared. Updating to 10.8.5 didn't solve the problem as well I still have internet and can still connect to Apple.com and Yahoo.com via Safari. Problem Number 1: Google doesn't load in Safari. Problem Number 2: Can't connect to App Store and iTunes Store.
If i use Chrome, i can load Google.com. The bigger problem is that i can't open app store and iTunes Store. Also, i really prefer using Safari over Chrome.
Hope someone can help. I also have the same problem.
Using a 2009 Macbook Pro 17'. I7/4gb/500gb OSX Mountain Lion updated to 10.8.5. I tried to fix it by reinstalling to Snow Leopard (Factory Settings), The problem disappeared at Snow Leopard but after going for Mountain Lion 10.8, the same problem appeared. Updating to 10.8.5 didn't solve the problem as well I still have internet and can still connect to Apple.com and Yahoo.com via Safari.
Problem Number 1: Google doesn't load in Safari. Problem Number 2: Can't connect to App Store and iTunes Store. If i use Chrome, i can load Google.com. The bigger problem is that i can't open app store and iTunes Store. Also, i really prefer using Safari over Chrome.
![10.5.8 10.5.8](/uploads/1/2/5/4/125483123/512539226.png)
Hope someone can help. Take each of the following steps that you haven't already tried until the issue is resolved. Back up all data before making any changes. Step 1 Check the of the service. If it's down, wait tor it to come back up. There may be a localized outage, even if the status indicator is green.
Step 2 Check that the date (including the year) and time shown by your system clock are correct. Step 3 Restart your router and broadband device, if different. Step 4 If you connect to the Internet through an HTTPS or SOCKS proxy server, follow the instructions in, or deselect the proxy entirely. Step 5 Boot in and try again. Step 6 Make sure aren't active for your account.
Step 7 Follow the instructions in to change your DNS settings. If there's no change, revert the settimgs. Step 8 If possible, test on a different network, such as a public Wi-Fi hotspot or the cellular network of your phone. Step 9 Launch the Keychain Access application. In the Keychains list, there should be an item named System. If not, select. From the menu bar, select Keychain Access ▹ Preferences ▹ Certificates There are three menus in the window.
Change the selection in the top two to Best attempt, and in the bottom one to CRL. Next, select the login keychain. Delete any expired or otherwise invalid certificates. Log out, log back in, and test. Step 10 Launch the Activity Monitor application. Select All Processes from the menu in the toolbar of the Activity Monitor window, if not already selected.
Enter 'ocspd' (without the quotes) in the 'Filter' text field. Is a process with that name listed? If not, back up all data, then triple-click anywhere in the line of text below on this page to select it: /var/db/crls Copy the selected text to the Clipboard ( command-C). In the Finder, select Go ▹ Go to Folder. From the menu bar, paste into the box that opens ( command-V). You won't see what you pasted because a line break is included. Press return.
Move all the files in the folder that opens to the Trash. You’ll be prompted for your administrator password. Reboot, empty the Trash, and test.
Step 11 If you've moved to a different country, select Store ▹ View My Account from the App Store menu bar, then click Change Country or Region and update your billing information. I had this problem after medling with my dlink router that is connected to my cable modem. I updated the router to open a couple of VPN ports so I can run a server. While my desktop computers could access google, my macbook air could not. I have an Airport Extreme connected to the DLINK router. The macbook connects to the Airport.
I tried a number of software steps and I even powered down the airport extreme. However, that did not go far enough. I had to go back and power down the whole LAN and then power back on slowly from the cable modem, the DLINK router, and then the airport extreme. Afterwhich, I was able to surf to Google and wherever else I wanted to go. Finally solved this for my brand new Mac Air after hours of searching today! (helped a lot by this thread).
It was this specific Certificate that is the problem, at least it was for me: In Keychain Access, System Roots (not System): Verisign Class 3 Public Primary Certification Authority. I needed to open this and switch Trust / 'When Using this Certificate' options to 'System Default', then verify with password. (They previously read Always Trust). This cured the following problems for me, showing how important this certificate apparently is:. Itunes Store: no access (certificate warnings).
App Store: no access (showed 'no internet connection'). Software Update: not working, no download. Various websites including Twitter, icloud and apple support: https ruled through, 'this certificate was signed by an untrusted issuer' warning.
Some Images missing on other sites that I could access. Very slow loading of some websites that I could access. (Possibly) inability to re-install OSX Recovery Mode, which kept timing out. (This was final option suggested by Apple Support, after a 45 minute phone call) It was the Twitter site that clued me in to the solution, as, reading the Twitter Certificate, both it and more importantly its 'parent' certificate, Verisign, had red crosses next to them, although they appeared normal within Keychain Access. There is a lot of not quite precise information around about this, apparently. Linc's advice (for which thanks very much) is broadly correct about the certificates, but I had to look in System Roots, not System to find the faulty certificate.
Examining a certificate such as the faulty Twitter certificate as described above may help you find the cause in your case, and this should hopefully fix all the problems at once. Apple Footer. This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums.
Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the.