Home Networking - Switch or Cable issue?

[Dokusaru]

Hey people - been browsing AnandTech for years but this is my first post.

I recently moved and have had problems setting up my home network. I've got a Comcast cable internet connection (+ I blow some extra money on the 'ultra' speed). That connects to a wireless linksys router which had wired connections to 360, PS3 and so on.

I'm running a 100ft ethernet cable upstairs to my office and I want to plug that into a switch so I can have a couple of wired connections upstairs. When I plug the cable directly into my computer I've got a great connection speed. When I plug it into the switch I get no connection at all. If I take the switch downstairs and plug it into the router with a smaller (say 25ft) cable it blinks on no problem.

Anyone else experienced this? Is the cable or switch likely at fault? The switch's manual says it should work upwards of 100 meters (328 feet).

If it is the switch please suggest a replacement. Don't remember the model # but I'm working with newly purchased Cisco with 8 ports. Thanks!

 

[Harvey]

What's the make and model of your switch, and is it a switch or a router?

Did it come with an installation disk/program, or is there one available on the manufacturer's site?

Search Google for user problems with the make and model. There may be a conflict between the Comcast's default IP address and the default used by the switch. If so, you may have to override the default manually.

Contact Comcast's tech support. They may have experienced similar problems with other customers who own the same make/model as your switch.

Good luck.

 

[seepy83]

I'm guessing that your 100 ft cable is a patch cable with stranded copper. If it is, then 100 ft is too long and the cable is your problem. Check out the sticky on Proper network cable installation. You need the majority of your run to be solid-core cable that is punched down to a keystone jack on each end, and then use short (15 ft or less) store-bought patch cables to connect from the keystone to the device.

 

[VirtualLarry]

Considered doing powerline networking, or using a wireless repeater (DD-wrt router)?

 

[imagoon]

I'm guessing that your 100 ft cable is a patch cable with stranded copper. If it is, then 100 ft is too long and the cable is your problem. Check out the sticky on Proper network cable installation. You need the majority of your run to be solid-core cable that is punched down to a keystone jack on each end, and then use short (15 ft or less) store-bought patch cables to connect from the keystone to the device.

Pretty much this. You are out of spec. Some devices can do it, others as you see will simply give up or throw a ton of errors.

 

[Dokusaru]

Thanks for the advice everyone.

Would running 100ft of solid-core to the switch do it or am I going to need go use a keystone?

I'll check out that sticky now as well.

 

[imagoon]

Thanks for the advice everyone.

Would running 100ft of solid-core to the switch do it or am I going to need go use a keystone?

I'll check out that sticky now as well.

Proper is keystones on the solid core cable, short patch cords from the keystone to the devices.

 

[Harvey]

Solid core wire isn't as flexible as stranded, which could be a problem if you need the flexibility to move the switch around, for example, for dusting or getting to other components. The keystone or punchblock is a convenient way to interface between the longer solid core wire run and the shorter cables that actually connect to your gear on either end.

 

[spidey07]

Don't forget you may need a crossover cable. Switch to switch or router to switch require a crossover cable or for the device to support auto-MDI which automatically switches the transmit and receive pairs.

 

[AstroGuardian]

Don't forget you may need a crossover cable. Switch to switch or router to switch require a crossover cable or for the device to support auto-MDI which automatically switches the transmit and receive pairs.

Never heard that one before. Never done it and it worked 100% for hundreds of times.

 

[imagoon]

Never heard that one before. Never done it and it worked 100% for hundreds of times.

Welcome to networking, you must be pretty young in it

 

[AstroGuardian]

Welcome to networking, you must be pretty young in it

Actually i am more than 10 years into networking. And still this is the first time i hear bout it.
I know that older NICs require crossover cable for NIC-to-NIC operation

 

[spidey07]

Actually i am more than 10 years into networking. And still this is the first time i hear bout it.
I know that older NICs require crossover cable for NIC-to-NIC operation

I hope you're kidding. 10 years ago the concept of auto-MDI was completely foreign. It's only been out for around 6 years.

Ethernet devices are either MDI or MDI-X, one is for end points, the other for DCE/equipment. When like ports are connected you MUST use a crossover cable or one device MUST support auto-MDI.

 

[imagoon]

Spidey, there was "auto-mdi" more than 10 years ago, it was just not called that. The name escapes me at the moment but I have a few really old HP Procurves 100Mb that I bought on ebay (for $1 lol) 7 years ago that do it.

 

[spidey07]

Eitherway, no link means no link and most likely a crossover cable is needed.