osx - My Mac is not responding for this own IP, but it's ok for everything else
2014-04
Lordn__n
My Mac has the IP 192.168.1.123 and this network settings:
IP: 192.168.1.123
Net Mask: 255.255.255.0
Router: 192.168.1.3
DNS: 208.67.222.222, 8.8.8.8
and apache answer correctly if I request http://localhost http://127.0.0.1
but if I request http://192.168.1.123 it gives me a "ERR_CONNECTION_TIMED_OUT"
If I do a ping to 192.168.1.123 it show:
$ ping 192.168.1.123
PING 192.168.1.123 (192.168.1.123): 56 data bytes
64 bytes from 192.168.1.123: icmp_seq=0 ttl=64 time=0.065 ms
64 bytes from 192.168.1.123: icmp_seq=1 ttl=64 time=0.077 ms
64 bytes from 192.168.1.123: icmp_seq=2 ttl=64 time=0.067 ms
^C
--- 192.168.1.123 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.065/0.070/0.077/0.005 ms
If I do a traceroute:
$ traceroute 192.168.1.123
traceroute to 192.168.1.123 (192.168.1.123), 64 hops max, 52 byte packets
1 192.168.1.123 (192.168.1.123) 0.181 ms 0.039 ms 0.030 ms
BUT! if ANY other computer do a request to http://192.168.1.123 it show correctly!
The only weird thing I could found was that the previous user deleted this lines from /etc/hosts
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
I've already put those lines in /etc/hosts and restarted the mac... but the problem continue... any suggestions?
WreithKassan
Sorry, I am changing my input to appease the jerks. So, make sure that apache is listening on that IP as well. In httpd.conf, add Listen 192.168.#.#:80
nbrogi
I don't know if this might help, but I recently found out that if connected to the same network you can also use http://computer-name.local
For instance, I have http://macbook-air.local and it shows Apache.
It's a lot more convenient, as your IP might change often...
angelamia
I'm having an issue on a Macbook Pro running Mac OS X 10.5, I'm unable to visit certain websites such as: "themarchesa.com"
On other computers in the same LAN network connected over wifi I'm able to see those sites fine and run a traceroute succesfully.
When I run a traceroute from the terminal it doesn't even appear to go out to the wireless router gateway:
angela-dions-macbook-pro:~ Angie$ traceroute themarchesa.com
traceroute to themarchesa.com (64.202.189.170), 64 hops max, 40 byte packets
traceroute: sendto: No route to host
1 traceroute: wrote themarchesa.com 40 chars, ret=-1
*traceroute: sendto: No route to host
traceroute: wrote themarchesa.com 40 chars, ret=-1
When I run the same command on google.com it looks different:
angela-dions-macbook-pro:~ Angie$ traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 74.125.227.18
traceroute to google.com (74.125.227.18), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 3.768 ms 6.499 ms 6.716 ms
2 * * *
3 gig3-11.austtxk-rtr2.austin.rr.com (66.68.1.253) 15.161 ms 24.131 ms 16.291 ms
4 Gi0-2-1-1.austtxrdcsc-rtr2.austin.rr.com (24.27.12.174) 18.678 ms 26.495 ms 16.064 ms
5 gig6-3-0.dllatxl3-rtr1.texas.rr.com (72.179.205.76) 15.589 ms 18.537 ms 18.427 ms
6 ae-4-0.cr0.dfw10.tbone.rr.com (66.109.6.88) 16.404 ms 24.141 ms 27.108 ms
7 ae-1-0.pr0.dfw10.tbone.rr.com (66.109.6.179) 25.488 ms 19.721 ms 20.257 ms
8 74.125.48.65 (74.125.48.65) 20.165 ms 22.483 ms 21.444 ms
9 72.14.233.65 (72.14.233.65) 20.186 ms 25.394 ms 20.003 ms
10 216.239.47.54 (216.239.47.54) 24.236 ms 37.011 ms 38.239 ms
11 74.125.227.18 (74.125.227.18) 27.468 ms 27.292 ms 20.032 ms
EDIT: Here's the output of route get on the IP address:
angela-dions-macbook-pro:~ Angie$ route get 64.202.189.170
route to: pwfwd-v01.prod.mesa1.secureserver.net
destination: default
mask: default
gateway: 192.168.1.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
Also here's my routing table information if that helps out (what else could cause this to happen). I'm able to run traceroute and visit the website on other machines on the same LAN (connected to the same router over wifi).
angela-dions-macbook-pro:~ Angie$ netstat -rn
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGSc 30 0 en1
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 1 19326 lo0
169.254 link#5 UCS 0 0 en1
192.168.1 link#5 UCS 4 0 en1
192.168.1.1 0:18:f8:b7:45:7c UHLW 26 112 en1 955
192.168.1.107 7c:6d:62:d2:43:99 UHLW 0 0 en1 1198
192.168.1.111 127.0.0.1 UHS 0 0 lo0
192.168.1.255 link#5 UHLWb 3 18 en1
Internet6:
Destination Gateway Flags Netif Expire
::1 link#1 UHL lo0
fe80::%lo0/64 fe80::1%lo0 Uc lo0
fe80::1%lo0 link#1 UHL lo0
fe80::%en1/64 link#5 UC en1
fe80::21f:5bff:fec7:aed7%en1 0:1f:5b:c7:ae:d7 UHLW en1
fe80::223:6cff:fe88:f0bd%en1 0:23:6c:88:f0:bd UHL lo0
ff01::/32 ::1 U lo0
ff02::/32 fe80::1%lo0 UC lo0
ff02::/32 link#5 UC en1
I'm not sure what else I can do to debug this issue, what should I use to help debug and fix this issue?
There were some people that ran into a similiar issue and used some cache cleaning tools (but it seemed like the problem kept popping up, feels almost like a virus?):
- Problems connecting to a few sites on OS X- google cached version (the original link seems dead)
angelamia
The issue turned out to be Peer Guardian, I had to disable the filters and then I was able to hit those websites.
Ingmar Hupp
Transmission has built-in block list support, which means you don't need to use Peer Guardian, avoiding such issues.