I recently added a switch to my home network due to some new hardware needing internet access. When I did this I had to make a new CAT5e cable for the port that my opensuse PC is connected to. Ever since doing this it will not detect the internet connection. At first I just thought I had incorrectly spliced the CAT5e but I replaced the ends and the switch lights up on the port the PC is hooked up to so it sees the PC but the PC still says that it is not connected. Is there a way to force it to recheck for the network connection?
On Sun January 24 2010 08:06 pm, elduderino9 wrote:
>
> I recently added a switch to my home network due to some new hardware
> needing internet access. When I did this I had to make a new CAT5e cable
> for the port that my opensuse PC is connected to. Ever since doing this
> it will not detect the internet connection. At first I just thought I
> had incorrectly spliced the CAT5e but I replaced the ends and the switch
> lights up on the port the PC is hooked up to so it sees the PC but the
> PC still says that it is not connected. Is there a way to force it to
> recheck for the network connection?
>
>
elduderino;
Restarting the network is all that should be needed. The most likely problem
is with the patch cable but it is also possible to have a faulty switch or
damage connector on the PC. Check the cable for proper wire order and
connectivity. Both ends should conform to either T568B or T568A standard.
For T568B the connection is:
pin wire
1 W/O
2 O
3 W/G
4 Bl
5 W/Bl
6 G
7 W/Br
8 Br
W= white, O = orange, G = green, Bl = blue, Br = brown
T568A is the same except O and G are interchanged.
It is easy for one wire to slip back when you crimp the ends resulting in a
wire which is not connected to its pin. Sometimes a simple visual inspection
will reveal this. Of course a broken wire in mid cable can not be checked
visually. If you do not have a cable tester, a simple ohm meter can be used
(with some care) to check that you have connectivity between pins and no
leakage to other pins.
Of course you can replace the suspect cable with a known good cable just for
testing. The lights on the switch turning on does not mean the cable is
good.
Lots of luck.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
On Sun January 24 2010 08:58 pm, PV wrote:
> On Sun January 24 2010 08:06 pm, elduderino9 wrote:
>
>>
>> I recently added a switch to my home network due to some new hardware
>> needing internet access. When I did this I had to make a new CAT5e cable
<snip
>
> Of course you can replace the suspect cable with a known good cable just for
> testing. The lights on the switch turning on does not mean the cable is
> good.
>
> Lots of luck.
>
elduderino9;
A couple of other thoughts:
I assume you did not replace the network card/device on your PC. If you did
replace this it will need to be reconfigured with YaST.
Have you checked that no two devices on your network have the same IP. If all
the devices are configured with dhcp this should not be a problem. However
if some have static IP’s they could be conflicting.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
It is easy for one wire to slip back when you crimp the ends resulting in a
wire which is not connected to its pin. Sometimes a simple visual inspection
will reveal this. Of course a broken wire in mid cable can not be checked
visually. If you do not have a cable tester, a simple ohm meter can be used
(with some care) to check that you have connectivity between pins and no
leakage to other pins.
Thank you for the replies. As it turns out this is all it was. I don’t know why I didn’t notice it when I first crimped the cable but one of the ends was in the wrong port. I just cut the end off and recrimped it and it worked fine.
On Wed January 27 2010 09:36 am, elduderino9 wrote:
>
>> It is easy for one wire to slip back when you crimp the ends resulting
>> in a
>> wire which is not connected to its pin. Sometimes a simple visual
>> inspection
>> will reveal this. Of course a broken wire in mid cable can not be
>> checked
>> visually. If you do not have a cable tester, a simple ohm meter can be
>> used
>> (with some care) to check that you have connectivity between pins and
>> no
>> leakage to other pins.
>
> Thank you for the replies. As it turns out this is all it was. I don’t
> know why I didn’t notice it when I first crimped the cable but one of
> the ends was in the wrong port. I just cut the end off and recrimped it
> and it worked fine.
>
>
elduderino9
I suspect everyone who makes their own cables has been there, done that. It’s
not uncommon for even retail cables to be bad. Glad you have it working.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green