> [ppssst! still speaking to me, Herb? :-), it's ok,...be cool]
Of course -- I am even surprised to find the question.
I drop topics when they get boring or fruitless,
not people.
You should see the crazies I answer in some of the
'policitcal' groups. <grin>
And I always do so without resorting to profanity <grin>
--
Herb Martin
"Phillip Windell" <@.> wrote in message
news:#(E-Mail Removed)...
> "Smowk" <(E-Mail Removed)> wrote in message
> news:Xns960759F09E4BSmowkieBandit@216.196.97.131.. .
> > "Herb Martin" <(E-Mail Removed)> wrote in
> > news:(E-Mail Removed):
> >
> > > Could be, but they might be different types of
> > > hubs or even bad cabling (that got change accidentally
> > > at the same time).
> >
> > nope...I'M the only one who messes with the hubs or cabling, and nothing
> > was changed
> >
> > > A ping failure without understanding it or even
> > > trying tracert is not sufficiently specific to blame
> > > anything.
> >
> > when you cant ping the computer next to you, dhcp or not, usually means
> > belkin is broken.
>
> Generally yes, but that is not a absolute. Personal Firewalls, bad cables,
> bad Nic in the target machine can all stop the ping without it being the
> belkin device.
>
> [ppssst! still speaking to me, Herb? :-), it's ok,...be cool]
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>