rui.pereira

Q: Can't connect to the internet!

Hey, guys, i'm having a problem connecting to internet.
Today, when I started my mac, it automatically connected to my home network, as usual, but it can't load any page. Other computers can access the same network with no problems! I also tried to connect to internet at school and it worked perfectly.

I've alreaday searched for solutions, but none has worked so far.

Any type for solution is welcome! Thank you!

MacBook Pro, OS X Mountain Lion (10.8.2)

Posted on Oct 1, 2012 2:46 PM

Close

Q: Can't connect to the internet!

  • All replies
  • Helpful answers

  • by sig,

    sig sig Oct 1, 2012 3:36 PM in response to rui.pereira
    Level 8 (35,798 points)
    Mac OS X
    Oct 1, 2012 3:36 PM in response to rui.pereira

    Reset your modem.

  • by rrahimi,

    rrahimi rrahimi Oct 1, 2012 3:43 PM in response to rui.pereira
    Level 3 (615 points)
    Oct 1, 2012 3:43 PM in response to rui.pereira

    Follow these troubleshooting steps:

     

    http://support.apple.com/kb/HT1714#one

  • by rui.pereira,

    rui.pereira rui.pereira Oct 3, 2012 3:07 PM in response to rui.pereira
    Level 1 (0 points)
    Oct 3, 2012 3:07 PM in response to rui.pereira

    I've reset my modem and the mac, nothing happened. also tried the suggestions on that link... nothing worked.

    Any ideas? It's really boring, to have a mac and to have to use a my old PC to access internet.

  • by rrahimi,

    rrahimi rrahimi Oct 3, 2012 8:07 PM in response to rui.pereira
    Level 3 (615 points)
    Oct 3, 2012 8:07 PM in response to rui.pereira

    Open the terminal. Type in this command:

     

    ping 8.8.8.8

     

    Let me know what happens. If it start printing results similar to this:

     

    64 bytes from 8.8.8.8: icmp_seq=0 ttl=55 time=42.200 ms

    64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=40.637 ms

    64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=42.077 ms

    64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=41.767 ms

     

    The at least we know you have basic connectivity. You can stop ping by pressing Ctrl-C

  • by Jwalls2111,

    Jwalls2111 Jwalls2111 Oct 4, 2012 5:37 PM in response to rrahimi
    Level 1 (0 points)
    Oct 4, 2012 5:37 PM in response to rrahimi

    I am having the same issue. I did the ping test and terminal and every thing seems to be fine. Every computer in the house, including my iPad can access the Internet. My mbp connects I just can't get a web page to load

  • by rrahimi,

    rrahimi rrahimi Oct 4, 2012 5:55 PM in response to Jwalls2111
    Level 3 (615 points)
    Oct 4, 2012 5:55 PM in response to Jwalls2111

    If this Ping test succeeds, that points to a possible DNS problem.

     

    Go to System Preferences --> Netowrk

     

    Select your Wifi network on the left and then click on

     

    Advanced... --> DNS

     

    Under DNS Servers list, click on the + button and add the following:

     

    8.8.8.8

     

    Also add this:

     

    8.8.4.4

     

    These two are Google's public DNS servers. If there are other items in the list, drag down to the bottom of the list so that the two above are the two on the top of the list.

     

    Press OK and then press Apply.

     

    Go to browser and try openning some website that didn't work before.

  • by Jwalls2111,

    Jwalls2111 Jwalls2111 Oct 4, 2012 6:04 PM in response to rrahimi
    Level 1 (0 points)
    Oct 4, 2012 6:04 PM in response to rrahimi

    Unfortunately that didn't seem to work. I've even tried connecting the computer to the modem via Ethernet, still to no avail.

  • by rrahimi,

    rrahimi rrahimi Oct 4, 2012 6:37 PM in response to Jwalls2111
    Level 3 (615 points)
    Oct 4, 2012 6:37 PM in response to Jwalls2111

    A few of Google's IP addresses are here:

     

    http://compnetworking.about.com/od/traceipaddresses/f/google-ip-address.htm

     

    Try one of them like http://74.125.224.72 and see if it opens google. (copy the full URL, not just the IP address).

     

    If that works, then the last thing I can think of is resetting mDNSResponder. I had DNS issues on Snow Leopard and this solved them, though I had to repeat it after earch restart.

     

    https://gist.github.com/1844353

     

    If it didn't work, then I got nothing. I'm assuming you have tried different browsers already.

  • by rui.pereira,

    rui.pereira rui.pereira Oct 8, 2012 1:22 AM in response to rui.pereira
    Level 1 (0 points)
    Oct 8, 2012 1:22 AM in response to rui.pereira

    I've tried every solution you presented here, and nothing worked. I know it is a problem with the DNS-something, but I still couldn't fix it. Can it be related to some setting in Mountain Lion?

  • by timeslut,

    timeslut timeslut Jan 31, 2013 2:32 AM in response to rui.pereira
    Level 1 (0 points)
    Jan 31, 2013 2:32 AM in response to rui.pereira

    i'm having this same problem- all other devices connect to the wi-fi. It's a sharehouse as well, and the only computer/hardware having any problem connecting to the internet is my macbook pro.

     

    i opened the terminal and typed ping 8.8.8.8...it came up with "host is down"

     

    I connect to a random neighbors unsecured network with the macbook pro. However, this is unstable and slow.

     

    Suggestisons? My iPhone and iPod touch connect fine to the wireless.

     

    -Tim

  • by timeslut,

    timeslut timeslut Jan 31, 2013 3:21 AM in response to timeslut
    Level 1 (0 points)
    Jan 31, 2013 3:21 AM in response to timeslut

    after an hour of searching and many methods, i discovered this incredibly simple fix:
    try disconnecting from the network and then go to "join other network" in the wi-fi menu. type in the name of your wi-fi network and type the password (you also need to tell what type of network security your wi-fi has). Hit the connect button and it should work.

  • by katzmopolitan,

    katzmopolitan katzmopolitan Mar 10, 2013 9:14 PM in response to rrahimi
    Level 1 (0 points)
    Mar 10, 2013 9:14 PM in response to rrahimi

    rrahimi,

     

    Thanks, your suggestion with mDNSResponder seemed to have worked, at least for now. It's a bit of an annoyance to do it every time I reboot but better than no internet...