2012 MacBook Pro Cannot access specific Websites

Associate
Joined
11 Apr 2011
Posts
48
Odd one this.

There are seven or eight specific websites that my macbook pro cannot access.
It's weird because any other device can access the websites and the macbook pro simply cannot.

It also isn't a router thing because I have the exact same issue from any network (e.g. if I log on at work, or tether to my mobile, or use public wifi - same websites, same issue - all other devices have no issue on any network).

The other 99.9% of the internet is flawless. It doesn't matter whether I use Chrome, Firefox or Safari - same issue.


I'm scratching my head! Anyone able to help?
 
Have you tried making a new network profile?

I'm not sure. If you mean systems preferences->Network then clicking the + and configuring a new wifi connection, then yes I just tried that. Made no odds. Not sure if I should be changing a configuration within it?

Any help sincerely appreciated.
 
On your MBP type:

Code:
nslookup <troublesome website address>

Do this for each website and then compare the answers with the output of the same command from a working computer on your network.

If the answers are different check the contents of your /etc/hosts file to make sure you have no entries for this sites.
 
On your MBP type:

Code:
nslookup <troublesome website address>

Do this for each website and then compare the answers with the output of the same command from a working computer on your network.

If the answers are different check the contents of your /etc/hosts file to make sure you have no entries for this sites.

Hi, I assumed that was a terminal command, sadly I only have the one Mac on my network at the moment so cannot replicate it with a working one. However.....

I did run the command for sites I know to be working, e.g. if I run it for the BBC which loads fine I get:

Server: 90.207.238.97
Address: 90.207.238.97#53
Non-authoritative answer:
www.bbc.com canonical name = www-bbc-com.bbc.net.uk.
Name: www-bbc-com.bbc.net.uk
Address: 212.58.246.94
Name: www-bbc-com.bbc.net.uk
Address: 212.58.246.95


HOWEVER - if I run it for any of the blocked sites I get, to pick one example, this:

Server: 90.207.238.97
Address: 90.207.238.97#53

Non-authoritative answer:
Name: www.dmgmedia.co.uk
Address: 5.79.36.94

And that's the lot. I may be grasping at straws but does that give a clue? How do I find these 'host files' and would flushing them somehow help?
 
What's an example of the "blocked" site?

That's a Sky DNS server, so I assume they're your ISP. For the BBC one above though, my Mac is using the local Sky router as DNS rather than the 90.x address.
 
Last edited:
What's an example of the "blocked" site?

That's a Sky DNS server, so I assume they're your ISP. For the BBC one above though, my Mac is using the local Sky router as DNS rather than the 90.x address.

www.dmgmedia.co.uk

Loads fine on my iphone. Works fine on my iphone, wont load on any network on my Mac. (yes my home ISP is Sky, but in terms of troubleshooting, I have the same issue on this Mac whatever network I'm connected so I don't think it is ISP/Router related - it has to be a local configuration on my Mac I think)
 
Same answer I get :
Server: 192.168.0.1
Address: 192.168.0.1#53

Non-authoritative answer:
Name: www.dmgmedia.co.uk
Address: 5.79.36.94

What's the DNS set to ?
(System Preferences/Network/Pick your NIC/Advanced/DNS)

If in doubt screengrab it (Cmd+Shift+4 then press space with the cursor over the window).
 
Hi Thanks for taking an interest in this. I'm really keen to sort it. My DNS has two IP addresses listed...

DNS Servers
90.207.238.97
90.207.238.99

Search Domain
WAG320N
 
The sites that do not load - do you see an error or a blank page in your browser?

In Chrome I get "OOOOps google chrome could not connect to this website" (or whatever that standard text is) In safari I just get the blue loading progress bar hang about a third in, like it is trying to connect but never actually does.
 
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.0.1 UGSc 312 0 en1
5 link#10 UC 2 0 ham0
5.255.255.255 ff:ff:ff:ff:ff:ff UHLWbI 0 12 ham0
127 localhost UCS 0 0 lo0
localhost localhost UH 8 3553 lo0
169.254 link#5 UCS 0 0 en1
192.168.0 link#5 UCS 4 0 en1
192.168.0.1 0:22:6b:fb:8f:95 UHLWIir 313 24 en1 1152
192.168.0.104 0:50:8d:98:7f:95 UHLWIi 1 103 en1 1185
192.168.0.105 7c:d1:c3:f1:f7:a5 UHLWI 0 0 en1 1067
192.168.0.107 localhost UHS 0 0 lo0
192.168.0.255 ff:ff:ff:ff:ff:ff UHLWbI 0 28 en1

Internet6:
Destination Gateway Flags Netif Expire
localhost localhost UHL lo0
2620:9b:: link#10 UC ham0
2620:9b::5a5:4b72 7a:79:5:a5:4b:72 UHL lo0
fe80::%lo0 localhost UcI lo0
localhost link#1 UHLI lo0
fe80::%en1 link#5 UCI en1
macpro1-5.local e0:f8:47:39:11:ba UHLI lo0
fe80::%ham0 link#10 UCI ham0
macpro1-5.local 7a:79:5:a5:4b:72 UHLI lo0
ff01::%lo0 localhost UmCI lo0
ff01::%en1 link#5 UmCI en1
ff01::%ham0 link#10 UmCI ham0
ff02::%lo0 localhost UmCI lo0
ff02::%en1 link#5 UmCI en1
ff02::%ham0 link#10 UmCI ham0



If you can make any sense of the above I salute you!
 
What happens if you traceroute website.com?

Also you only seem to have run one of my commands above :)
 
Hi Bes,

Thanks for helping on this - if I run the cat /etc/resolv.conf I get this:

#
# Mac OS X Notice
#
# This file is not used by the host name and address resolution
# or the DNS query routing mechanisms used by most processes on
# this Mac OS X system.
#
# This file is automatically generated.
#
nameserver 195.191.107.2
nameserver 195.191.106.2
nameserver 8.8.8.8


If I do traceroute I get (eventually):

traceroute to www.dmgmedia.co.uk (5.79.36.94), 64 hops max, 52 byte packets
1 * * *
2 *traceroute: sendto: No route to host
traceroute: wrote www.dmgmedia.co.uk 52 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote www.dmgmedia.co.uk 52 chars, ret=-1
*
traceroute: sendto: Host is down
3 traceroute: wrote www.dmgmedia.co.uk 52 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote www.dmgmedia.co.uk 52 chars, ret=-1
* *
4 * * *
5 *traceroute: sendto: No route to host
traceroute: wrote www.dmgmedia.co.uk 52 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote www.dmgmedia.co.uk 52 chars, ret=-1
*
traceroute: sendto: Host is down
6 traceroute: wrote www.dmgmedia.co.uk 52 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote www.dmgmedia.co.uk 52 chars, ret=-1
* *
7 * * *
8 * * *
traceroute: sendto: No route to host
9 traceroute: wrote www.dmgmedia.co.uk 52 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote www.dmgmedia.co.uk 52 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote www.dmgmedia.co.uk 52 chars, ret=-1


(and then I closed the terminal window....)

Whilst that was running I accessed the same website no problem from a Win 8 machine on the same network....
 
Ahhh I see the problem now...

Ok so basically all IP addresses beginning with 5 are using an interface called ham0 and not en1. Were you ever using a virtual interface or VPN client on that machine?

I will post a fix for you in the morning :)
 
Last edited:
So what's ham0?

Only thing I can think of that might create that would be Hamachi, but that's probably far too obvious.
 
It seems to be something that is created by LogMeIn - a virtual interface?

OP if you don't use it and have removed it, try deleting the application directory (if it is left behind) in (probably) single user mode and reboot.

Also I would see if there is an interface called ham0 listed under 'networks'. If you don't use LogMeIn, you could try removing it.

Finally, if none of that works/ you can't see that, you could use netstat to remove the static route.

something like sudo route -n delete 5.255.255.255 I think (Hard to get it right without trying).

Let me know if you need more help with any of that.
 
Last edited:
Back
Top Bottom