Please help me diag a Qworst routing issue..

[Michael March]

<mbydalek at compunetconsulting.com> wrote:
>
>  No, you're not in the same block =/  Also, you labeled this as a "routing"
> issue .. are you so sure?  It seems you can reach the server successfully.
>
>  Have you used tools such as traceroute (or tracepath), nmap, etc. to make
> sure you're getting to their servers (in)correctly?

nmap output:
root at pbx:/etc/asterisk $ nmap -v -P0 netconnect1.paymentech.net

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2008-03-07 11:19 MST
DNS resolution of 1 IPs took 0.62s.
Initiating SYN Stealth Scan against netconnect1.paymentech.net (65.124.118.120)
Discovered open port 443/tcp on 65.124.118.120
SYN Stealth Scan Timing: About 49.40% done; ETC: 11:20 (0:00:30 remaining)
The SYN Stealth Scan took 58.85s to scan 1680 total ports.
Host netconnect1.paymentech.net (65.124.118.120) appears to be up ... good.
Interesting ports on netconnect1.paymentech.net (65.124.118.120):
Not shown: 1678 filtered ports
PORT    STATE  SERVICE
80/tcp  closed http
443/tcp open   https

Nmap finished: 1 IP address (1 host up) scanned in 59.587 seconds
               Raw packets sent: 3369 (148.236KB) | Rcvd: 12 (552B)
root at pbx:/etc/asterisk $


>Perhaps it could be
> tpaymentech blocking you for some reason.  Have you contacted them?

Yeah.. I tried WireShark last night.. only to see what hosts it was
trying to hit.. I wish I looked a little more carefully..

I'll try to run it again remotely..

>  The best thing to do would be to fire up wireshark and see what's going on.
> Maybe you're never receiving an ACK back? Basically the goal would be find
> out where it's breaking down and go from there.
>
>  Just some thoughts =)


Great thoughts.. thanks!