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

poohat1000

macrumors 6502
Original poster
Nov 11, 2005
271
1
London
Hi i can connect to here and some other sites but it seems half the web i simply can't access. It's not a router problem, i have a pc on the same network that is working fine. I also have a macbook that is running fine... DNS issue perhaps? I have no idea.

please help, dont want to be stuck on that pc :'(
 
So you have this Mac, a MacBook, and a PC on the same router and the Mac you are on is the only one not able to connect to Google, Youtube, etc? Can't be a DNS issue or you would be seeing this happening to all your computers.

Have you tried restarting the computer or using another browser? If you are on a wireless connection, have you tried turning off Airport and the turning it back on?
 
yep


same thing in safari and ff, restart does nothing, same with airport

meebo works, msn doesn't, MSN SEARCH OF ALL THINGS DOES. google, yahoo dont - i get 404's
 
sorry its actually not a 404

its this :S

picture1pz8.jpg
 
Sure. Let's do a test to see if we can eliminate the browsers as the problem.

Go into terminal and type this:

telnet www.google.com 80

You should see something like this:

Trying 74.125.19.104...
Connected to www.l.google.com.
Escape character is '^]'.

Do you? If you do, type any character and hit return. You should get HTML text that includes:

<H1>Bad Request</H1>
Your client has issued a malformed or illegal request.

Do you get this stuff? If you do, do the telnet command again and send this:

GET / HTTP/1.1
host: www.google.com
<cr>
<cr>

You have to be fast with that. I used vi to create a text file with 4 lines. The first 2 lines contain the "GET" and "host" lines and the last two lines are just carriage returns. I then cat'ed the file and copied the four lines and then pasted them in after the telnet command was successful. Then you get a full page of HTML.

How does that work?

S-
 
i get

Trying 64.233.169.104...
telnet: connect to address 64.233.169.104: Connection refused
 
i get

Trying 64.233.169.104...
telnet: connect to address 64.233.169.104: Connection refused

Okay, the problem is not with the browsers. And your DNS is working fine too.

FYI: The IP address "64.233.169.104" belongs to the host "yo-in-f104.google.com" which is one of Google's many search hosts.

I'd be looking at firewalls at this point. Is something blocking port 80 from your Mac system?

S-
 
cheers guys, really appreciated.

I have the firewall turned off.

Its wireless, my macbook is fine. I'm posting from the problem computer at the moment. this site is fine.

I've looked in activity monitor for anything that might be blocking port 80... can't see anything unusual
 
poohat1000,

Go to the "Utilities" folder and run the "Network Utility". Select the "Netstat" tab and make sure the "Display routing table information" radio is selected. Then press the "Netstat" button. Report the results back here.

Next, in the "Network Utility", select the "Port Scan" tab and enter "www.google.com" in the text field. Check the "Only test ports between" checkbox and scan between ports 80 and 80. Report the results back to us.

S-
 
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.0.1 UGSc 702 14109 en1
127 localhost UCS 0 0 lo0
localhost localhost UH 0 3182 lo0
169.254 link#5 UCS 0 0 en1
192.168.0 link#5 UCS 2 0 en1
192.168.0.1 0:1b:2f:99:24:3e UHLW 708 30302 en1 1177
192.168.0.9 localhost UHS 1 52023 lo0
192.168.0.255 link#5 UHLWb 1 1173 en1

Internet6:
Destination Gateway Flags Netif Expire
localhost link#1 UHL lo0
fe80::%lo0 fe80::1%lo0 Uc lo0
fe80::1%lo0 link#1 UHL lo0
fe80::%en1 link#5 UC en1
Sean-Millers-Compu 0:d:93:80:18:bf UHL lo0
ff01:: localhost U lo0
ff02:: fe80::1%lo0 UC lo0


=======================================

Port Scan has started ...

Port Scanning host: 66.102.9.99

Port Scan has completed ...
 
The routing table looks normal. But you are still being blocked on port 80 when accessing "www.google.com" for some reason.

I have a hard time believing that your Mac is the problem here.

Okay. The next step is plug your Mac directly into the link your router is now plugged into and configure the Mac the same way your router now is. If that doesn't work...then something really strange is going on. Either way, this will tell us where the problem is.

First, try this from within Terminal:

Code:
route get www.google.com

You should get something like this:

Code:
   route to: cf-in-f104.google.com
destination: cf-in-f104.google.com
    gateway: 192.168.1.1
  interface: en0
      flags: <UP,GATEWAY,HOST,DONE,WASCLONED,PROTO3>
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire
       0         0         0         0         0         0      1500       157

Report back the result. Then try what I suggested above.

S-
 
Code:
 route to: yo-in-f104.google.com
destination: default
       mask: default
    gateway: 192.168.0.1
  interface: en1
      flags: <UP,GATEWAY,DONE,STATIC,PRCLONING>
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire
       0         0         0         0         0         0      1500         0
 
poohat1000,

That's different than what I posted but I did some more "route get" commands and found many that looked like what you got.

So the next test is to plug the Mac in place of your router. If you can't get to google.com then, but can get to this forum, we know the problem is in your Mac. If you can get to Google, we know the problem is either how you have the Mac IP stack setup when using the router or how the router is handling your Mac.

S-
 
Here is another idea:

Let's reset your network settings to factory default and then configure them again. To do that, lets rename the plist file that contains the settings and reboot. Here are the commands to rename the plist file:

Code:
cd /Library/Preferences/SystemConfiguration/
mv preferences.plist preferences.plist.sav

Then reboot the system. If you want the old settings back later, you can reverse the "cp" command. Enter the network information again and see what happens.

S-
 
This is what you get if you forget the "80":

Code:
$ telnet 64.233.169.104 
Trying 64.233.169.104...
telnet: connect to address 64.233.169.104: Operation timed out
telnet: Unable to connect to remote host

So I suspect he put the "80" in...

S-
 
Here is another idea:

Let's reset your network settings to factory default and then configure them again. To do that, lets rename the plist file that contains the settings and reboot. Here are the commands to rename the plist file:

Code:
cd /Library/Preferences/SystemConfiguration/
mv preferences.plist preferences.plist.sav

Then reboot the system. If you want the old settings back later, you can reverse the "cp" command. Enter the network information again and see what happens.

S-


mv: rename preferences.plist to preferences.plist.sav: Permission denied
 
sidewinder:

Yes, it appears you are correct. I thought I had tried it that way as well, but apparently I did something else.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.