Solved

Connected to 205.178.149.7 but connection died. (#4.4.2)

Posted on 2009-05-19
5
2,387 Views
Last Modified: 2013-12-02
My client @precisionpixelstudios.com on a linux server (209.104.3.182) can not email an address @michaelmcdermott.com.

Here is the error message:
Hi. This is the qmail-send program at exodus1.irapture.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
Connected to 205.178.149.7 but connection died. (#4.4.2)
I'm not going to try again; this message has been in the queue too long.


Notes:

I can ping 205.178.149.7 from 209.104.3.182.


Here is the traceroute from precisionpixelstudio.com's mail server to michaelmcdermott.com's networksolution.com's mail server:

traceroute to 205.178.149.7 (205.178.149.7), 30 hops max, 38 byte packets
 1  209.104.6.76 (209.104.6.76)  0.105 ms  0.055 ms  0.049 ms
 2  tus1.Login.COM (209.104.1.7)  0.422 ms  0.356 ms  0.380 ms
 3  tcs-edge-02.inet.qwest.net (65.121.93.133)  0.753 ms  0.678 ms  0.597 ms
 4  tcs-core-01.inet.qwest.net (205.171.212.41)  0.682 ms  0.772 ms  0.584 ms
 5  lap-brdr-03.inet.qwest.net (67.14.22.74)  13.238 ms  13.006 ms  12.900 ms
 6  63.146.26.182 (63.146.26.182)  12.958 ms 63.146.26.162 (63.146.26.162)  12.986 ms 63.146.26.182 (63.146.26.182)  13.119 ms
 7  te-4-1-0.rar3.la-ca.us.xo.net (207.88.12.153)  13.536 ms  14.303 ms  13.795 msIcmp checksum is wrong
 8  65.106.1.69.ptr.us.xo.net (65.106.1.69)  13.691 msIcmp checksum is wrong  13.731 msIcmp checksum is wrong
  13.523 ms Icmp checksum is wrong
 9  p6-0-0.RAR1.Dallas-TX.us.xo.net (65.106.0.13)  37.885 msIcmp checksum is wrong  49.145 msIcmp checksum is wrong  37.920 msIcmp checksum is wrong
10  p0-0-0d0.rar2.dallas-tx.us.xo.net (65.106.1.38)  38.000 msIcmp checksum is wrong  44.497 msIcmp checksum is wrong  51.442 msIcmp checksum is wrong
11  p6-0-0.rar1.atlanta-ga.us.xo.net (65.106.0.9)  81.718 msIcmp checksum is wrong  72.063 msIcmp checksum is wrong  71.990 msIcmp checksum is wrong
12  p0-0-0d0.rar2.atlanta-ga.us.xo.net (65.106.1.26)  85.004 msIcmp checksum is wrong  71.771 msIcmp checksum is wrong  71.925 ms
13  p1-0-0.rar2.washington-dc.us.xo.net (65.106.0.5)  71.805 ms  71.714 ms  81.323 ms
14  p7-0-0.MAR2.Washington5-DC.us.xo.net (65.106.3.206)  72.465 ms  72.436 ms  72.565 ms
15  71.5.190.110.ptr.us.xo.net (71.5.190.110)  72.391 ms  72.505 ms  72.476 ms
16  64.244.254.238 (64.244.254.238)  73.724 ms  73.987 ms  73.595 ms
17  edg-r-01-vlan12.net.dc2.netsol.com (205.178.191.14)  72.243 ms  72.200 ms  72.173 ms
18  205.178.182.6 (205.178.182.6)  73.718 ms  73.728 ms  73.655 ms
19  mail.networksolutionsemail.com (205.178.149.7)  72.250 ms  72.233 ms  72.293 ms

0
Comment
Question by:iRapture
  • 3
  • 2
5 Comments
 
LVL 20

Expert Comment

by:Daniel McAllister
ID: 24433639
The results of the tracertoute would indicate that you're having a significant error connecting (i.e.: data corruption is occurring) through some XO Communications routers.

Your ISP appears to be Qwest (or at least a client of Qwest)... I suggest that this information be shared with them (they will be the only ones XO will listen to about errors).

Then again, it could be safe to assume that they are (or will be very soon) aware of the issue and will work to resolve it.

I am assuming that other mail recipients receive messages without error....

Sorry I cannot be more helpful... (as in -- there is nothing YOU can do proactively, just report it up-stream in the Internet)

Dan
IT4SOHO
0
 
LVL 20

Expert Comment

by:Daniel McAllister
ID: 24666597
Any update?

This is now a month-old issue. Please close the question if you have resolved it.

Thanks,

Dan
IT4SOHO
0
 

Author Comment

by:iRapture
ID: 25020124
traceroute showed that one of the ips in the middle of the connection were blocked on the server for abuse.
0
 
LVL 20

Accepted Solution

by:
Daniel McAllister earned 500 total points
ID: 25024636
I have never "objected" to a user "reclaiming" a question before -- and I'm going to hit "submit" below, rather than formally objecting... but I fail to see how pointing you to the failure messages in the traceroute didn't lead you to your solution.

I'm just sayin....

Dan
IT4SOHO
0
 

Author Comment

by:iRapture
ID: 25036107
If you are looking for advice on a similiar problem I would advise to skip this thread and keep looking. I don't think the solution was found and the problem went away before a solution could be found.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Email signatures have numerous marketing benefits. Here are 8 top reasons to turn your email signature into a marketing channel.
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question