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