On Friday 07 March 2008, Michael March wrote:
> I'm helping a friend setup a POS system (running 95% Linux of course!)
> and it does creditcard processing via Paymentech over the net. He has
> Qworst DSL as his provider and for the life of me I can't get it to
> connect to the credit card server for the past 24hrs. We can reach
> Paymentech from ANY OTHER NETWORK. I'm fighting with Qwest now over
> this issue but I want to ask any of you who also uses Qwest in PHX if
> you could try to access the Paymentech URL from your Linux box..
>
> Here is a successful test:
>
> mmarch@werkstation-wk:~$ wget
> https://netconnect.paymentech.net/NetConnect/controler
> --10:22:57-- https://netconnect.paymentech.net/NetConnect/controler
> => `controler'
> Resolving netconnect.paymentech.net... 65.124.118.170
> Connecting to netconnect.paymentech.net|65.124.118.170|:443... connected.
> ERROR: Certificate verification error for netconnect.paymentech.net:
> unable to get local issuer certificate
> To connect to netconnect.paymentech.net insecurely, use
> `--no-check-certificate'.
> Unable to establish SSL connection.
>
> Here is an unsuccessful test:
>
> root@pbx:/etc/asterisk $ wget https://netconnect.paymentech.net
> --09:38:27-- https://netconnect.paymentech.net/
> Resolving netconnect.paymentech.net... 65.124.118.170
> Connecting to netconnect.paymentech.net|65.124.118.170|:443... connected.
>
> If you guys can, I'll have a really hard fight with Qwest.. if you
> can't, I'll have a bigger club to hit them with.
>
> Thanks!
ok,
I sent a response indicating that a 404 was found from my cox.net address..
ping results are as follows:
PING netconnect.paymentech.net (65.124.118.170) 56(84) bytes of data.
--- netconnect.paymentech.net ping statistics ---
13 packets transmitted, 0 received, 100% packet loss, time 12011ms
******************
and here is my traceroute:
(make a note that it looks like some router messup on hops 10,11 and that
no connectivity can be measured after hop 16. it seems as though its the
far end that has the problem.
*****************
proudhawk@t95:~$ traceroute netconnect.paymentech.net
traceroute to netconnect.paymentech.net (65.124.118.170), 30 hops max, 40 byte packets
1 m163.avondale (192.168.1.254) 0.152 ms 0.070 ms 0.073 ms
2 10.148.128.1 (10.148.128.1) 61.903 ms 61.780 ms 64.366 ms
3 68.2.8.69 (68.2.8.69) 64.494 ms 64.492 ms 64.319 ms
4 68.2.13.78 (68.2.13.78) 63.499 ms 67.410 ms 67.326 ms
5 68.2.13.1 (68.2.13.1) 68.037 ms 68.051 ms 68.016 ms
6 chnddsrj01-ae2.0.rd.ph.cox.net (68.2.14.9) 67.364 ms 67.332 ms 67.159 ms
7 te-3-4.car1.Phoenix1.Level3.net (4.79.184.153) 68.465 ms 64.885 ms 67.674 ms
8 ae-11-11.car2.Phoenix1.Level3.net (4.69.133.34) 267.222 ms 267.258 ms 267.278 ms
9 ae-4-4.ebr2.LosAngeles1.Level3.net (4.69.133.38) 134.796 ms 134.940 ms 134.967 ms
10 ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 131.151 ms ae-72-72.csw2.LosAngeles1.Level3.net (4.69.137.22) 126.662 ms ae-82-82.cs w3.LosAngeles1.Level3.net (4.69.137.26) 126.755 ms
11 ae-44-99.car4.LosAngeles1.Level3.net (4.68.20.198) 126.987 ms ae-14-69.car4.LosAngeles1.Level3.net (4.68.20.6) 126.764 ms ae-34-89.car4 .LosAngeles1.Level3.net (4.68.20.134) 126.794 ms
12 qwest-level3-te.LosAngeles1.Level3.net (4.68.63.66) 126.999 ms 126.844 ms 127.572 ms
13 los-core-01.inet.qwest.net (205.171.32.1) 135.791 ms 94.204 ms 103.310 ms
14 * * *
15 bos-core-01.inet.qwest.net (205.171.8.25) 169.650 ms 169.690 ms 168.856 ms
16 bos-edge-03.inet.qwest.net (205.171.28.38) 166.495 ms 162.903 ms 166.793 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
***************
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)