>Scott or others,
>how can I locate the problem ?
>I can't connect to the mx server
>216.72.25.226
I get the same IP for the MX record, but I can connect to it.
>here is the tracert I get
>1 7 7 172.16.12.1
>2 23 16 208.154.200.5
>3 719 696 10.0.6.1
>4 867 148 192.168.230.18
>5 664 -203 207.45.219.18
>*
>*
It looks like minrex.gov.cu's routing is poorly set up. You've got a
private IP (yours, I would assume) going to a public IP, to 2 private IPs,
to a public IP. That's extremely bad routing. From here, a tracert takes
16 hops, but only has 2 private IPs (both 192.168.253.50 and
192.168.240.46) at the very end.
It's hard to say where the problem is, but if you're losing packets after
the 5th hop, I would suspect a problem on your end. Note that
208.154.200.5 is a public IP (yours), which is then going through 2
different private IP rantes before hitting 207.45.219.18, which is either
dropping the packet or routing it to a blackhole somewhere.
I'd check with your upstream to find out what is happening.
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
This E-mail came from the Declude.Virus mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.Virus". You can E-mail
[EMAIL PROTECTED] for assistance. You can visit our web
site at http://www.declude.com .
