Vick's dashboard

For anyone that knows how to interpret trace routes beyond the basics, here is the one from the computer that can connect

Tracing route to linkedin.com [64.74.98.86]
over a maximum of 30 hops:

1 * * * Request timed out.
2 1 ms 1 ms 1 ms 69-106-211-150.tscgsolutions.com [69.106.211.150
]
3 10 ms 10 ms 10 ms 192.0.2.100
4 14 ms 19 ms 10 ms dist3-vlan65.irvnca.pbi.net [67.114.48.129]
5 10 ms 9 ms 10 ms bb1-p6-7.emhril.ameritech.net [151.164.42.3]
6 * * * Request timed out.
7 21 ms 11 ms 13 ms asn4725-japantelecom.eqlaca.sbcglobal.net [151.1
64.251.38]
8 21 ms 21 ms 23 ms tge9-3.fr4.sjc.llnw.net [69.28.172.54]
9 69 ms 74 ms 74 ms tge1-1.fr3.ord.llnw.net [69.28.171.65]
10 65 ms 65 ms 65 ms linkedin.tge3-4.fr3.ord.llnw.net [208.111.156.70
]
11 65 ms 65 ms 65 ms www.linkedin.com.ar [64.74.98.86]

Trace complete.

And here is the traceroute from all others that cannot connect

Tracing route to linkedin.com [64.74.98.86]
over a maximum of 30 hops:

1 * * * Request timed out.
2 1 ms 1 ms 1 ms 69-106-211-150.tscgsolutions.com [69.106.211.150
]
3 10 ms 9 ms 9 ms 192.0.2.100
4 10 ms 9 ms 10 ms dist3-vlan65.irvnca.pbi.net [67.114.48.129]
5 10 ms 10 ms 10 ms bb1-g4-0.irvnca.sbcglobal.net [151.164.43.141]
6 11 ms 11 ms 11 ms 151.164.98.61
7 21 ms 11 ms 13 ms asn4725-japantelecom.eqlaca.sbcglobal.net [151.1
64.251.38]
8 25 ms 23 ms 25 ms tge9-3.fr4.sjc.llnw.net [69.28.172.54]
9 64 ms 66 ms 74 ms tge1-1.fr3.ord.llnw.net [69.28.171.65]
10 65 ms 64 ms 64 ms linkedin.tge3-4.fr3.ord.llnw.net [208.111.156.70
]
11 65 ms 65 ms 65 ms linkedin.com.ar [64.74.98.86]

Trace complete.

Both computers seem to get there. So the plot thickens.

Vick