tag:blogger.com,1999:blog-1431617529154334054.post826401302547606517..comments2024-02-07T18:29:19.668-05:00Comments on Bodega Pop: Alton Ellis | Get Ready for Rock Reggae SteadyGaryhttp://www.blogger.com/profile/06115441682219034891noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-1431617529154334054.post-4078405314439369362013-10-16T09:23:01.830-04:002013-10-16T09:23:01.830-04:00Grrr, not working, both with Chrome and Safari. De...Grrr, not working, both with Chrome and Safari. Desperate to listen to this. Help?Ross Brownhttps://www.blogger.com/profile/08734812782982659136noreply@blogger.comtag:blogger.com,1999:blog-1431617529154334054.post-44958339651066229862012-09-10T16:24:45.036-04:002012-09-10T16:24:45.036-04:00I get that sometimes using Google Chrome. I would ...I get that sometimes using Google Chrome. I would first try accessing it through another browser (Firefox, Safari or Internet Explorer).<br /><br />It might be some sort of setting issue in Google Chrome, I don't know.<br /><br />I'm accessing it through Firefox now and it's fine.Garyhttps://www.blogger.com/profile/06115441682219034891noreply@blogger.comtag:blogger.com,1999:blog-1431617529154334054.post-66025838557799780062012-09-10T16:21:31.220-04:002012-09-10T16:21:31.220-04:00I'll try again later. This what I see:
Oops! ...I'll try again later. This what I see:<br /><br />Oops! Google Chrome could not find www.divshare.com<br /><br />or:<br />This webpage is not available<br />The server at www.divshare.com can't be found, because the DNS lookup failed. DNS is the network service that translates a website's name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network.<br />Here are some suggestions:<br />Reload this webpage later.<br />Check your Internet connection. Restart any router, modem, or other network devices you may be using.<br />Check your DNS settings. Contact your network administrator if you're not sure what this means.<br />Try disabling network prediction by following these steps: Go to the wrench menu > Settings > Show advanced settings... and deselect "Predict network actions to improve page load performance." If this does not resolve the issue, we recommend selecting this option again for improved performance.<br />Add Google Chrome as a permitted program in your firewall's or antivirus software's settings. If it is already a permitted program, try deleting it from the list of permitted programs and adding it again.<br />If you use a proxy server, check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server, adjust your proxy settings: Go to the wrench menu > Settings > Show advanced settings... > Change proxy settings... > LAN Settings and deselect the "Use a proxy server for your LAN" checkbox.<br />Error 105 (net::ERR_NAME_NOT_RESOLVED): Unable to resolve the server's DNS address.Barronhttps://www.blogger.com/profile/10471842428666128664noreply@blogger.comtag:blogger.com,1999:blog-1431617529154334054.post-77063325180648111682012-09-10T16:05:31.910-04:002012-09-10T16:05:31.910-04:00Link seems to be working now; please try again!Link seems to be working now; please try again!Garyhttps://www.blogger.com/profile/06115441682219034891noreply@blogger.comtag:blogger.com,1999:blog-1431617529154334054.post-55354828838740432422012-09-10T14:16:35.448-04:002012-09-10T14:16:35.448-04:00Looks great, but the link doesn't work.Looks great, but the link doesn't work.Barronhttps://www.blogger.com/profile/10471842428666128664noreply@blogger.com