----
You can use
/System/Library/CoreServices/Applications/Network Utility.app
or for older os's:
/applications/utilities/network utility
to diagnose the situation.
You can ping google.com.
Result:
Ping has started ...
PING google.com (64.233.167.99): 56 data bytes
64 bytes from 64.233.167.99: icmp_seq=0 ttl=244 time=215.362 ms
64 bytes from 64.233.167.99: icmp_seq=1 ttl=244 time=279.597 ms
64 bytes from 64.233.167.99: icmp_seq=2 ttl=244 time=189.747 ms
64 bytes from 64.233.167.99: icmp_seq=3 ttl=244 time=250.657 ms
64 bytes from 64.233.167.99: icmp_seq=4 ttl=244 time=183.232 ms
64 bytes from 64.233.167.99: icmp_seq=5 ttl=244 time=243.753 ms
64 bytes from 64.233.167.99: icmp_seq=6 ttl=244 time=173.108 ms
64 bytes from 64.233.167.99: icmp_seq=7 ttl=244 time=230.239 ms
64 bytes from 64.233.167.99: icmp_seq=8 ttl=244 time=180.639 ms
64 bytes from 64.233.167.99: icmp_seq=9 ttl=244 time=232.177 ms
--- google.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 173.108/217.851/279.597/33.615 ms
If that does not work, try pinging 64.233.167.99 Result:
Ping has started ...
PING 64.233.167.99 (64.233.167.99): 56 data bytes
64 bytes from 64.233.167.99: icmp_seq=0 ttl=244 time=189.655 ms
64 bytes from 64.233.167.99: icmp_seq=1 ttl=244 time=213.471 ms
64 bytes from 64.233.167.99: icmp_seq=2 ttl=244 time=257.873 ms
64 bytes from 64.233.167.99: icmp_seq=3 ttl=244 time=172.745 ms
64 bytes from 64.233.167.99: icmp_seq=4 ttl=244 time=226.723 ms
64 bytes from 64.233.167.99: icmp_seq=5 ttl=244 time=171.883 ms
64 bytes from 64.233.167.99: icmp_seq=6 ttl=244 time=260.308 ms
64 bytes from 64.233.167.99: icmp_seq=7 ttl=244 time=172.963 ms
64 bytes from 64.233.167.99: icmp_seq=8 ttl=244 time=198.840 ms
64 bytes from 64.233.167.99: icmp_seq=9 ttl=244 time=181.215 ms
--- 64.233.167.99 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 171.883/204.568/260.308/32.247 ms
If pinging 17.254.3.183 works but pinging Google.com doesn't. You have a bad DNS Server address.
I use Google.
Google provides free dns lookup. Their numbers are:
8.8.8.8
8.8.4.4
BDAqua suggests in a post.
You can use OpenDNS for looking up web addresses.
Put these numbers in Network>TCP/IP>DNS Servers for a try...
208.67.222.222
208.67.220.220
I think they now pretend you need to join to use, but you don't.
https://www.opendns.com/homenetwork/start/device/apple-osx-tiger
(Please note that you do not need to a joint Open DNS to use it.)
http://discussions.apple.com/message.jspa?messageID=5908432#5908432
fyi:
If Tiger has a working ethernet connection and configured to use dhcp, but doesn't find a dhcp server, Tiger will generate these addresses:
ip address: 169.254.193.199
mask: 255.255.255.0
Robert
=======================================================
I suggest that you try pinging Google.com.
Macintosh-HD -> Applications -> Utilities -> Terminal
# press return to run the command.
# settings for you communications port. en0 is the ethenet cable port
ifconfig
# gateway address
netstat -nr | grep default
mac $ ping -c4 google.com
PING google.com (64.233.187.99): 56 data bytes
64 bytes from 64.233.187.99: icmp_seq=0 ttl=245 time=177.617 ms
64 bytes from 64.233.187.99: icmp_seq=1 ttl=245 time=251.899 ms
64 bytes from 64.233.187.99: icmp_seq=2 ttl=245 time=169.291 ms
64 bytes from 64.233.187.99: icmp_seq=3 ttl=245 time=250.119 ms
--- google.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 169.291/212.232/251.899/38.894 ms
mac $ ping -c4 64.233.187.99
PING 64.233.187.99 (64.233.187.99): 56 data bytes
64 bytes from 64.233.187.99: icmp_seq=0 ttl=245 time=176.723 ms
64 bytes from 64.233.187.99: icmp_seq=1 ttl=245 time=247.889 ms
64 bytes from 64.233.187.99: icmp_seq=2 ttl=245 time=176.890 ms
64 bytes from 64.233.187.99: icmp_seq=3 ttl=245 time=244.623 ms
--- 64.233.187.99 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 176.723/211.531/247.889/34.744 ms
mac $
Analysis: If you cannot ping Goolge.com but you can ping 64.233.187.99, then you need to enter you dns address. For some reason Mac OS X sometimes doesn't set the dns. You can set it manually.
Try pinging your router.
mac $ ping -c4 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=255 time=0.958 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=0.950 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=255 time=0.955 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=255 time=0.984 ms
--- 192.168.1.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.950/0.962/0.984/0.013 ms
mac $
Try pinging your dns server 8.8.8.8 or 8.8.4.4
apple > system preferences > network
tcp/ip tab and enter address of dns servers
example 162.33.160.100
You will need to use a different number.
Robert