ping responds on one macbook pro but not on another

Question

Level 1

0 points

ping responds on one macbook pro but not on another

Hi All

I've got two macbook pros (different generations). They are both configured as follows:

o/s = 10.5.8
ipfw list = 65535 allow ip from any to any
system preferences :
firewall> allow all incoming connections
sharing> all off
both on same LAN.

From my windows pc I can ping one of them (the older one), but not the other.

Anyone had the same, or any ideas how to resolve?

Thanks!

macbook pro, Mac OS X (10.5.8)

Posted on Nov 7, 2010 1:13 AM

Reply

Answer 1

paulito Author

Level 1

0 points

Nov 7, 2010 1:29 AM in response to paulito

some further information I thought my be useful:

ifconfig (from the mac that I can ping)

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0 mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:16:cb:91:87:dd
media: autoselect status: inactive

supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 2030
lladdr 00:16:cb:ff:fe:60:12:38
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::216:cbff:fe08:ebae%en1 prefixlen 64 scopeid 0x6
inet 192.160.0.9 netmask 0xffffff00 broadcast 192.160.0.255
ether 00:16:cb:08:eb:ae
media: autoselect status: active
supported media: autoselect
vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.128.1 netmask 0xffffff00 broadcast 192.168.128.255
ether 00:50:56:c0:00:08
vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 172.16.234.1 netmask 0xffffff00 broadcast 172.16.234.255
ether 00:50:56:c0:00:01
en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::210:32ff:fe54:7698%en3 prefixlen 64 scopeid 0x9
ether 00:10:32:54:76:98
media: autoselect status: active
supported media: autoselect
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::201:23ff:fe45:6789%en2 prefixlen 64 scopeid 0xa
ether 00:01:23:45:67:89
media: autoselect status: active
supported media: autoselect

ifconfig (from the mac that I can't ping)

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fd53:7c5a:996:830b:21f:5bff:fef4:825c prefixlen 128
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0 mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:1f:5b:f4:82:5c
media: autoselect status: inactive
supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 00:1f:f3:ff:fe:2a:d3:fc
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::21e:c2ff:fec5:76ba%en1 prefixlen 64 scopeid 0x6
inet 192.160.0.6 netmask 0xffffff00 broadcast 192.160.0.255
ether 00:1e:c2:c5:76:ba
media: autoselect status: active
supported media: autoselect
en7: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
ether 54:55:43:44:52:00
media: autoselect status: inactive
supported media: autoselect
Check Point Virtual Network Adapter
vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.65.1 netmask 0xffffff00 broadcast 192.168.65.255
ether 00:50:56:c0:00:08
vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.171.1 netmask 0xffffff00 broadcast 192.168.171.255
ether 00:50:56:c0:00:01
vboxnet0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 0a:00:27:00:00:00

Reply

Answer 2

Nov 7, 2010 6:20 AM in response to paulito

Hi
On the Mac not responding to ping, you could try pinging the loopback (127.0.0.1) to check if it can even be pinged! If that fails, check:

System Preferences > Security > Firewall > (unlock, if needed) > Advanced > Stealth Mode check box.

If Stealth Mode is on (checked), the computer won't respond to any ICMP requests, like ping.

If that's not it, make sure the Mac is connected to the network and also try pinging the router/gateway/www.google.com from that Mac to make sure the connection is working. I have sometimes experienced that even when Airport is connected, I'm not able to access the network or ping the router. In such a case, switching Airport off and on again usually works.

Post again if you have problems!

--Arunjit

Reply

Answer 3

paulito Author

Level 1

0 points

Nov 7, 2010 12:20 PM in response to arunjitsingh

Hi Arunjit - thanks for your reply.

System Preferences > Security > Firewall > (unlock, if needed) > Advanced > Stealth Mode check box.

is grayed out, as I have 'Allow all incoming connections' selected. However, I changed it to 'Allow only essential services' selected 'Advanced' and can see that it is not selected. Just 'Enable Firewall Logging' is ticked (curiously, when I click 'open log...', nothing happens.

I never have trouble getting out onto the internet from this macbook pro and I can ping my router + internet ok :

p$ ping www.google.com
PING www.l.google.com (173.194.37.104): 56 data bytes
64 bytes from 173.194.37.104: icmp_seq=0 ttl=53 time=27.940 ms

ping 192.160.0.1
PING 192.160.0.1 (192.160.0.1): 56 data bytes
64 bytes from 192.160.0.1: icmp_seq=0 ttl=64 time=3.206 ms

Any other ideas would be much appreciated! Thanks.

Reply

Answer 4

paulito Author

Level 1

0 points

Nov 8, 2010 2:44 AM in response to paulito

One new mystery that transpired yesterday. I tried to connect to my work VPN and it complained that in order to use the VPN, 'Back to my mac' needs to be disabled. So obviously there is some deeper network stuff going on here. So I disabled it and after a reboot was able to connect to the VPN. However, after that I still couldn't ping it on the LAN.

Reply

Answer 5

Nov 8, 2010 6:19 AM in response to paulito

Wow.. some very interesting things may be happening.
Can the Mac ping itself? that would be `$ ping 127.0.0.1`

If that doesn't work, then.. uh.. I really don't know! Usually such problems for me are solved after either a reboot or restart to the network. It's strange that the computer is able to receive connections from outside, but not pings! are other services like Web Sharing (SysPrefs > Sharing > "Web Sharing" check box) accessible over LAN?

I hope the answer lies somewhere here!

Sorry I couldn't solve it!
--Arunjit

Message was edited by: arunjitsingh. (Square) brackets make links.. did not know that.

Reply

Answer 6

paulito Author

Level 1

0 points

Nov 8, 2010 3:14 PM in response to arunjitsingh

yes, can ping 127.0.0.1 no problem. No sharing enabled.

Will post if I ever get a solution!

Thanks!

Reply