RE; Mixing straight and crossover cables through a switch

To network techies, I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device. A to B = works if I connect A to the switch and B to the switch A to B through S = Not reachable If I introduce another computer(C) and assign it a similar IP(that of device A) C to B through S = works. Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*). At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real. Help *_______________________________________________________________We must Keep on, We can't stop here *

What mysterious device is A? It may be a device specific issue. On Tue, Mar 29, 2016 at 2:35 PM, joe mwirigi via skunkworks < skunkworks@lists.my.co.ke> wrote:
To network techies,
I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device.
A to B = works
if I connect A to the switch and B to the switch A to B through S = Not reachable
If I introduce another computer(C) and assign it a similar IP(that of device A) C to B through S = works.
Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*).
At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real.
Help
*_______________________________________________________________We must Keep on, We can't stop here *
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
-- Best Regards Jimmy Thuo

The mysterious device A is an Access control Device which can run any IP I throw at it, on my local home network, it works perfectly through the switches and all but when on this mystic network N, I cannot ping it through the switch. *_______________________________________________________________We must Keep on, We can't stop here * On Tue, Mar 29, 2016 at 2:47 PM, Jimmy Thuo <jimmy.thuo@gmail.com> wrote:
What mysterious device is A? It may be a device specific issue.
On Tue, Mar 29, 2016 at 2:35 PM, joe mwirigi via skunkworks < skunkworks@lists.my.co.ke> wrote:
To network techies,
I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device.
A to B = works
if I connect A to the switch and B to the switch A to B through S = Not reachable
If I introduce another computer(C) and assign it a similar IP(that of device A) C to B through S = works.
Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*).
At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real.
Help
*_______________________________________________________________We must Keep on, We can't stop here *
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
-- Best Regards Jimmy Thuo

For a switch/hub or other network device you generally use a straight (non-crossover cable) - for direct device to device connection you will (in most) cases need a crossover-cable. 1. Some (not all) switches have "auto-sensing" ports that apply crossover or not depending on the cable you use - check the actual specifications of your switch. 2. Common issue is that individual ports in a switch might be "fried", hence maybe the port you have connected A into may be dead - try another port. .. Mike On 3/29/16 2:35 PM, joe mwirigi via skunkworks wrote:
To network techies,
I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device.
A to B = works
if I connect A to the switch and B to the switch A to B through S = Not reachable
If I introduce another computer(C) and assign it a similar IP(that of device A) C to B through S = works.
Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*).
At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real.
Help /_______________________________________________________________ We must Keep on, We can't stop here /
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke

Thanks Michael, Let me do just that, will report back. Rgds *_______________________________________________________________We must Keep on, We can't stop here * On Tue, Mar 29, 2016 at 2:54 PM, Michael Pedersen via skunkworks < skunkworks@lists.my.co.ke> wrote:
For a switch/hub or other network device you generally use a straight (non-crossover cable) - for direct device to device connection you will (in most) cases need a crossover-cable.
1. Some (not all) switches have "auto-sensing" ports that apply crossover or not depending on the cable you use - check the actual specifications of your switch. 2. Common issue is that individual ports in a switch might be "fried", hence maybe the port you have connected A into may be dead - try another port.
.. Mike
On 3/29/16 2:35 PM, joe mwirigi via skunkworks wrote:
To network techies,
I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device.
A to B = works
if I connect A to the switch and B to the switch A to B through S = Not reachable
If I introduce another computer(C) and assign it a similar IP(that of device A) C to B through S = works.
Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*).
At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real.
Help
*_______________________________________________________________ We must Keep on, We can't stop here *
_______________________________________________ skunkworks mailing listskunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribehttp://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Ruleshttp://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke

Tried switching the ports, Pinging A still results to *unreachable with 0%loss*. i.e. all sent packets are received but still no reply from the device. Connecting B to C (2 computers on the same ports) seems ok and replies. Rgds *_______________________________________________________________We must Keep on, We can't stop here * On Tue, Mar 29, 2016 at 2:57 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
Thanks Michael, Let me do just that, will report back.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:54 PM, Michael Pedersen via skunkworks < skunkworks@lists.my.co.ke> wrote:
For a switch/hub or other network device you generally use a straight (non-crossover cable) - for direct device to device connection you will (in most) cases need a crossover-cable.
1. Some (not all) switches have "auto-sensing" ports that apply crossover or not depending on the cable you use - check the actual specifications of your switch. 2. Common issue is that individual ports in a switch might be "fried", hence maybe the port you have connected A into may be dead - try another port.
.. Mike
On 3/29/16 2:35 PM, joe mwirigi via skunkworks wrote:
To network techies,
I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device.
A to B = works
if I connect A to the switch and B to the switch A to B through S = Not reachable
If I introduce another computer(C) and assign it a similar IP(that of device A) C to B through S = works.
Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*).
At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real.
Help
*_______________________________________________________________ We must Keep on, We can't stop here *
_______________________________________________ skunkworks mailing listskunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribehttp://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Ruleshttp://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke

Have you tried with a different cable? sometimes the cable termination pin points might not have full contact on some devices whereas on others they are ok. On Tue, Mar 29, 2016 at 3:03 PM, joe mwirigi via skunkworks < skunkworks@lists.my.co.ke> wrote:
Tried switching the ports,
Pinging A still results to *unreachable with 0%loss*. i.e. all sent packets are received but still no reply from the device. Connecting B to C (2 computers on the same ports) seems ok and replies.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:57 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
Thanks Michael, Let me do just that, will report back.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:54 PM, Michael Pedersen via skunkworks < skunkworks@lists.my.co.ke> wrote:
For a switch/hub or other network device you generally use a straight (non-crossover cable) - for direct device to device connection you will (in most) cases need a crossover-cable.
1. Some (not all) switches have "auto-sensing" ports that apply crossover or not depending on the cable you use - check the actual specifications of your switch. 2. Common issue is that individual ports in a switch might be "fried", hence maybe the port you have connected A into may be dead - try another port.
.. Mike
On 3/29/16 2:35 PM, joe mwirigi via skunkworks wrote:
To network techies,
I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device.
A to B = works
if I connect A to the switch and B to the switch A to B through S = Not reachable
If I introduce another computer(C) and assign it a similar IP(that of device A) C to B through S = works.
Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*).
At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real.
Help
*_______________________________________________________________ We must Keep on, We can't stop here *
_______________________________________________ skunkworks mailing listskunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribehttp://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Ruleshttp://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
-- Best Regards Jimmy Thuo

@Jimmy, We are preparing several straight cables to test this. Will reply after several tests. Thanks for your time. Rgds *_______________________________________________________________We must Keep on, We can't stop here * On Tue, Mar 29, 2016 at 3:12 PM, Jimmy Thuo <jimmy.thuo@gmail.com> wrote:
Have you tried with a different cable? sometimes the cable termination pin points might not have full contact on some devices whereas on others they are ok.
On Tue, Mar 29, 2016 at 3:03 PM, joe mwirigi via skunkworks < skunkworks@lists.my.co.ke> wrote:
Tried switching the ports,
Pinging A still results to *unreachable with 0%loss*. i.e. all sent packets are received but still no reply from the device. Connecting B to C (2 computers on the same ports) seems ok and replies.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:57 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
Thanks Michael, Let me do just that, will report back.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:54 PM, Michael Pedersen via skunkworks < skunkworks@lists.my.co.ke> wrote:
For a switch/hub or other network device you generally use a straight (non-crossover cable) - for direct device to device connection you will (in most) cases need a crossover-cable.
1. Some (not all) switches have "auto-sensing" ports that apply crossover or not depending on the cable you use - check the actual specifications of your switch. 2. Common issue is that individual ports in a switch might be "fried", hence maybe the port you have connected A into may be dead - try another port.
.. Mike
On 3/29/16 2:35 PM, joe mwirigi via skunkworks wrote:
To network techies,
I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device.
A to B = works
if I connect A to the switch and B to the switch A to B through S = Not reachable
If I introduce another computer(C) and assign it a similar IP(that of device A) C to B through S = works.
Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*).
At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real.
Help
*_______________________________________________________________ We must Keep on, We can't stop here *
_______________________________________________ skunkworks mailing listskunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribehttp://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Ruleshttp://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
-- Best Regards Jimmy Thuo

Thanks @Michael And @Jimmy, turns out it was the crimping pins :) Used different ones. As Jimmy had suggested, the pins were not making good contact with the device socket. Very grateful! *_______________________________________________________________We must Keep on, We can't stop here * On Tue, Mar 29, 2016 at 3:18 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
@Jimmy, We are preparing several straight cables to test this. Will reply after several tests.
Thanks for your time.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:12 PM, Jimmy Thuo <jimmy.thuo@gmail.com> wrote:
Have you tried with a different cable? sometimes the cable termination pin points might not have full contact on some devices whereas on others they are ok.
On Tue, Mar 29, 2016 at 3:03 PM, joe mwirigi via skunkworks < skunkworks@lists.my.co.ke> wrote:
Tried switching the ports,
Pinging A still results to *unreachable with 0%loss*. i.e. all sent packets are received but still no reply from the device. Connecting B to C (2 computers on the same ports) seems ok and replies.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:57 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
Thanks Michael, Let me do just that, will report back.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:54 PM, Michael Pedersen via skunkworks < skunkworks@lists.my.co.ke> wrote:
For a switch/hub or other network device you generally use a straight (non-crossover cable) - for direct device to device connection you will (in most) cases need a crossover-cable.
1. Some (not all) switches have "auto-sensing" ports that apply crossover or not depending on the cable you use - check the actual specifications of your switch. 2. Common issue is that individual ports in a switch might be "fried", hence maybe the port you have connected A into may be dead - try another port.
.. Mike
On 3/29/16 2:35 PM, joe mwirigi via skunkworks wrote:
To network techies,
I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device.
A to B = works
if I connect A to the switch and B to the switch A to B through S = Not reachable
If I introduce another computer(C) and assign it a similar IP(that of device A) C to B through S = works.
Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*).
At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real.
Help
*_______________________________________________________________ We must Keep on, We can't stop here *
_______________________________________________ skunkworks mailing listskunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribehttp://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Ruleshttp://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
-- Best Regards Jimmy Thuo

Surely!!! From: joe mwirigi via skunkworks [mailto:skunkworks@lists.my.co.ke] Sent: Tuesday, March 29, 2016 3:36 PM To: Jimmy Thuo Cc: Skunkworks Mailing List Subject: Re: [Skunkworks] RE; Mixing straight and crossover cables through a switch Thanks @Michael And @Jimmy, turns out it was the crimping pins :) Used different ones. As Jimmy had suggested, the pins were not making good contact with the device socket. Very grateful! _______________________________________________________________ We must Keep on, We can't stop here On Tue, Mar 29, 2016 at 3:18 PM, joe mwirigi <joemwirigi@gmail.com> wrote: @Jimmy, We are preparing several straight cables to test this. Will reply after several tests. Thanks for your time. Rgds _______________________________________________________________ We must Keep on, We can't stop here On Tue, Mar 29, 2016 at 3:12 PM, Jimmy Thuo <jimmy.thuo@gmail.com> wrote: Have you tried with a different cable? sometimes the cable termination pin points might not have full contact on some devices whereas on others they are ok. On Tue, Mar 29, 2016 at 3:03 PM, joe mwirigi via skunkworks <skunkworks@lists.my.co.ke> wrote: Tried switching the ports, Pinging A still results to unreachable with 0%loss. i.e. all sent packets are received but still no reply from the device. Connecting B to C (2 computers on the same ports) seems ok and replies. Rgds _______________________________________________________________ We must Keep on, We can't stop here On Tue, Mar 29, 2016 at 2:57 PM, joe mwirigi <joemwirigi@gmail.com> wrote: Thanks Michael, Let me do just that, will report back. Rgds _______________________________________________________________ We must Keep on, We can't stop here On Tue, Mar 29, 2016 at 2:54 PM, Michael Pedersen via skunkworks <skunkworks@lists.my.co.ke> wrote: For a switch/hub or other network device you generally use a straight (non-crossover cable) - for direct device to device connection you will (in most) cases need a crossover-cable. 1. Some (not all) switches have "auto-sensing" ports that apply crossover or not depending on the cable you use - check the actual specifications of your switch. 2. Common issue is that individual ports in a switch might be "fried", hence maybe the port you have connected A into may be dead - try another port. .. Mike On 3/29/16 2:35 PM, joe mwirigi via skunkworks wrote: To network techies, I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device. A to B = works if I connect A to the switch and B to the switch A to B through S = Not reachable If I introduce another computer(C) and assign it a similar IP(that of device A) C to B through S = works. Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*). At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real. Help _______________________________________________________________ We must Keep on, We can't stop here _______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24 <http://my.co.ke/phpbb/viewtopic.php?f=24&t=94> &t=94 ------------ Other services @ http://my.co.ke _______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24 <http://my.co.ke/phpbb/viewtopic.php?f=24&t=94> &t=94 ------------ Other services @ http://my.co.ke _______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24 <http://my.co.ke/phpbb/viewtopic.php?f=24&t=94> &t=94 ------------ Other services @ http://my.co.ke -- Best Regards Jimmy Thuo

@Tony yes! 5/- . Apparently. You spend 1 week prototyping a device and 2 weeks getting a pin to work! :( *_______________________________________________________________We must Keep on, We can't stop here * On Tue, Mar 29, 2016 at 3:41 PM, Tony Gacheru <tonygacheru@gmail.com> wrote:
Surely!!!
*From:* joe mwirigi via skunkworks [mailto:skunkworks@lists.my.co.ke] *Sent:* Tuesday, March 29, 2016 3:36 PM *To:* Jimmy Thuo *Cc:* Skunkworks Mailing List *Subject:* Re: [Skunkworks] RE; Mixing straight and crossover cables through a switch
Thanks @Michael And @Jimmy, turns out it was the crimping pins :) Used different ones. As Jimmy had suggested, the pins were not making good contact with the device socket.
Very grateful!
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:18 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
@Jimmy,
We are preparing several straight cables to test this. Will reply after several tests.
Thanks for your time.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:12 PM, Jimmy Thuo <jimmy.thuo@gmail.com> wrote:
Have you tried with a different cable? sometimes the cable termination pin points might not have full contact on some devices whereas on others they are ok.
On Tue, Mar 29, 2016 at 3:03 PM, joe mwirigi via skunkworks < skunkworks@lists.my.co.ke> wrote:
Tried switching the ports,
Pinging A still results to *unreachable with 0%loss*. i.e. all sent packets are received but still no reply from the device. Connecting B to C (2 computers on the same ports) seems ok and replies.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:57 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
Thanks Michael,
Let me do just that, will report back.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:54 PM, Michael Pedersen via skunkworks < skunkworks@lists.my.co.ke> wrote:
For a switch/hub or other network device you generally use a straight (non-crossover cable) - for direct device to device connection you will (in most) cases need a crossover-cable.
1. Some (not all) switches have "auto-sensing" ports that apply crossover or not depending on the cable you use - check the actual specifications of your switch. 2. Common issue is that individual ports in a switch might be "fried", hence maybe the port you have connected A into may be dead - try another port.
.. Mike
On 3/29/16 2:35 PM, joe mwirigi via skunkworks wrote:
To network techies,
I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device.
A to B = works
if I connect A to the switch and B to the switch
A to B through S = Not reachable
If I introduce another computer(C) and assign it a similar IP(that of device A)
C to B through S = works.
Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*).
At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real.
Help
*_______________________________________________________________We must Keep on, We can't stop here *
_______________________________________________
skunkworks mailing list
skunkworks@lists.my.co.ke
------------
List info, subscribe/unsubscribe
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
------------
Skunkworks Rules
http://my.co.ke/phpbb/viewtopic.php?f=24&t=94
------------
Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
--
Best Regards Jimmy Thuo

Hahaha it happens to the best of us. Good thing is once it happens to you, you will be wiser the next time. On Tue, Mar 29, 2016 at 3:47 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
@Tony yes! 5/- . Apparently. You spend 1 week prototyping a device and 2 weeks getting a pin to work!
:(
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:41 PM, Tony Gacheru <tonygacheru@gmail.com> wrote:
Surely!!!
*From:* joe mwirigi via skunkworks [mailto:skunkworks@lists.my.co.ke] *Sent:* Tuesday, March 29, 2016 3:36 PM *To:* Jimmy Thuo *Cc:* Skunkworks Mailing List *Subject:* Re: [Skunkworks] RE; Mixing straight and crossover cables through a switch
Thanks @Michael And @Jimmy, turns out it was the crimping pins :) Used different ones. As Jimmy had suggested, the pins were not making good contact with the device socket.
Very grateful!
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:18 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
@Jimmy,
We are preparing several straight cables to test this. Will reply after several tests.
Thanks for your time.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:12 PM, Jimmy Thuo <jimmy.thuo@gmail.com> wrote:
Have you tried with a different cable? sometimes the cable termination pin points might not have full contact on some devices whereas on others they are ok.
On Tue, Mar 29, 2016 at 3:03 PM, joe mwirigi via skunkworks < skunkworks@lists.my.co.ke> wrote:
Tried switching the ports,
Pinging A still results to *unreachable with 0%loss*. i.e. all sent packets are received but still no reply from the device. Connecting B to C (2 computers on the same ports) seems ok and replies.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:57 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
Thanks Michael,
Let me do just that, will report back.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:54 PM, Michael Pedersen via skunkworks < skunkworks@lists.my.co.ke> wrote:
For a switch/hub or other network device you generally use a straight (non-crossover cable) - for direct device to device connection you will (in most) cases need a crossover-cable.
1. Some (not all) switches have "auto-sensing" ports that apply crossover or not depending on the cable you use - check the actual specifications of your switch. 2. Common issue is that individual ports in a switch might be "fried", hence maybe the port you have connected A into may be dead - try another port.
.. Mike
On 3/29/16 2:35 PM, joe mwirigi via skunkworks wrote:
To network techies,
I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device.
A to B = works
if I connect A to the switch and B to the switch
A to B through S = Not reachable
If I introduce another computer(C) and assign it a similar IP(that of device A)
C to B through S = works.
Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*).
At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real.
Help
*_______________________________________________________________We must Keep on, We can't stop here *
_______________________________________________
skunkworks mailing list
skunkworks@lists.my.co.ke
------------
List info, subscribe/unsubscribe
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
------------
Skunkworks Rules
http://my.co.ke/phpbb/viewtopic.php?f=24&t=94
------------
Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
--
Best Regards Jimmy Thuo
-- Best Regards Jimmy Thuo

Worth noting... The cheap RJ45 plugs are intended for crimping on flexible cables which have multiple (usually 7) strands. If you crimp such a plug on solid conductor cable - like oddments of ordinary cat5 cable, then you have one of several possibilities: (a) the pin hits the wire straight on top, and sits too high, or (b) it slides down to the left or right of the conductor, and is twisted, or (c) it cuts the conductor. With 8 pins in the plug, random chances are that you will get all three variants! To my knowledge, only Siemon make 'universal' RJ45 plugs, which may be crimped on either solid or flexible cable. So the solution is either use multi-stranded flexible cable (best) or use Siemon plugs on solid conductor cable. Cheers, Tony On 29/03/2016, Jimmy Thuo via skunkworks <skunkworks@lists.my.co.ke> wrote:
Hahaha it happens to the best of us. Good thing is once it happens to you, you will be wiser the next time.
On Tue, Mar 29, 2016 at 3:47 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
@Tony yes! 5/- . Apparently. You spend 1 week prototyping a device and 2 weeks getting a pin to work!
:(
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:41 PM, Tony Gacheru <tonygacheru@gmail.com> wrote:
Surely!!!
*From:* joe mwirigi via skunkworks [mailto:skunkworks@lists.my.co.ke] *Sent:* Tuesday, March 29, 2016 3:36 PM *To:* Jimmy Thuo *Cc:* Skunkworks Mailing List *Subject:* Re: [Skunkworks] RE; Mixing straight and crossover cables through a switch
Thanks @Michael And @Jimmy, turns out it was the crimping pins :) Used different ones. As Jimmy had suggested, the pins were not making good contact with the device socket.
Very grateful!
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:18 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
@Jimmy,
We are preparing several straight cables to test this. Will reply after several tests.
Thanks for your time.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:12 PM, Jimmy Thuo <jimmy.thuo@gmail.com> wrote:
Have you tried with a different cable? sometimes the cable termination pin points might not have full contact on some devices whereas on others they are ok.
On Tue, Mar 29, 2016 at 3:03 PM, joe mwirigi via skunkworks < skunkworks@lists.my.co.ke> wrote:
Tried switching the ports,
Pinging A still results to *unreachable with 0%loss*. i.e. all sent packets are received but still no reply from the device. Connecting B to C (2 computers on the same ports) seems ok and replies.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:57 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
Thanks Michael,
Let me do just that, will report back.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:54 PM, Michael Pedersen via skunkworks < skunkworks@lists.my.co.ke> wrote:
For a switch/hub or other network device you generally use a straight (non-crossover cable) - for direct device to device connection you will (in most) cases need a crossover-cable.
1. Some (not all) switches have "auto-sensing" ports that apply crossover or not depending on the cable you use - check the actual specifications of your switch. 2. Common issue is that individual ports in a switch might be "fried", hence maybe the port you have connected A into may be dead - try another port.
.. Mike
On 3/29/16 2:35 PM, joe mwirigi via skunkworks wrote:
To network techies,
I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device.
A to B = works
if I connect A to the switch and B to the switch
A to B through S = Not reachable
If I introduce another computer(C) and assign it a similar IP(that of device A)
C to B through S = works.
Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*).
At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real.
Help
*_______________________________________________________________We must Keep on, We can't stop here *
_______________________________________________
skunkworks mailing list
skunkworks@lists.my.co.ke
------------
List info, subscribe/unsubscribe
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
------------
Skunkworks Rules
http://my.co.ke/phpbb/viewtopic.php?f=24&t=94
------------
Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
--
Best Regards Jimmy Thuo
-- Best Regards Jimmy Thuo
-- Tony White

Thanks @Tony, note taken. Apparently the undisclosed place has a great design covering Km's all done in fiber and standard. !'m the first chinese they've seen in years :( *_______________________________________________________________We must Keep on, We can't stop here * On Tue, Mar 29, 2016 at 5:13 PM, Tony White <tony.mzungu@gmail.com> wrote:
Worth noting...
The cheap RJ45 plugs are intended for crimping on flexible cables which have multiple (usually 7) strands. If you crimp such a plug on solid conductor cable - like oddments of ordinary cat5 cable, then you have one of several possibilities: (a) the pin hits the wire straight on top, and sits too high, or (b) it slides down to the left or right of the conductor, and is twisted, or (c) it cuts the conductor.
With 8 pins in the plug, random chances are that you will get all three variants!
To my knowledge, only Siemon make 'universal' RJ45 plugs, which may be crimped on either solid or flexible cable.
So the solution is either use multi-stranded flexible cable (best) or use Siemon plugs on solid conductor cable.
Cheers, Tony
On 29/03/2016, Jimmy Thuo via skunkworks <skunkworks@lists.my.co.ke> wrote:
Hahaha it happens to the best of us. Good thing is once it happens to you, you will be wiser the next time.
On Tue, Mar 29, 2016 at 3:47 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
@Tony yes! 5/- . Apparently. You spend 1 week prototyping a device and 2 weeks getting a pin to work!
:(
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:41 PM, Tony Gacheru <tonygacheru@gmail.com> wrote:
Surely!!!
*From:* joe mwirigi via skunkworks [mailto:skunkworks@lists.my.co.ke] *Sent:* Tuesday, March 29, 2016 3:36 PM *To:* Jimmy Thuo *Cc:* Skunkworks Mailing List *Subject:* Re: [Skunkworks] RE; Mixing straight and crossover cables through a switch
Thanks @Michael And @Jimmy, turns out it was the crimping pins :) Used different ones. As Jimmy had suggested, the pins were not making good contact with the device socket.
Very grateful!
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:18 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
@Jimmy,
We are preparing several straight cables to test this. Will reply after several tests.
Thanks for your time.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:12 PM, Jimmy Thuo <jimmy.thuo@gmail.com> wrote:
Have you tried with a different cable? sometimes the cable termination pin points might not have full contact on some devices whereas on others they are ok.
On Tue, Mar 29, 2016 at 3:03 PM, joe mwirigi via skunkworks < skunkworks@lists.my.co.ke> wrote:
Tried switching the ports,
Pinging A still results to *unreachable with 0%loss*. i.e. all sent packets are received but still no reply from the device. Connecting B to C (2 computers on the same ports) seems ok and replies.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:57 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
Thanks Michael,
Let me do just that, will report back.
Rgds
*_______________________________________________________________We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 2:54 PM, Michael Pedersen via skunkworks < skunkworks@lists.my.co.ke> wrote:
For a switch/hub or other network device you generally use a straight (non-crossover cable) - for direct device to device connection you will (in most) cases need a crossover-cable.
1. Some (not all) switches have "auto-sensing" ports that apply crossover or not depending on the cable you use - check the actual specifications of your switch. 2. Common issue is that individual ports in a switch might be "fried", hence maybe the port you have connected A into may be dead - try another port.
.. Mike
On 3/29/16 2:35 PM, joe mwirigi via skunkworks wrote:
To network techies,
I've been experiencing a problem which I cannot figure out the cause. I have a device(A) connecting to a switch (S) then a router. If I connect the device directly from a laptop(B), am able to reach the device.
A to B = works
if I connect A to the switch and B to the switch
A to B through S = Not reachable
If I introduce another computer(C) and assign it a similar IP(that of device A)
C to B through S = works.
Device A has no firewall the subnet is the same for all the devices (255.255.255.0) so is the IPs (192.168.0.*).
At first I thought the subject was the problem but C connects to B thro the same setup. or is the device ginxed for real.
Help
*_______________________________________________________________We must Keep on, We can't stop here *
_______________________________________________
skunkworks mailing list
skunkworks@lists.my.co.ke
------------
List info, subscribe/unsubscribe
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
------------
Skunkworks Rules
http://my.co.ke/phpbb/viewtopic.php?f=24&t=94
------------
Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
--
Best Regards Jimmy Thuo
-- Best Regards Jimmy Thuo
-- Tony White

This is exactly why I stopped crimping RJ-45's onto cables years back - somehow there is always "small flaw" that you will end up debugging the rest of the day (of-course with the right test/debug equipment it would be easy - but I don't need a new cable often enough to justify the expense).. I once took a course on implemented structured cabling, intended for electricians who was being trained on such installations - it was quite interesting on the geek-level... For one realizing just how fragile UTP cables are and how easily you can degrade them - just by bending them.. Another take-away point was that a "professional" structured cable installation should come with a frequency/capacity test documented for each and every termination, to verify that this particular termination could actually carry the bandwidth that the cable was originally certified for (i.e. to make sure the electrician had not bended the cable too many times). Since then I have discretely asked office/building-managers to see if they had received the documentation from the installation company.... am yet to see one. Finally it was also nice to learn that there are good and well thought-through standards for how to enumerate the various termination points in a building, IBM has a good one as I recall. Downside it makes my toes cringe whenever I see an office where the ports seems to be numbered by random. Maybe I geek too much... .. Mike On 3/29/16 3:36 PM, joe mwirigi wrote:
Thanks @Michael And @Jimmy, turns out it was the crimping pins :) Used different ones. As Jimmy had suggested, the pins were not making good contact with the device socket.
Very grateful!
/_______________________________________________________________ We must Keep on, We can't stop here /
On Tue, Mar 29, 2016 at 3:18 PM, joe mwirigi <joemwirigi@gmail.com <mailto:joemwirigi@gmail.com>> wrote:
@Jimmy, We are preparing several straight cables to test this. Will reply after several tests.
Thanks for your time.
Rgds
/_______________________________________________________________ We must Keep on, We can't stop here /
On Tue, Mar 29, 2016 at 3:12 PM, Jimmy Thuo <jimmy.thuo@gmail.com <mailto:jimmy.thuo@gmail.com>> wrote:
Have you tried with a different cable? sometimes the cable termination pin points might not have full contact on some devices whereas on others they are ok.

Buy Siemon (quality ) Rest Easy... simple ! On Tue, Mar 29, 2016 at 8:46 PM, Michael Pedersen via skunkworks < skunkworks@lists.my.co.ke> wrote:
This is exactly why I stopped crimping RJ-45's onto cables years back - somehow there is always "small flaw" that you will end up debugging the rest of the day (of-course with the right test/debug equipment it would be easy - but I don't need a new cable often enough to justify the expense)..
I once took a course on implemented structured cabling, intended for electricians who was being trained on such installations - it was quite interesting on the geek-level...
For one realizing just how fragile UTP cables are and how easily you can degrade them - just by bending them..
Another take-away point was that a "professional" structured cable installation should come with a frequency/capacity test documented for each and every termination, to verify that this particular termination could actually carry the bandwidth that the cable was originally certified for (i.e. to make sure the electrician had not bended the cable too many times). Since then I have discretely asked office/building-managers to see if they had received the documentation from the installation company.... am yet to see one.
Finally it was also nice to learn that there are good and well thought-through standards for how to enumerate the various termination points in a building, IBM has a good one as I recall. Downside it makes my toes cringe whenever I see an office where the ports seems to be numbered by random.
Maybe I geek too much...
.. Mike
On 3/29/16 3:36 PM, joe mwirigi wrote:
Thanks @Michael And @Jimmy, turns out it was the crimping pins :) Used different ones. As Jimmy had suggested, the pins were not making good contact with the device socket.
Very grateful!
*_______________________________________________________________ We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:18 PM, joe mwirigi <joemwirigi@gmail.com> wrote:
@Jimmy, We are preparing several straight cables to test this. Will reply after several tests.
Thanks for your time.
Rgds
*_______________________________________________________________ We must Keep on, We can't stop here *
On Tue, Mar 29, 2016 at 3:12 PM, Jimmy Thuo < <jimmy.thuo@gmail.com> jimmy.thuo@gmail.com> wrote:
Have you tried with a different cable? sometimes the cable termination pin points might not have full contact on some devices whereas on others they are ok.
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
-- ALVIN OCHOLA 0722-313923 www.greenline.co.ke
participants (6)
-
Alvin Jason Ochieng
-
Jimmy Thuo
-
joe mwirigi
-
Michael Pedersen
-
Tony Gacheru
-
Tony White