General discussion

Locked

network collision

By den_espe ·
i have a small network of 8 terminals all connected to the internet using winproxy. when i added a new terminal and plugged in one port of the hub, a continous blinking indicating a collision occurs, why? the terminal is assigned a unique IP and theTCP/IP configuration is exactly same with the rest

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

network collision

by rich In reply to network collision

I really wish they didn't call them "collisions". If I'm hearing you right, it's nothing serious -- a collision is something perfectly natural and within normal operation of an ethernet network.

A collision occurs when two ethernet signals are sent at the same time. The devices then pick a random interval to resend the packet. That's how ethernet works across a hub. Nothing scary, it's just part of its operation. If you get LOTS of collisions, then you eventually get performance degradation. Consider buying a switch if that's the case.

Hope that helped. =)

Cheers,
Rich

Collapse -

network collision

by den_espe In reply to network collision

"Collision" coz of the continous blinking in the port wher i pluged it and "COL" is permanent red, but the NIC of the "defective" pc does not indicate a connection (no light) on the other end, but I found out that this "collision" occurs only in that specific terminal coz when i tried connecting another terminal no "collision" occured (i mean no continous blinking in the port wher i plugged it & "COL" is not permanent red). But again, this "defective" terminal works when i conected directly to the switch & obtained a dedicated internet connection bypassing the winproxy network. (btw, the "winproxy" network uses only 10baset hub & the server is connected to thesame switch) is there something wrong w/ the "defective" pc's NIC card (dual 3com) coz it worked on the switch but not on the 10bt hub?

Collapse -

network collision

by matkinson In reply to network collision

A continuously-on collision light is a bad thing. On your network, where the ninth machine makes the collision light go on continuously (where before you rarely saw the light on), you probably have a jabbering NIC. Jabber is the condition where a NIC won't stop sending signals, even when it's supposed to.

If this machine and its NIC works on your switch but not on your hub, you may have a polarity problem or some other issue that the switch is smart enough to correct for, but that the hub can't. Is this a manageable switch? If so, is it telling you anything about that port?

Collapse -

network collision

by den_espe In reply to network collision

Poster rated this answer

Collapse -

network collision

by den_espe In reply to network collision

This question was closed by the author

Back to Networks Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums