Solved ICMP LAN issues SOHO

November 5, 2011 at 04:36:57
Specs: Windows 7
Hi, i'll provide some background, and do my best to descripble.

I have a approx 3 machines that connect to a unmanaged switch, the unmanaged then connects to a modem.router, the modem.router also connects to a wifi.router, some more computers connect to the wifi modem either wireless or wired.

I have two networks 192.168.1/24 and 192.168.2/24 the network is fine from an WAN and LAN perspecitive, all nodes have connectivity both locally and with the internet. I can use rpd and smb to cross both networks.
I've noticed that a single computer on the 192.168.1/24 network cannot be pinged - but I can access the machine with rpd, smb, ftp, from workstations on 192.168.1/24 and 192.168.2/24 networks.

this computer cannot be pinged - but everything works (internet, rpd etc)
I have other machines on that same network which are fine, so far i have tried the following:

set to static ip
set to dhcp ip
set to fixed dhcp
reinstalled ipv4
rebooted unmanged switch
rebuilt machine
*checked cabling*
*rebooted machine*

the router connected to the 192.168.1/24 network cannot evening ping the machine, but i can see that it's providing internet services..the machine can ping everything else, both no one can ping him...

this is a same fault as the network is operating, but it has my interest...
any networking guys out their?


See More: ICMP LAN issues SOHO

Report •


✔ Best Answer
November 7, 2011 at 07:59:42
simple tcp/ip service running?
windows firewall configured to allow icmp?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's



#1
November 5, 2011 at 06:33:11
Is IMCP blocked on that machine? Is a worthless Symantec type product running? Does it really matter that it can't be pinged if everything else works?

How do you know when a politician is lying? His mouth is moving.


Report •

#2
November 6, 2011 at 00:46:02
Hi, i recently reinstalled the OS - ICMP is not blocked as i can ping the loop back address successfully.. so the TCP IP stack is working, yes you are correct, its not too important that i can't ping, as i can still connect.

but i am interested to identify the fault.

OK i just captured from packets form wireshark,
I can see when i ping the unable-pingable address, the ICMP packet ask it's default gateway which sends a broadcast for the networkID, the response if the MAC of the next router... after that the process repeats.
It's must be a mis configuration on the router... but what is misconfigured?


Report •

#3
November 6, 2011 at 05:41:02
I don't see how it could be misconfigured for one machine. Compare the wireshark captures with the machines that don't have the problem.

How do you know when a politician is lying? His mouth is moving.


Report •

Related Solutions

#4
November 7, 2011 at 07:59:42
✔ Best Answer
simple tcp/ip service running?
windows firewall configured to allow icmp?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#5
November 8, 2011 at 03:44:19
thanks wanderer,
damn windows firewall, strange as their no existing rules for enable/disabling ICMP
should so used a port scanner.. i wounder want port echo uses?

*Resolved
*Solution:
Disabled firewall, ping worked
Enabled firewall, ping failed
Created custom inbound rule, allow ICMP on all ports
Address in now pingable


Report •


Ask Question