up vote 0 down vote favorite
share [g+] share [fb]

I have two systems in my office LAN. One is running Fedora and the other windows 7. I can ping the windows machine from the Fedora machine but I am unable to ping the Fedora machine from windows machine. Whenever I ping the Fedora machine it gives a "Request timed out" I tried disabling the firewall on Fedora machine but it did't help. Please suggest what could be the problem here.

link|improve this question
Can the Fedora machine ping itself? – cwallenpoole Oct 7 '11 at 18:05
... on its external interface? – Kusalananda Oct 7 '11 at 18:09
Is the Fedora dropping ping requests? (iptables enabled?) – ott-- Oct 7 '11 at 18:12
I am not able to ping Fedora machine with or without iptables enabled. – vjain27 Oct 7 '11 at 18:27
Do cat /proc/sys/net/ipv4/icmp_echo_ignore_all - does it show 1? Then do echo "0" >/proc/sys/net/ipv4/icmp_echo_ignore_all and try ping again. – ott-- Oct 7 '11 at 19:25
show 2 more comments
feedback

migrated from stackoverflow.com Oct 8 '11 at 7:30

This question came from our site for professional and enthusiast programmers.

1 Answer

up vote 0 down vote

Ping replies are simply handled by an interrupt call in the Windows TCP/IP stack, therefore interaction with your server is quite limited. To send out the ping from Windows, though, it needs to know how to route the packet. Is your routing set up correctly? Can you see the network from your Windows box? Have you got the right IP address for your Fedora box?

(I edited this to get the Windows/Fedora thing the right way round, but the basic point remains the same - as has also been said, replying to a ping and sending a ping out are not the same)

link|improve this answer
There is no problem with the windows box because I can ping my windows box from my Fedora box. It is not working the other way round. – vjain27 Oct 7 '11 at 21:23
The process of pinging and replying to a ping are different, hence the question about routing. My guess would be routing also. A ping reply just pushes the reply back out the same interface it came in on. So my guess is the Windows box routing is wrong. – Paul Oct 9 '11 at 11:55
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.