(no subject)
Nov. 26th, 2006 08:46 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
torkellMemo to self: when testing infrastructure CAT5, it is vitally important that the cable you use is *not* a crossover.
On a related note, the two sockets I put in today have labels stuck on them containg "CROSSOVER LINK" and a couple of exclamation marks.
On a related note, the two sockets I put in today have labels stuck on them containg "CROSSOVER LINK" and a couple of exclamation marks.
no subject
Date: 2006-11-26 09:35 pm (UTC)I've done that a few times, purely on accident.
At one point, I made a habit of coloring the jacket at the ends of my crossover patches black with a shaprie, so I could tell at a glance if it was a crossover or not.
Since I built my crossover hub and cover stub, though, I don't do that.
no subject
Date: 2006-11-26 10:37 pm (UTC)no subject
Date: 2006-11-26 10:37 pm (UTC)The layout is this: drop from 8-port auto-sensing switch in server cupboard to socket in my room. Plain cable to my switch (specifically, the crossed port on my switch). Cable from there to socket in next-door room, with a computer on the end of that.
Both runs are crossed, thanks to I think pinouts.ru being wrong (or me misreading their site - the sockets are wired to 'A').
Hook mine up - it works, as the switch upstairs is auto-sensing. Hook housemante's up, and it no work. Ponder for a while, confused as to what is up because both runs tested fine.
Get the smart idea of jotting down just what's crossed according to the tester with a different cable, and realise I've swapped a pair. Other housemate asks if the first test cable was a crossover, at which point the traditional ightbulb appears and I plug first housemate's link into the crossed port on the switch.
Laugh at my amusing failure.