Im trying to have a 2pc network useing cross-over cable both computer useing onBoard lan ports. but on this pc the green light doesnt come on, and im getting the error message "A network cable is unplugged " I know they both work coz i've used them at LANparties. what should I do?
Did you make the cable yourself? Sounds like one of the connectors isn't properly crimped and thus not making a connection
remember 1 -3 2 - 6 3 - 1 4 - 4 5 - 5 6 - 2 7 - 7 8 - 8 Make sure all wires are fully in there before you crimp
I would not recommend using a crossover cable for networking…sure it might work but it is not a standard procedure. Get a 4 port hub for $20 and save yourself a lot of grief.
your right keir can do whatever he wants with his network Crossover will work but a small switch or hub would be better
Keir, despite what that rude dude is telling you…I would not use a crossover cable to establish a network. And here is the reason…In the old days, NICs were just dumb hardware, they did what you told them to do and nothing else. But now they are getting smart and one of the things they are starting to do is check for a connection to a benign resource (hub, switch ect.). As long as they find a resource, everything is honky dory, but in the case of a crossover, there is no benign resource at the other end. It’s an active resource (another NIC)…and it’s doing the same thing, looking for a benign resource to connect to. Now what do you think is going to happen when two active resources, looking for a quiet connection, can’t find any? I’ll tell ya…they crap out! Then they reset and start the whole process over again. Now, the crapping out is really funny because it does not happen immediately and it may only show up as an intermittent problem and you may not even notice it. But since a 4 port hub is so cheap…why take the chance. Info source: Third tier engineering at Compaq I ran into this problem at an install I did at NCC bank.
well im useing cross over and thats it lol its all working fine now no idea what was wrong Anyway thx for trying to help everone
Well, my Cisco academy course says that crossover is perfectly acceptable, so ner Bluebark, if all a repeater (hub) does is repeat whatever it gets, then how will a NIC know if it's connected to one or not? If it was a switch, then i can see what you're trying to say. Hubs are incredibly dumb. Yeah, crossover is crap, but still... Not trying to trip you up or anything, at the moment I just disagree a little with what you're saying.
Well, personally, I don't add exra hardware where it isn't needed as it adds extra scope for faults. If the Crossover cable is wired up correctly and is within the CAT5e standard it will work just fine. As for NIC being more intelligent, that is true. But the Hub/Switch/Router has to be transparent to the NIC therefore a Crossover will make no difference. In fact if you want to be technical about it a Hub/Switch/Router will add a latency to the connection, as it repeats what it receives (although it would be difficult to measure the latency difference as it would be so small). If the problem returns I suggest you check the Cable first, then the actual pins in the sockets on the motherboards. Then try with offboard cards, only after eliminating any possible hardware problems mess with software.
Herbs sits on the fence and says x-overs can be a pain but so can be hubs/switches. Personnaly I would always take a hub/switch over a x-over cable.
First…Kier, I did not tell you that you had to use a hub ect. to create you’re network. I merely said that I would not recommend it. Then proceeded to tell you why I said that because I do not make a habit of stating something for the heck of it…That would make me look like a fool and that is something I’m not….Although I have been known to act like one from time to time. And Second…RTT, I’m sure Cisco does state that a crossover is acceptable…but there is a difference between acceptable and recommended…which is what I stated. As for how a NIC knows if it is connected to a hub ect. I think the Compaq guy said it had to do with how the packets were handled…it was over three years ago and my increasing age is having a severe affect on my memory. I would not have put the effort into explaining myself if I thought the info was bogus…again, it would make me look like a fool. All I know is that I have dealt with this issue first hand and it drove me ballistic. I probably would have slammed the server on the floor if I could have gotten it out of the rack fast enough….and yes…I have anger management issues. It comes with the territory. Fly, agree with you’re assessment that more hardware means more points of possible failure…That’s why I recommended a crossover cable to our client to handle replication because the production and backup servers were in the same rack and replicating across the cable would help to alleviate some of the congestion on their network. But I kept getting calls because DoubleTake kept going down. After about six months of flying back and forth to Cleveland and bring in Microsoft, DoublTake and Compaq plus a sniffer, that is what we found. We threw a switch into the equation and I have slept peacefully ever since. So ends the story of Bluebark and the NICs…sounds like a rock group or something.
Just one of those faults... Hehe, that's why us Network Engineers will always be able to baffle clients, because half of the time we are baffled ourself (except we know, usually from experience, the 200 possible 'fixes' for the required unbaffling). But I didn't say that.
Yea...it can be a real hassle some times. I especially like it when a client calls you up complaining about a problem they can’t seem to fix, you fly out there (all expenses paid of course) and fix their problem in a couple of hours…and as you walk out of the server room people just stare at you.
