CAT5 Crossover Cables

[Guest_imported]

Hello all. I'm trying to network two PCs in a home and share one DSL line/modem. I have one 50ft Cat5 Crossover cable that'll go to one PC downstairs, a 4 port hub, and a short CAT5 standard cable that I think can go from DSL modem to hub. I know I need one more short cable to go from hub to second PC, but got a bit confused because I know the pinouts are switched with the crossover cable, and it gets tricky with using the right port on the hub (uplink??). It's my first attempt at this, and I wanted to know if I need to get a 2nd crossover or 2nd standard. I know I should've gotten all the same type Cat5 to begin with, but since I already have the long crossover cable, I was wondering if this could be done...thanks a bunch.

 

[GoLdFiNgeR]

one pc, preferably teh dsl host, will plug into the uplink on the hub with the crossover cable, your other pc will use a regular port, (1) using a standard straignt thought cable, non-crossover. but it is way trikier than that, what ive found out is that you will need two nics in your host computer, one for dsl and one for your network, your cable from your router to your dsl comp should be regular, going into nic #1, then you will have a cable from nic #2 go to your hub, if the cable is crossover use the uplink , if not the use port 1, then a regular cable will go from port 2 to your secnd comp, of course all useing the same workgroup, and all that oterh stuff, bt this should get you started

 

[Daveyboy2]

Normally with a hub you don't need to go with a crossover. Any with a DSL at home, you really want a router with a built in hub.

BUT, you shouldn't need a crossover from a normal hub port to a PC. They are straight pin outs from hub to PC. It's a straight thru on most modems to the hub if memory recalls - the only time you need a crossover is if you are hooking 2 computers together via crossover and NO hub. -= Beer is food! Is it suppertime? =-
If ya like the info on the posts - rate them helpful!

 

[GoLdFiNgeR]

yeah you dont need a crossover, but you can use one if you plug it into uplink, and he already has one so it would save him the money from buying a regular cable, so yes he doesnt need one, but he has one so well use it

 

[ceh4702]

I had a cable modem for a while and they restricted to me to one IP number. Since you have to put the IP # into the network section in the control panel, you can not use two computers on the same IP # on a network without causing a conflict on the cable Wide Area Network. This is why many people buy a DSL/Cable Router so they can hide the number of computers they have connected to the IP number.

You need to know what the policy of your Cable supplier is on this. This can get into a grey legal area. If you do not like my post feel free to point out your opinion or my errors.

 

[GoLdFiNgeR]

he will have two ips, one on nic#1 for his dsl, and one on nic#2 for his lan, i dont think this is legal, and you should check, but ive done it before, legally, and it should work the same, illegally, becaue only one comp is connected with the dsl modem. but do be careful

 

[Guest_imported]

I knew I didn't need the crossover to begin with, and it does seem like it'll make things more complicated, but I'll live and learn since I have it and might as well figure it out. Will performance suffer at all, or is it just more of a headache to set up? Option 1: Do you think I should scratch the hub altogether then and just add a 2nd nic in the host? This would then mean that I go standard Cat5 from modem to one of the host's nic and then crossover from host's second nic to second PC?

Option 2: the way I have lookin right now, with a hub and a nic for each PC, the host would get the standard cat5 to it and the 2nd pc would get the crossover, if that's possible?

Much appreciated.....

 

[GoLdFiNgeR]

yes, option one would work, and in option two, use the x over on the host going to uplink on the hub, and regular going to port 1 on the hub

 

[Grenage]

So you have 2 computers, one with the DSL modem connected to it and you want to share the connection between the two of them ?

If the above is the case you "could" just put a crossover cable between the 2 machines and bypass the hub. I am assuming you don't want to do this though (I wouldn't). In which case you won't need a crossover cable. Just a normal CAT5 lead from each PC into a normal port on the hub will do you fine.

You shouldnt have a problem with using both computers with conflicting IP's, because if you are using an OS like win98SE or above that has internet sharing and it used NAT. THat translates your seperate computers requests into one IP, and back again.

 

[Psychosylph]

Just my two cents...

I was a newbie to setting up a home network until about two weeks ago. As far as I'm concerned, there are probably two ways to do this that would work best for you.

1. Two NICs in one computer, one in the other. Straight-thru cable from DSL modem to first computer, then crossover from 1st computer to second; setup internet connection sharing and network. Real easy and I got good performance to the second computer - no real noticeable slowdown. I was surprised, but then I always had to have the first on to let the second access the Net...

2. Get a small router. Straight-through from DSL to uplink (WAN), straight-through from port to computer, one for each. This will cost you a little more, but I (and my wife) like it a lot better. My Linksys w/ WinXP was a cinch to set up (15 minutes start to finish).

I don't know if your hub will work. You may have a problem with IP addressing - that is something that you will probably have to take up with your ISP. But either of the other two will not give you any trouble.



I LOVE troubleshooting...

 

[garwain]

If you know a technician with an RJ-45 crip tool, it would take him about 2 minutes to crip on a new connector to switch your crossover to a straight-through cable. (or you could take the cable to a computer shop and have them do it)

total cost should run about 2 minutes, 1 RJ-45 connector and leave you with 2 inches less of cable on the crossover where it gets cut off.

If you are planning on playing around with more cables, a good cut/strip/crimp tool runs about $30US I believe, but it you only want to change 1 connector, then it's probably better to have it done for you.

 

[Guest_imported]

I was leaning towards option 2 on Psychosylph's message, and my immediate concern was whether or not the crossover cable that I already have could be used in some way to get my two Pcs together (with my hub, without adding a 2nd nic in the host), but I guess it's not the best idea. If adding that extra nic means I'll need to keep the host Pc on whenever I want to use the other one for the net, then I'll just get straight-thru cabling for the whole deal. I had just seen somewhere reading that if you plug the crossover into a regular port on the hub instead of the uplink it might work and I would be able to use the combo of 2 straight-thru cables (modem to hub, and hub to host), 1 crossover (hub to 2nd PC), and the whole thing might work.
I'll have to check with the ISP about configuring the second IP address if needed. I'm not sure about that or any of the legal stuff that goes with it. I had told them I was planning on a network when I subscribed so I think it might be okay..

 

[Guest_imported]

Changing the cable to a straight-thru now becomes a pretty good idea, too.....many thanks!

 

[GoLdFiNgeR]

what if you plug the modem cable into the uplink on the hub, then the 2 comps into the ports of 1 and 2 on the hub, that may work also

 

[garwain]

yeah, if you are going with the get 2 IP's approach, then change your long cable to a straight-through and plug the modem cable into the uplink port.

if you want to have either computer able to access the net without requiring the other to be on and want to work with 1 IP then you'll need a router.

I once had a setup with a cable modem plugged into my hub, and 1 IP, so I would just have to do an
ipconfig /release
ipconfig /renew

from the command prompt from the computer I was on at the time. This would cause the computer to get a new address from the server and the other computer would then loose access. Sometimes a reboot would be required though.