Joe,
Funnily enough I had a similar problem myself with a small network only last
week. I had updated the 4 switches from 10Mb to 100Mb and the system had
worked no problem for a week  - until a power cut. Then when all the PC's
booted, 2 of them couldn't see other PC's on the network by PC name. By IP
address was no problem - DOH! Network neighbourhood revealed no other PC's
from the rogue ones - very strange - but I could Ping them!!!. Oh' by the
way, win 2K and XP machines everywhere.

I first thought was that the master Browser on the network hadn't been
discovered by the rogue PC's so left the network a while - still no joy.

Then I turned off all Firewalls and the other PC's could see the rogue ones
again by IP address but not by name and then the rogue PC's could see the
others by name but not by IP address. 

At this stage I was really confused and even on a total reboot the same
thing occurred. I was just set about to set up all the shares using a
mixture of IP address and actual PC Names and I thought that I'd try and
reboot the switches as they had never been reset since the power failure. 

Before that I tried disconnecting/reconnecting the rogue PC's from their
relevant switches and surprise, surprise the activity/connection light on
each one of them stayed stubbornly OFF despite the fact that the PC could
still ping IP addresses on the network.

A reboot of the hubs hosting the rogue PC's and the system immediately burst
into life. I don't know what had happened after the power failure but those
switches certainly hadn't rebooted properly.

Dave Crozier


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Joe Yoder
Sent: 24 July 2008 01:04
To: [email protected]
Subject: RE: [NF] What would cause a machine to stop responding to a ping?

I am the sysadmin. The rest of the machines on the network could ping 
each other.  Just the one machine wouldn't reply even though it could 
ping other machines.

I took a break and thought things through.  I have pretty well convinced 
myself that the switch itself was causing the problem.  I planned to 
substitute a 4 port switch after I came back from my break but by that 
time the problem had resolved itself or at least gone into hiding.  I 
turned the Windows Firewall on the problem machine back on and everything 
still works.  I think I should get another 16 port switch.  Having a 
spare available should be enough to scare the problem into staying 
hidden! - Joe

On Wednesday, July 23, 2008  7:43 PM, Lew wrote:
>
>Date: Wed, 23 Jul 2008 19:43:56 -0400
>From: Lew
>To: [EMAIL PROTECTED]
>cc:
>Subject: RE: [NF] What would cause a machine to stop responding to a ping?
>
>Isn't the ability to process pings established on a network - wide basis?
iow, if your sysadmin turned them
>off, your machine just wouldn't 'hear' them.
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of John Harvey
>Sent: Wednesday, July 23, 2008 4:51 PM
>To: 'ProFox Email List'
>Subject: RE: [NF] What would cause a machine to stop responding to a ping?
>
>I believe they call it a firewall....
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
>Of Joe Yoder
>Sent: Wednesday, July 23, 2008 3:37 PM
>To: [email protected]
>Subject: [NF] What would cause a machine to stop responding to a ping?
>
>I have been working on a machine with a new installation of XP Pro.  This
>afternoon it stopped responding to pings from other machines on the LAN
>connected to the same switch.  It can ping other machines just fine.  It
>seems to access data from the server and browse the Internet without a
>problem.   I tried another cable and different port on the switch - no
>change.  I swapped Ethernet cards - got a different assigned IP address but
>still have the  same problem.  I turned off the Windows firewall - no
>effect.  Ideas anyone?
>
>TIA - Joe
>
>
>--- StripMime Report -- processed MIME parts ---
>multipart/alternative
>  text/plain (text body -- kept)
>  text/html
>---
>
[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to