Home All Groups Group Topic Archive Search About

New Rule of Thumb

Author
23 Feb 2005 6:16 PM
Smowk
Came to this conclusion last night...a real good rule of thumb:

Belkin is Broken



4 out of 6 belkin hubs installed at the holiday inn i work
for...mysteriously broken...just stop working after a few months...one at a
time just goes out.  Installing a netgear works perfectly.

2 different belkin routers, each at different locations...mysteriously stop
routing.  dhcp works, internal network traffic works...but ping yahoo.com
or msn.com...nothing.  restored factory default settings...nothing. 
upgrade firmware...nothing.  install linksys...everything

so remember guys

BELKIN IS BROKEN



smowk

Author
24 Feb 2005 4:08 AM
Herb Martin
I am not a great fan of Belkin but I have my issues
with NetGear and maybe even more with LinkSys
(I buy mostly NetGear if they make what I want.)

> 4 out of 6 belkin hubs installed at the holiday inn i work
> for...mysteriously broken...just stop working after a few months...one at
a
> time just goes out.  Installing a netgear works perfectly.

Could be, but they might be different types of
hubs or even bad cabling (that got change accidentally
at the same time).


> 2 different belkin routers, each at different locations...mysteriously
stop
> routing.  dhcp works, internal network traffic works...but ping yahoo.com
> or msn.com...nothing.  restored factory default settings...nothing.
> upgrade firmware...nothing.  install linksys...everything

A ping failure without understanding it or even
trying tracert is not sufficiently specific to blame
anything.
Author
24 Feb 2005 1:50 PM
Smowk
"Herb Martin" <n***@LearnQuick.com> wrote in
news:O4saudiGFHA.2620@tk2msftngp13.phx.gbl:

> 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.
Author
24 Feb 2005 4:52 PM
Phillip Windell
Show quote Hide quote
"Smowk" <Smowk***@Yahoo.com> wrote in message
news:Xns960759F09E4BSmowkieBandit@216.196.97.131...
> "Herb Martin" <n***@LearnQuick.com> wrote in
> news:O4saudiGFHA.2620@tk2msftngp13.phx.gbl:
>
> > 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
Author
24 Feb 2005 10:53 PM
Herb Martin
> [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


Show quoteHide quote
"Phillip Windell" <@.> wrote in message
news:#OTzAFpGFHA.1476@TK2MSFTNGP09.phx.gbl...
> "Smowk" <Smowk***@Yahoo.com> wrote in message
> news:Xns960759F09E4BSmowkieBandit@216.196.97.131...
> > "Herb Martin" <n***@LearnQuick.com> wrote in
> > news:O4saudiGFHA.2620@tk2msftngp13.phx.gbl:
> >
> > > 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
>
>
Author
25 Feb 2005 2:26 PM
Phillip Windell
"Herb Martin" <n***@LearnQuick.com> wrote in message
news:Oul7IVsGFHA.400@TK2MSFTNGP14.phx.gbl...
> > [ppssst! still speaking to me, Herb? :-),  it's ok,...be cool]
>
> Of course -- I am even surprised to find the question.

Just wanting to make sure. I've had a "spell" of everyone being ticked at me
for one thing or another lately.

> You should see the crazies I answer in some of the
> 'policitcal' groups. <grin>

You should see the trouble I get in for being "political" in the groups over
what I considered a "playful side-comment".  See the thread "Did
Anti-spyware Vendor Cave In?" over in the "ms.public.security group".

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
Author
25 Feb 2005 4:50 PM
Herb Martin
"Phillip Windell" <@.> wrote in message

> You should see the trouble I get in for being "political" in the groups
over
> what I considered a "playful side-comment".  See the thread "Did
> Anti-spyware Vendor Cave In?" over in the "ms.public.security group".

Naught <grin>

--
Herb Martin


Show quoteHide quote
news:OZkowX0GFHA.4032@TK2MSFTNGP12.phx.gbl...
> "Herb Martin" <n***@LearnQuick.com> wrote in message
> news:Oul7IVsGFHA.400@TK2MSFTNGP14.phx.gbl...
> > > [ppssst! still speaking to me, Herb? :-),  it's ok,...be cool]
> >
> > Of course -- I am even surprised to find the question.
>
> Just wanting to make sure. I've had a "spell" of everyone being ticked at
me
> for one thing or another lately.
>
> > You should see the crazies I answer in some of the
> > 'policitcal' groups. <grin>
>
> You should see the trouble I get in for being "political" in the groups
over
> what I considered a "playful side-comment".  See the thread "Did
> Anti-spyware Vendor Cave In?" over in the "ms.public.security group".
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
Author
24 Feb 2005 11:45 PM
Smowk
"Phillip Windell" <@.> wrote in
news:#OTzAFpGFHA.1476@TK2MSFTNGP09.phx.gbl:


> 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]
>

the cables were the same, the nics were the same, the computers were the
same

belkin broken
linksys working

tried again

belkin broken
linksys working

tried again

belkin broken
linksys working

tried again

belkin broken
linksys working

tried again

belkin broken
linksys working

tried again

belkin broken
linksys working

tried again

belkin broken
linksys working


hmmmm...maybe the belkin does work