1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Home Network Computers Don't Respond to Ping

Discussion in 'Networking (Hardware & Software)' started by dbender, 2009/01/03.

  1. 2009/01/03
    dbender

    dbender Inactive Thread Starter

    Joined:
    2009/01/02
    Messages:
    4
    Likes Received:
    0
    I have 3 computers on my home network. A desktop and laptop running XP Pro, and a laptop running Vista 64. All three have access to the internet through a router and cable modem. All three can ping internet servers via IP address and/or domain names. All three can ping themselves and the router. All three show the other two in their network maps. I can access shared folders and printers on the desktop from both laptops (well, I can't print from the Vista laptop, but that's another story).

    Here's the problem: None of these three computers will respond to a ping request from either of the other two. Not a major problem for me right now, but I don't understand and it bothers me--and may present problems later.

    I have Norton Internet Security running on all three. i created a firewall rule to allow all protocols, inbound and outbound, to/from all computers in the range 192.168.0.1 to 192.168.0.255. Windows firewall is turned off on all three. I know of no other firewalls running.

    What else could cause this behavior?

    Thanks for any ideas.

    Duane
     
  2. 2009/01/03
    Eraser

    Eraser Inactive

    Joined:
    2008/12/20
    Messages:
    104
    Likes Received:
    2
    Hi,
    Some questions:-
    Do you have a star topology ?
    Do you share an internet connection with the help of LAN ?
    Please elaborate on your network structure and firewall settings ?
     

  3. to hide this advert.

  4. 2009/01/03
    rsinfo

    rsinfo SuperGeek Alumni

    Joined:
    2005/12/25
    Messages:
    4,076
    Likes Received:
    178
    Norton Internet Security is itself a firewall. You would have to allow it to respond to an incoming ping request & reply to it. [ICMP echo request]
     
  5. 2009/01/03
    dbender

    dbender Inactive Thread Starter

    Joined:
    2009/01/02
    Messages:
    4
    Likes Received:
    0
    Thanks for the two responses, and here's what I can add:

    Network topology: Cable modem provides WAN connectivity to wireless router/switch. Ethernet cable connects XP desktop PC to router/switch. XP and Vista 64 laptops connect to router via wifi. The only firewall running (AFAIK) is the "Smart Firewall" included in Norton Internet Security. If I turn it off, the Windows Security Center reports lack of running firewall.

    I checked NIS for an ICMP Echo rule and found three:

    - "Default Allow Specific Inbound ICMP ":
    - Direction: Inbound
    - Computer: Any
    - Communications: Specific
    - Protocol: ICMP

    - Default Allow Specific Outbound ICMP (Echo Request)
    - Direction: Outbound
    - Computer: Any
    - Communications: Specific
    - Protocol: ICMP

    - Default Allow Specific Outbound ICMP (Others)
    - Direction: Outbound
    - Computer: Any
    - Communications: Specific
    - Protocol: ICMP

    The first of these rules is unchecked, which I assume means it is defined but inactive; it is also read-only, and I do not know how to change that state so that I could activate it. And the read-only state also prevents me from examining the details (like what does the "specific" mean?).

    The second of these rules in checked, which I assume means it is active; it is also read-only.

    The third rule is checked, and is read/write, so I can change that one. And I can also see the details of the rule, which tells me that the "specific" in this case means ICMP "command 0-7" and "command 9-18 ". I would assume, then, that the second rule allows outbound ICMP command 8. Taken together, these two rules would then allow outbound ICMP commands 0-18. Probably, the first rule would allow inbound ICMP command 0, if I could turn it on. If that's what I need, I could try to find out how to make that rule read/write so I can activate it; or I suppose I could create a new rule that allows inbound ICMP command 0 from computers in the 192.168.0.1 - 192.168.0.255 range.

    I'm already over my head here, so I hope this is enough detail. Thanks again.

    Duane
     
  6. 2009/01/03
    rsinfo

    rsinfo SuperGeek Alumni

    Joined:
    2005/12/25
    Messages:
    4,076
    Likes Received:
    178
    Try logging in as Administrator & then change the settings.
     
  7. 2009/01/04
    dbender

    dbender Inactive Thread Starter

    Joined:
    2009/01/02
    Messages:
    4
    Likes Received:
    0
    Logging in as Administrator did not allow me to modify the read-only firewall rules. But I created a new rule, allowing inbound ICMP command 8 from all computers in the local subnet, and the computers now respond to ping requests. One problem down. Thanks for the responses.

    Duane
     
  8. 2009/01/04
    rsinfo

    rsinfo SuperGeek Alumni

    Joined:
    2005/12/25
    Messages:
    4,076
    Likes Received:
    178
    Good.

    I would also suggest that you search Norton kb for this problem. Almost all the firewalls allow ICMP requests to be turned on.
     
  9. 2009/01/08
    Eraser

    Eraser Inactive

    Joined:
    2008/12/20
    Messages:
    104
    Likes Received:
    2
    Read This !!!

    Hi,
    Thought that could be helpful:-
    http://en.wikipedia.org/wiki/Ping

    it says that the ping packet 0 is for introduction and many recent Firewalls tend to drop the ping 0 & 8 which is ICMP echo return request.
    I suggest you do not create a rule for command 8 to be allowed in your subnet as it can lead to virus/worm attack!!
    :D
     
  10. 2009/01/09
    dbender

    dbender Inactive Thread Starter

    Joined:
    2009/01/02
    Messages:
    4
    Likes Received:
    0
    Really? Accepting these commands from computers on subnet 192.168.0.0, which I assumes means only from my own router and my own computers, exposes me to viruses launched from the other side of the router? I thought that would be safe. I guess I really don't understand this stuff as well as I thought. Thanks for the warning.

    Duane
     
  11. 2009/01/11
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    Most ISPs will block packets to and from 192.168.0.0 addresses, so no packets from these addresses should hit your external port. It wouldn't hurt to add a firewall rule to drop all packets from 192.168.0.0 that come in on the external port. However, whether you can do that, depends on the sophistication of your firewall and anyway, its very unlikely that any will anyway due to ISPs blocking them.

    Therefore, I'd feel reasonably safe setting a firewall rule to allow ping between 192.168.0.0 addresses.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.