Complete hangup of network caused by single device

Complete hangup of network caused by single device
NewsGroups | Search | Tools
User Password
Register Now! Lost Password?
 comp.dcom.lans.ethernet  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Complete hangup of network caused by single device RH 09-08-2006
Posted by RH on September 8, 2006, 5:01 am
If you were  Registered and logged in, you could reply and use other advanced thread options


Hi all,

I'm being troubled by this most peculiar problem. In an embedded
environment, the PC (running XP Embedded) sometimes falls into
a complete hangup (i.e. XP doesn't respond to anything). It is
related to a hangup of the network; the PC hardware involved seems
to do something on its network connection that causes the switch
(brand: SMC, 24 ports) to block all traffic to/from the other
participants
on the network. As soon as I disconnect the cable from the hanging
PC the whole networks OK again.

I wonder, which phenomenon on a single Ethernet connection
could cause that a complete network is locked out?

(the vendor already has had his own internal network locked out
in an attempt to reproduce the issue, so he's sure the problem
exists)

Any clues?

Rob Hulsebos
Philips Netherlands


Pure Networks
Posted by Robert Redelmeier on September 8, 2006, 7:13 am
If you were  Registered and logged in, you could reply and use other advanced thread options


> I wonder, which phenomenon on a single Ethernet connection
> could cause that a complete network is locked out?

From your email addr, I presume you are not a Black Hat.

Any broadcast that occurs too frequently (flooding) will
bring many ethernets to a crawl if not a stand-still.
For many unmanaged switches, any unknown (non replying)
MAC address qualifies as broadcast.

The real problem is why the device [re]transmits too
frequently. Sounds like a buggy timer/timeout. Sometimes,
a loop (redundant path) can cause the same troulbe.

-- Robert


Similar ThreadsPosted
A question froma complete ignaramus re BNC to RJ45 adapters March 11, 2006, 4:09 pm
Ethernet over single UTP April 19, 2005, 1:32 pm
Multiple VLANs on Single NIC January 19, 2006, 8:06 am
Multiple PHYs to a single MAC April 11, 2007, 10:30 am
1000BaseSX and Single Mode Fibre April 8, 2005, 9:15 am
multiple vlans at a single port June 23, 2008, 1:13 am
Ordered 5 single board computer ref. design, all are same MAC addr, what to do? February 14, 2006, 11:24 pm
Diagnosing network slowness: server or network? June 24, 2005, 12:59 pm
Nat Device required March 14, 2006, 5:42 pm
Identifying a storage device in N/W October 22, 2007, 6:09 am

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map