Problem with Paypal connection - Error (28) connect() timed out!

[mc12345678]

Before discussing this further, what was the exact traceroute command that you are using for testing?

Unless you enable TCP and specify port 443 it is unlikely your results are telling you much at all.

-------------------------------------------------------
Example#1 (seemingly blocked / no route)
rod@sue:~# traceroute api-3t.paypal.com
traceroute to api-3t.paypal.com (173.0.88.69), 30 hops max, 60 byte packets
1 gw (192.168.0.254) 0.871 ms 1.163 ms 1.662 ms
2 lns20.adl2.on.ii.net (203.16.215.197) 40.294 ms 41.506 ms 42.412 ms
3 te3-3.cor3.adl2.on.ii.net (150.101.134.29) 44.132 ms 45.606 ms 47.304 ms
4 xe-0-0-0.cr1.adl6.on.ii.net (150.101.225.77) 48.920 ms 50.429 ms 52.932 ms
5 ae4.br1.syd7.on.ii.net (150.101.33.34) 73.005 ms 73.829 ms 75.752 ms
6 te0-2-1-2.br1.sjc2.on.ii.net (150.101.33.147) 232.961 ms 233.349 ms 233.677 ms
7 144.232.191.193 (144.232.191.193) 266.432 ms 244.702 ms 244.354 ms
8 sl-payp2-413771-0.sprintlink.net (144.232.191.210) 215.993 ms 217.464 ms 218.960 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
rod@sue:~#

Example#2 (Using TCP port 443 shows all ok)
rod@sue:~# traceroute-T -p 443 api-3t.paypal.com
traceroute to api-3t.paypal.com (173.0.88.101), 30 hops max, 60 byte packets
1 gw (192.168.0.254) 0.847 ms 1.196 ms 1.528 ms
2 lns20.adl2.on.ii.net (203.16.215.197) 60.540 ms 60.752 ms 60.994 ms
3 te3-3.cor3.adl2.on.ii.net (150.101.134.29) 71.761 ms 71.901 ms 71.958 ms
4 xe-0-0-0.cr1.adl6.on.ii.net (150.101.225.77) 61.367 ms 61.633 ms 61.635 ms
5 * * *
6 te0-2-1-2.br1.sjc2.on.ii.net (150.101.33.147) 233.445 ms 232.920 ms 234.687 ms
7 144.232.191.193 (144.232.191.193) 292.718 ms 216.278 ms 225.398 ms
8 sl-payp2-413771-0.sprintlink.net (144.232.191.210) 217.304 ms 218.512 ms 219.541 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 api-3t.paypal.com (173.0.88.101) 243.720 ms 245.597 ms 246.570 ms
rod@sue:~#
--------------------------------------------------

Cheers
Rod

Example #1 was the latest attempt. Thought I had looked through the command options for determination of a secure route, but guess I missed. The obvious.

When I performed a traceroute from a New Zealand service they identified the same general end service location as option #2.

Previous discussion in this or a similar thread has provided the same end result as #2, but a follow on comment was that it was still AT&T even though the end result was sprintlink. Advice?

Also, today wrote back to AT&T asking if they showed traffic through their servers from or IP address, and was provided a traceroute from them to us. (Thinking also in format of option #1.)

[RodG]

Previous discussion in this or a similar thread has provided the same end result as #2,

This is the result needed. If this traceroute works, the processing will also work.

but a follow on comment was that it was still AT&T

The traceroute example I provided shows that there is no problem between my localhost and the paypal server. It doesn't tell us anything about the connectivity between your store and PayPal.

even though the end result was sprintlink. Advice?

Unless proven otherwise I will be assuming that all traceroutes performed so far (even those performed by AT&T) were done without the required options.

Also, today wrote back to AT&T asking if they showed traffic through their servers from or IP address, and was provided a traceroute from them to us. (Thinking also in format of option #1.)

Unless you know the traceroute command being used the results are worthless.

Show me the output of a traceroute-T -p 443 api-3t.paypal.com from your store, because I'm seeing conflicting information here.

Cheers
Rod