Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

icafe

macrumors newbie
Original poster
Nov 11, 2006
17
0
San Francisco, CA.
So all of a sudden my web browsers—Safari, IE, Firefox—stopped working yesterday through a wireless connection. I can still check my email through Mail and chat on AOL IM, but I can't surf the web. My toolbar says I have a full connection too. Any ideas on what's causing this problem?

Thanks!
 
How are you connected? (using router, direct to cable/dsl modem, or?)

I almost sounds like a problem with accessing your DNS, but not if Mail is working.

You might be able to get more information on what's happening by using the network diagnostics.

You will find it here: System Preferences > Network. Click on "Assist me...", then click on "Diagnostics..."
 
network diagnostics says my internet connection is fine after going through all the setting.

this is what i get when i ping www.google.com before aborting it.

Last login: Sat Nov 11 12:42:27 on console
Welcome to Darwin!
Macintosh-7:~ username$ ping www.google.com
PING www.l.google.com (66.102.7.104): 56 data bytes
64 bytes from 66.102.7.104: icmp_seq=0 ttl=243 time=25.503 ms
64 bytes from 66.102.7.104: icmp_seq=1 ttl=243 time=26.006 ms
64 bytes from 66.102.7.104: icmp_seq=2 ttl=243 time=23.716 ms
64 bytes from 66.102.7.104: icmp_seq=3 ttl=243 time=24.597 ms
64 bytes from 66.102.7.104: icmp_seq=4 ttl=243 time=23.625 ms
64 bytes from 66.102.7.104: icmp_seq=5 ttl=243 time=24.805 ms
64 bytes from 66.102.7.104: icmp_seq=6 ttl=243 time=23.914 ms
64 bytes from 66.102.7.104: icmp_seq=7 ttl=243 time=24.290 ms
64 bytes from 66.102.7.104: icmp_seq=8 ttl=243 time=24.242 ms
64 bytes from 66.102.7.104: icmp_seq=9 ttl=243 time=24.432 ms
64 bytes from 66.102.7.104: icmp_seq=10 ttl=243 time=24.465 ms
64 bytes from 66.102.7.104: icmp_seq=11 ttl=243 time=23.593 ms
64 bytes from 66.102.7.104: icmp_seq=12 ttl=243 time=24.673 ms
64 bytes from 66.102.7.104: icmp_seq=13 ttl=243 time=23.829 ms
64 bytes from 66.102.7.104: icmp_seq=14 ttl=243 time=24.942 ms
64 bytes from 66.102.7.104: icmp_seq=15 ttl=243 time=24.064 ms
64 bytes from 66.102.7.104: icmp_seq=16 ttl=243 time=23.157 ms
64 bytes from 66.102.7.104: icmp_seq=17 ttl=243 time=24.659 ms
64 bytes from 66.102.7.104: icmp_seq=18 ttl=243 time=24.949 ms
64 bytes from 66.102.7.104: icmp_seq=19 ttl=243 time=24.050 ms
64 bytes from 66.102.7.104: icmp_seq=20 ttl=243 time=23.281 ms
64 bytes from 66.102.7.104: icmp_seq=21 ttl=243 time=24.271 ms
64 bytes from 66.102.7.104: icmp_seq=22 ttl=243 time=23.400 ms
64 bytes from 66.102.7.104: icmp_seq=23 ttl=243 time=24.773 ms
64 bytes from 66.102.7.104: icmp_seq=24 ttl=243 time=23.653 ms
64 bytes from 66.102.7.104: icmp_seq=25 ttl=243 time=24.948 ms
64 bytes from 66.102.7.104: icmp_seq=26 ttl=243 time=23.856 ms
64 bytes from 66.102.7.104: icmp_seq=27 ttl=243 time=25.140 ms
64 bytes from 66.102.7.104: icmp_seq=28 ttl=243 time=24.104 ms
64 bytes from 66.102.7.104: icmp_seq=29 ttl=243 time=23.516 ms
64 bytes from 66.102.7.104: icmp_seq=30 ttl=243 time=24.294 ms
64 bytes from 66.102.7.104: icmp_seq=31 ttl=243 time=23.466 ms
64 bytes from 66.102.7.104: icmp_seq=32 ttl=243 time=24.598 ms
64 bytes from 66.102.7.104: icmp_seq=33 ttl=243 time=23.643 ms
64 bytes from 66.102.7.104: icmp_seq=34 ttl=243 time=24.974 ms
64 bytes from 66.102.7.104: icmp_seq=35 ttl=243 time=24.247 ms
64 bytes from 66.102.7.104: icmp_seq=36 ttl=243 time=25.489 ms
64 bytes from 66.102.7.104: icmp_seq=37 ttl=243 time=24.594 ms
64 bytes from 66.102.7.104: icmp_seq=38 ttl=243 time=24.900 ms
64 bytes from 66.102.7.104: icmp_seq=39 ttl=243 time=25.069 ms
64 bytes from 66.102.7.104: icmp_seq=40 ttl=243 time=25.107 ms
64 bytes from 66.102.7.104: icmp_seq=41 ttl=243 time=25.755 ms
64 bytes from 66.102.7.104: icmp_seq=42 ttl=243 time=23.336 ms
^C
--- www.l.google.com ping statistics ---
43 packets transmitted, 43 packets received, 0% packet loss
round-trip min/avg/max/stddev = 23.157/24.370/26.006/0.699 ms
Macintosh-7:~ username$
 
The ping was successful, which means you are connected, and the name server is working properly (DNS). Only one service (web) failing might mean a port is being blocked.

What sort of network are you connected to? (your own, company, school?)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.