|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
#1 |
|
Member (6 bit)
Join Date: Feb 2000
Location: On D Globe
Posts: 34
|
Greetings!!!
I have set up our LAN using 6 CPU.(all in 1 room) I use cable with the RJ45 connector all is well but the 7th one which is about 70 feet away from the rest cannot connect to the 6 CPU. Have checked the manual & it says that 300 feet will do.I am using "Intel 8 port hub plus" Please help thanks |
|
|
|
|
|
#2 |
|
Member (12 bit)
|
Is the workgroup named the same on this 7th computer? Does this 7th computer have it's own name, different from all the other computers' names? Is the NIC's light shining in back of the computer? Are you using a known good length of cable? Have you installed the correct network protocols on the 7th computer?
__________________
To err is human, but to really foul things up requires a computer. tiretool@pcmech.com My URL |
|
|
|
|
|
#3 |
|
Premium Member
Join Date: Jun 1999
Posts: 9,231
|
I couldnt find info on your hub, but are you sure that the port on the hub isnt an uplink? If so you might need to use a crossover patch cable for the PC connecting it .. that is of course if the information Tiretool mentioned is correct.
|
|
|
|
|
|
#4 |
|
Member (6 bit)
Join Date: Feb 2000
Location: On D Globe
Posts: 34
|
Did a thorough check of the rest(6) & copied all the configuration (workgroup, name etc.). NIC lights are also blinking.Try also to change the former cable with a different one, but still it won't work.
Then I moved the 7th nearer, change the cable to a shorter one & it works....Do u think cable is the problem? Its been giving me a headache. How will I use the crossover patch cable? is it a different combination? I use this combination at both ends (Wh Or; Wh Gr; Wh Bl; Wh Br). |
|
|
|
|
|
#5 |
|
Forum Administrator
Staff
Premium Member
Join Date: May 2000
Location: Joplin MO
Posts: 36,460
|
If you are making your own cables, this can be part of the problem - the 100 meter restriction assumes properly assembled and tested/certified cables. Nobody can hand crimp cables as well as a machine. For that one machine, consider a machine-made Cat5e cable - they aren't that expensive.
We don't make cables any more - we buy them premade and for inside wall wiring we subcontract a certified electrician. Since we did this, we have had a LOT less hassles and it saves a lot of time (and eyesight) and time is money. This brings up a story - we have a customer who, to put it frankly, is a cheap SOB. He wanted to network his office (a NT server and 4 workstations). We sent our electrician over to give him a quote - and it included doing the job right. He wanted to put in a patch panel behind the server and hub in addition to outlets by every workstation. The customer asked him "why a patch panel"? The electrician could not give him an answer except that "this is the way we do it". The customer got pissed off and ran the wires himself and spent all weekend messing with it crimping connectors, etc. (we told him that we don't do wiring - use our electrician, find another electrician, or do it himself). He saved some *cash* but in the past 2 years has paid us many times over fixing his wiring deficiencies. He now has premade cables running along the floor everywhere, and unused wall outlets that never worked right anyway (he didn't do it right the first time - oh well.....). Doing your own wiring is not rocket science, but to do it right requires the right tools and equipment and a lot of practice and some training. Last edited by glc; 06-20-2001 at 03:14 PM. |
|
|
|
|
|
#6 |
|
Member (6 bit)
Join Date: Feb 2000
Location: On D Globe
Posts: 34
|
thanks to all & glc i will try first that cable. then hire someone for the job.
|
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|