| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 58199 | 2005-05-24 10:37:00 | Networking Problem | Lovelee (6586) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 358139 | 2005-05-31 06:42:00 | Umm. The "cable" detection actually detects a "cable with a live device connected to the other end". It's a bit odd that the other computer isn't complaining, but I suppose the detection consists in looking for some volts from the other end's transmitter. So it only needs one of the receive lines to be open (differential signals) for the detection to fail. | Graham L (2) | ||
| 358140 | 2005-05-31 07:00:00 | Yes, I see what you mean. I get the "unplugged" icon whether I unplug it from the back of the PC or from the wall. I was just trying to help after Lovelee's waspish (but probably justified) response to my earlier post. :blush: But would that still apply to a crossover cable? I got the impression from the thread that she was only getting the message at the laptop and not the other PC. |
Tony (4941) | ||
| 358141 | 2005-05-31 07:08:00 | That's right. I suspect that one of the contacts in the laptop's socket is not connecting to the cable. Almost certainly one of the receiver pins. A crossover cable (or a straight one) will cause the "no cable" error if it's used wrongly, because you haven't got a TX pair connected to a RX pair and an RX to a TX. If a receiver can't see a live transmitter nothing will work. Changing the speed and duplex setting might cause a burst of activity on the port. (The laptop can probably send OK, so you'd see that activity, but if it can't recieve it will drop out again.) |
Graham L (2) | ||
| 1 2 3 4 5 6 7 | |||||