No route to host - TCP-IP

This is a discussion on No route to host - TCP-IP ; We have a simple network: a) One Linux server 192.168.1.1 b) One Windows workstation 192.168.1.12 Both access the internet via an ADSL connection: modem/router@ 192.168.1.254. The server runs the apps but does not run a DNS server, DHCP is handled ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: No route to host

  1. No route to host

    We have a simple network:
    a) One Linux server 192.168.1.1
    b) One Windows workstation 192.168.1.12

    Both access the internet via an ADSL connection: modem/router@
    192.168.1.254.

    The server runs the apps but does not run a DNS server, DHCP is handled by
    the router.

    The Linux fax server should forward faxes received to an email address
    however this is not happening.

    I have tried to diagnose this problem however have gotten nowhere and am
    loath to start changing many setting in fear that I turn a relatively simple
    problem into a complex one.

    The following entry, and many others like it, are logged in /var/log/maillog

    May 29 13:31:52 declan sendmail[6116]: k4RBqD69004136:
    to=username@ourdomain.com.au, ctladdr=
    (78/78), delay=1+17:39:39, xdelay=00:00:00, mailer=esmtp, pri=3943029,
    relay=mail3.zoneedit.com., dsn=4.0.0, stat=Deferred: mail3.zoneedit.com.: No
    route to host

    Our domain name "ourdomain.com.au" is hosted by zoneedit.com who forward
    emails received to this domain to the ISP email accounts.

    I understand from my research that this is not a sendmail problem but simply
    a DNS problem however it intrigues me that the server has associated
    ourdomain.com.au with zoneedit.com which implies to me the links are being
    made correctly.

    I can traceroute to mail3.zoneedit.com as per below:

    [root@declan /]# traceroute mail3.zoneedit.com
    traceroute to mail3.zoneedit.com (216.133.67.106), 30 hops max, 38 byte
    packets
    1 home.gateway (192.168.1.254) 0.517 ms 0.544 ms 0.527 ms
    2 nexthop.wa.ii.net (203.59.14.16) 367.998 ms 373.839 ms 376.146 ms
    3 gi2-3.per-qv1-bdr2.ii.net (203.215.4.30) 377.825 ms 404.063 ms
    406.515 ms
    4 po5-2.syd-mci-bdr1.ii.net (203.215.4.253) 466.781 ms 464.174 ms
    464.173 ms
    5 202.139.19.21 (202.139.19.21) 463.321 ms 464.861 ms 202.139.19.29
    (202.139.19.29) 463.314 ms
    6 203.208.148.101 (203.208.148.101) 672.719 ms 631.518 ms 647.936 ms
    7 ge-4-0-0.plapx-ar3.ix.singtel.com (203.208.168.110) 642.618 ms
    ge-0-0-0.plapx-ar3.ix.singtel.com (203.208.168.106) 633.044 ms 655.549 ms
    8 * * *
    9 giga10-0.pao-c001.gw.epoch.net (155.229.101.98) 652.297 ms 649.010 ms
    665.215 ms
    10 pos0-0.dcp-c000.gw.epoch.net (155.229.57.5) 708.436 ms 710.051 ms
    735.167 ms
    MPLS Label=3087 CoS=5 TTL=1 S=0
    11 pos1-0.btm-m200.gw.epoch.net (155.229.123.213) 719.241 ms 713.039 ms
    722.809 ms
    12 206-135-244-114.btm-m200.cust.gw.epoch.net (206.135.244.114) 762.203 ms
    784.713 ms 788.146 ms
    13 mail3.zoneedit.com (216.133.67.106) 800.079 ms 779.147 ms 780.510 ms
    [root@declan /]#


    I cannot ping mail3.zoneedit.com as per below, it picks up the ip address
    but simply hangs:

    [root@declan /]# ping mail3.zoneedit.com
    PING mail3.zoneedit.com (216.133.67.106) 56(84) bytes of data.

    The following is the resolv.conf file, not sure if it helps but may
    assist...

    [root@declan /]# cat /etc/resolv.conf
    search ourdomain
    nameserver 192.168.1.254
    [root@declan /]#


    Any help here would be greatly appreciated... thanks in advance...



  2. Re: No route to host

    In article
    <447a9fa0$0$7888$5a62ac22@per-qv1-newsreader-01.iinet.net.au>,
    "McHenry" wrote:

    > We have a simple network:
    > a) One Linux server 192.168.1.1
    > b) One Windows workstation 192.168.1.12
    >
    > Both access the internet via an ADSL connection: modem/router@
    > 192.168.1.254.
    >
    > The server runs the apps but does not run a DNS server, DHCP is handled by
    > the router.
    >
    > The Linux fax server should forward faxes received to an email address
    > however this is not happening.
    >
    > I have tried to diagnose this problem however have gotten nowhere and am
    > loath to start changing many setting in fear that I turn a relatively simple
    > problem into a complex one.
    >
    > The following entry, and many others like it, are logged in /var/log/maillog
    >
    > May 29 13:31:52 declan sendmail[6116]: k4RBqD69004136:
    > to=username@ourdomain.com.au, ctladdr=
    > (78/78), delay=1+17:39:39, xdelay=00:00:00, mailer=esmtp, pri=3943029,
    > relay=mail3.zoneedit.com., dsn=4.0.0, stat=Deferred: mail3.zoneedit.com.: No
    > route to host
    >
    > Our domain name "ourdomain.com.au" is hosted by zoneedit.com who forward
    > emails received to this domain to the ISP email accounts.
    >
    > I understand from my research that this is not a sendmail problem but simply
    > a DNS problem however it intrigues me that the server has associated
    > ourdomain.com.au with zoneedit.com which implies to me the links are being
    > made correctly.


    Why do you think it's a DNS problem?

    What happens if you do: telnet mail3.zoneedit.com 25

    If there's a firewall somewhere blocking port 25, that would result in
    "No route to host".

    --
    Barry Margolin, barmar@alum.mit.edu
    Arlington, MA
    *** PLEASE post questions in newsgroups, not directly to me ***
    *** PLEASE don't copy me on replies, I'll read them in the group ***

  3. Re: No route to host

    > mail3.zoneedit.com.: No route to host

    Quite odd. Perhaps your ISP is screwing about. Try a tcp trace. Upon
    performing my own testing, it seems that mail3 is not responding
    properly. Though, I detected no icmp response when trying to reach mail3
    and that is what I would attribute the above error. Try resending and
    monitor for icmp. Failing that, try sending to mail2.


    dm# hping -STp 25 mail3.zoneedit.com
    HPING mail3.zoneedit.com (vlan4 216.133.67.106): S set, 40 headers + 0
    data bytes
    hop=1 TTL 0 during transit from ip=195.16.87.33 name=r3.deadghost.com
    hop=1 hoprtt=2.5 ms
    hop=2 TTL 0 during transit from ip=194.126.235.1
    name=rtr-1.peering.virt-ix.net
    hop=2 hoprtt=192.9 ms
    hop=3 TTL 0 during transit from ip=213.193.208.73
    name=c1201-gateway.trueserver.nl
    hop=3 hoprtt=188.3 ms
    hop=4 TTL 0 during transit from ip=87.233.192.2
    name=10ge-6-0.e600-2.ams5.true.nl
    hop=4 hoprtt=197.7 ms
    hop=5 TTL 0 during transit from ip=87.233.192.14
    name=10ge-6-1.e600-1.ams1.true.nl
    hop=5 hoprtt=196.0 ms
    hop=6 TTL 0 during transit from ip=87.233.192.22
    name=10ge-6-0.e600-2.ams1.true.nl
    hop=6 hoprtt=196.2 ms
    hop=7 TTL 0 during transit from ip=213.193.235.158
    name=wedare-gw.trueserver.nl
    hop=7 hoprtt=194.1 ms
    hop=8 TTL 0 during transit from ip=84.244.177.46
    name=ge-1-1-0.ar3.ams.we-dare.net
    hop=8 hoprtt=193.3 ms
    hop=9 TTL 0 during transit from ip=195.69.144.124
    name=te3-3.mpd01.ams03.atlas.cogentco.com
    hop=9 hoprtt=465.5 ms
    hop=10 TTL 0 during transit from ip=130.117.0.33
    name=t2-0-0.core01.ams03.atlas.cogentco.com
    hop=10 hoprtt=191.1 ms
    hop=11 TTL 0 during transit from ip=130.117.1.170
    name=p9-0.core02.jfk02.atlas.cogentco.com
    hop=11 hoprtt=274.6 ms
    hop=12 TTL 0 during transit from ip=66.28.4.13
    name=p15-0.core01.jfk02.atlas.cogentco.com
    hop=12 hoprtt=375.2 ms
    hop=13 TTL 0 during transit from ip=66.28.4.178
    name=p5-0.core01.bwi01.atlas.cogentco.com
    hop=13 hoprtt=284.4 ms
    hop=14 TTL 0 during transit from ip=38.112.18.18
    name=balt.demarc.cogentco.com
    hop=14 hoprtt=281.5 ms
    hop=15 TTL 0 during transit from ip=38.112.72.1
    name=core.38-112-72-1.balticore.net
    hop=15 hoprtt=357.5 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4929 sport=25 flags=RA seq=1
    win=512 rtt=29774.3 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4932 sport=25 flags=R seq=2
    win=512 rtt=29773.0 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4936 sport=25 flags=R seq=3
    win=512 rtt=29776.0 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4938 sport=25 flags=R seq=4
    win=512 rtt=29787.8 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4940 sport=25 flags=R seq=5
    win=512 rtt=29773.5 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4942 sport=25 flags=R seq=6
    win=512 rtt=29776.4 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4944 sport=25 flags=R seq=7
    win=512 rtt=29775.6 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4948 sport=25 flags=RA seq=8
    win=512 rtt=29774.4 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4950 sport=25 flags=R seq=9
    win=512 rtt=29773.1 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4952 sport=25 flags=R seq=10
    win=512 rtt=29772.1 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4954 sport=25 flags=R seq=11
    win=512 rtt=29774.8 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4957 sport=25 flags=R seq=12
    win=512 rtt=29773.9 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4960 sport=25 flags=R seq=13
    win=512 rtt=29773.0 ms
    DUP! len=46 ip=216.133.67.106 ttl=255 id=4963 sport=25 flags=R seq=14
    win=512 rtt=29775.5 ms
    len=46 ip=216.133.67.106 ttl=255 id=4966 sport=25 flags=R seq=15 win=512
    rtt=29774.8 ms
    len=46 ip=216.133.67.106 ttl=255 id=4968 sport=25 flags=R seq=16 win=512
    rtt=29773.4 ms
    len=46 ip=216.133.67.106 ttl=255 id=4973 sport=25 flags=R seq=17 win=512
    rtt=29776.6 ms
    len=46 ip=216.133.67.106 ttl=255 id=4975 sport=25 flags=R seq=18 win=512
    rtt=29775.2 ms
    len=46 ip=216.133.67.106 ttl=255 id=4978 sport=25 flags=R seq=19 win=512
    rtt=29774.4 ms
    len=46 ip=216.133.67.106 ttl=255 id=4981 sport=25 flags=R seq=20 win=512
    rtt=29777.1 ms
    len=46 ip=216.133.67.106 ttl=255 id=4985 sport=25 flags=RA seq=21
    win=512 rtt=29775.7 ms
    len=46 ip=216.133.67.106 ttl=255 id=4987 sport=25 flags=R seq=22 win=512
    rtt=29774.8 ms
    len=46 ip=216.133.67.106 ttl=255 id=4991 sport=25 flags=R seq=23 win=512
    rtt=29773.5 ms
    len=46 ip=216.133.67.106 ttl=255 id=4993 sport=25 flags=R seq=24 win=512
    rtt=29776.4 ms
    len=46 ip=216.133.67.106 ttl=255 id=4997 sport=25 flags=R seq=25 win=512
    rtt=29775.4 ms
    len=46 ip=216.133.67.106 ttl=255 id=5001 sport=25 flags=R seq=26 win=512
    rtt=29774.6 ms
    len=46 ip=216.133.67.106 ttl=255 id=5003 sport=25 flags=R seq=27 win=512
    rtt=29773.3 ms
    len=46 ip=216.133.67.106 ttl=255 id=5006 sport=25 flags=R seq=28 win=512
    rtt=29772.4 ms
    len=46 ip=216.133.67.106 ttl=255 id=5011 sport=25 flags=R seq=29 win=512
    rtt=29775.1 ms
    len=46 ip=216.133.67.106 ttl=255 id=5013 sport=25 flags=R seq=30 win=512
    rtt=29774.1 ms
    len=46 ip=216.133.67.106 ttl=255 id=5015 sport=25 flags=R seq=31 win=512
    rtt=29772.7 ms
    len=46 ip=216.133.67.106 ttl=255 id=5019 sport=25 flags=R seq=32 win=512
    rtt=29775.7 ms
    len=46 ip=216.133.67.106 ttl=255 id=5022 sport=25 flags=R seq=33 win=512
    rtt=29774.5 ms
    len=46 ip=216.133.67.106 ttl=255 id=5025 sport=25 flags=R seq=34 win=512
    rtt=29781.4 ms
    len=46 ip=216.133.67.106 ttl=255 id=5028 sport=25 flags=RA seq=35
    win=512 rtt=29772.7 ms
    len=46 ip=216.133.67.106 ttl=255 id=5030 sport=25 flags=R seq=36 win=512
    rtt=29775.1 ms
    ^C
    --- mail3.zoneedit.com hping statistic ---
    66 packets tramitted, 51 packets received, 23% packet loss
    round-trip min/avg/max = 2.5/21088.1/29787.8 ms
    dm# host zoneedit.com
    zoneedit.com has address 69.72.176.180
    zoneedit.com has address 69.72.176.188
    zoneedit.com mail is handled by 0 mail3.zoneedit.com.
    zoneedit.com mail is handled by 0 mail2.zoneedit.com.
    dm# hping -STp 25 mail2.zoneedit.com
    HPING mail2.zoneedit.com (vlan4 216.40.250.211): S set, 40 headers + 0
    data bytes
    hop=1 TTL 0 during transit from ip=195.16.87.33 name=r3.deadghost.com
    hop=1 hoprtt=1.9 ms
    hop=2 TTL 0 during transit from ip=194.126.235.1
    name=rtr-1.peering.virt-ix.net
    hop=2 hoprtt=231.4 ms
    hop=3 TTL 0 during transit from ip=213.193.208.73
    name=c1201-gateway.trueserver.nl
    hop=3 hoprtt=248.8 ms
    hop=4 TTL 0 during transit from ip=87.233.192.2
    name=10ge-6-0.e600-2.ams5.true.nl
    hop=4 hoprtt=196.6 ms
    hop=5 TTL 0 during transit from ip=87.233.192.14
    name=10ge-6-1.e600-1.ams1.true.nl
    hop=5 hoprtt=205.0 ms
    hop=6 TTL 0 during transit from ip=87.233.192.22
    name=10ge-6-0.e600-2.ams1.true.nl
    hop=6 hoprtt=197.4 ms
    hop=7 TTL 0 during transit from ip=213.193.235.158
    name=wedare-gw.trueserver.nl
    hop=7 hoprtt=194.7 ms
    hop=8 TTL 0 during transit from ip=84.244.177.46
    name=ge-1-1-0.ar3.ams.we-dare.net
    hop=8 hoprtt=196.6 ms
    hop=9 TTL 0 during transit from ip=195.69.144.122
    name=ge-5-1-0.mpr3.ams1.nl.above.net
    hop=9 hoprtt=192.7 ms
    hop=10 TTL 0 during transit from ip=64.125.27.222
    name=64.125.27.222.available.above.net
    hop=10 hoprtt=200.6 ms
    hop=11 TTL 0 during transit from ip=64.125.27.165
    name=so-7-0-0.cr2.dca2.us.above.net
    hop=11 hoprtt=325.6 ms
    hop=12 TTL 0 during transit from ip=64.125.29.169
    name=so-3-0-0.cr2.dfw2.us.above.net
    hop=12 hoprtt=330.4 ms
    hop=13 TTL 0 during transit from ip=64.125.29.17
    name=so-4-1-0.mpr2.iah1.us.above.net
    hop=13 hoprtt=348.0 ms
    hop=14 TTL 0 during transit from ip=216.200.251.26
    name=289.ge-3-2-1.mpr1.iah1.us.above.net
    hop=14 hoprtt=399.9 ms
    hop=15 TTL 0 during transit from ip=207.218.245.29
    name=ivhou-207-218-245-29.ev1.net
    hop=15 hoprtt=305.9 ms
    hop=16 TTL 0 during transit from ip=207.218.245.126
    name=ivhou-207-218-245-126.ev1.net
    hop=16 hoprtt=344.8 ms
    len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=16
    win=5840 rtt=393.6 ms
    len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=17
    win=5840 rtt=304.3 ms
    DUP! len=46 ip=216.40.250.211 ttl=255 id=5122 sport=25 flags=R seq=17
    win=512 rtt=414.0 ms
    len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=18
    win=5840 rtt=304.8 ms
    len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=19
    win=5840 rtt=300.2 ms
    len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=20
    win=5840 rtt=299.9 ms
    len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=21
    win=5840 rtt=354.3 ms
    len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=22
    win=5840 rtt=308.0 ms
    DUP! len=46 ip=216.40.250.211 ttl=255 id=5128 sport=25 flags=R seq=22
    win=512 rtt=408.2 ms
    len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=23
    win=5840 rtt=305.1 ms
    len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=24
    win=5840 rtt=305.1 ms
    len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=25
    win=5840 rtt=304.4 ms
    len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=26
    win=5840 rtt=303.9 ms
    len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=27
    win=5840 rtt=302.0 ms
    DUP! len=46 ip=216.40.250.211 ttl=255 id=5131 sport=25 flags=R seq=27
    win=512 rtt=403.6 ms
    len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=28
    win=5840 rtt=302.4 ms
    ^C
    --- mail2.zoneedit.com hping statistic ---
    29 packets tramitted, 32 packets received, -10% packet loss
    round-trip min/avg/max = 1.9/288.6/414.0 ms
    dm#

  4. Re: No route to host


    "Dom" wrote in message
    news:447bbbe6$0$14238$892e7fe2@authen.yellow.readf reenews.net...
    >> mail3.zoneedit.com.: No route to host

    >
    > Quite odd. Perhaps your ISP is screwing about. Try a tcp trace. Upon
    > performing my own testing, it seems that mail3 is not responding properly.
    > Though, I detected no icmp response when trying to reach mail3 and that is
    > what I would attribute the above error. Try resending and monitor for
    > icmp. Failing that, try sending to mail2.
    >
    >
    > dm# hping -STp 25 mail3.zoneedit.com
    > HPING mail3.zoneedit.com (vlan4 216.133.67.106): S set, 40 headers + 0
    > data bytes
    > hop=1 TTL 0 during transit from ip=195.16.87.33 name=r3.deadghost.com
    > hop=1 hoprtt=2.5 ms
    > hop=2 TTL 0 during transit from ip=194.126.235.1
    > name=rtr-1.peering.virt-ix.net
    > hop=2 hoprtt=192.9 ms
    > hop=3 TTL 0 during transit from ip=213.193.208.73
    > name=c1201-gateway.trueserver.nl
    > hop=3 hoprtt=188.3 ms
    > hop=4 TTL 0 during transit from ip=87.233.192.2
    > name=10ge-6-0.e600-2.ams5.true.nl
    > hop=4 hoprtt=197.7 ms
    > hop=5 TTL 0 during transit from ip=87.233.192.14
    > name=10ge-6-1.e600-1.ams1.true.nl
    > hop=5 hoprtt=196.0 ms
    > hop=6 TTL 0 during transit from ip=87.233.192.22
    > name=10ge-6-0.e600-2.ams1.true.nl
    > hop=6 hoprtt=196.2 ms
    > hop=7 TTL 0 during transit from ip=213.193.235.158
    > name=wedare-gw.trueserver.nl
    > hop=7 hoprtt=194.1 ms
    > hop=8 TTL 0 during transit from ip=84.244.177.46
    > name=ge-1-1-0.ar3.ams.we-dare.net
    > hop=8 hoprtt=193.3 ms
    > hop=9 TTL 0 during transit from ip=195.69.144.124
    > name=te3-3.mpd01.ams03.atlas.cogentco.com
    > hop=9 hoprtt=465.5 ms
    > hop=10 TTL 0 during transit from ip=130.117.0.33
    > name=t2-0-0.core01.ams03.atlas.cogentco.com
    > hop=10 hoprtt=191.1 ms
    > hop=11 TTL 0 during transit from ip=130.117.1.170
    > name=p9-0.core02.jfk02.atlas.cogentco.com
    > hop=11 hoprtt=274.6 ms
    > hop=12 TTL 0 during transit from ip=66.28.4.13
    > name=p15-0.core01.jfk02.atlas.cogentco.com
    > hop=12 hoprtt=375.2 ms
    > hop=13 TTL 0 during transit from ip=66.28.4.178
    > name=p5-0.core01.bwi01.atlas.cogentco.com
    > hop=13 hoprtt=284.4 ms
    > hop=14 TTL 0 during transit from ip=38.112.18.18
    > name=balt.demarc.cogentco.com
    > hop=14 hoprtt=281.5 ms
    > hop=15 TTL 0 during transit from ip=38.112.72.1
    > name=core.38-112-72-1.balticore.net
    > hop=15 hoprtt=357.5 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4929 sport=25 flags=RA seq=1
    > win=512 rtt=29774.3 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4932 sport=25 flags=R seq=2
    > win=512 rtt=29773.0 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4936 sport=25 flags=R seq=3
    > win=512 rtt=29776.0 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4938 sport=25 flags=R seq=4
    > win=512 rtt=29787.8 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4940 sport=25 flags=R seq=5
    > win=512 rtt=29773.5 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4942 sport=25 flags=R seq=6
    > win=512 rtt=29776.4 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4944 sport=25 flags=R seq=7
    > win=512 rtt=29775.6 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4948 sport=25 flags=RA seq=8
    > win=512 rtt=29774.4 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4950 sport=25 flags=R seq=9
    > win=512 rtt=29773.1 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4952 sport=25 flags=R seq=10
    > win=512 rtt=29772.1 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4954 sport=25 flags=R seq=11
    > win=512 rtt=29774.8 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4957 sport=25 flags=R seq=12
    > win=512 rtt=29773.9 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4960 sport=25 flags=R seq=13
    > win=512 rtt=29773.0 ms
    > DUP! len=46 ip=216.133.67.106 ttl=255 id=4963 sport=25 flags=R seq=14
    > win=512 rtt=29775.5 ms
    > len=46 ip=216.133.67.106 ttl=255 id=4966 sport=25 flags=R seq=15 win=512
    > rtt=29774.8 ms
    > len=46 ip=216.133.67.106 ttl=255 id=4968 sport=25 flags=R seq=16 win=512
    > rtt=29773.4 ms
    > len=46 ip=216.133.67.106 ttl=255 id=4973 sport=25 flags=R seq=17 win=512
    > rtt=29776.6 ms
    > len=46 ip=216.133.67.106 ttl=255 id=4975 sport=25 flags=R seq=18 win=512
    > rtt=29775.2 ms
    > len=46 ip=216.133.67.106 ttl=255 id=4978 sport=25 flags=R seq=19 win=512
    > rtt=29774.4 ms
    > len=46 ip=216.133.67.106 ttl=255 id=4981 sport=25 flags=R seq=20 win=512
    > rtt=29777.1 ms
    > len=46 ip=216.133.67.106 ttl=255 id=4985 sport=25 flags=RA seq=21 win=512
    > rtt=29775.7 ms
    > len=46 ip=216.133.67.106 ttl=255 id=4987 sport=25 flags=R seq=22 win=512
    > rtt=29774.8 ms
    > len=46 ip=216.133.67.106 ttl=255 id=4991 sport=25 flags=R seq=23 win=512
    > rtt=29773.5 ms
    > len=46 ip=216.133.67.106 ttl=255 id=4993 sport=25 flags=R seq=24 win=512
    > rtt=29776.4 ms
    > len=46 ip=216.133.67.106 ttl=255 id=4997 sport=25 flags=R seq=25 win=512
    > rtt=29775.4 ms
    > len=46 ip=216.133.67.106 ttl=255 id=5001 sport=25 flags=R seq=26 win=512
    > rtt=29774.6 ms
    > len=46 ip=216.133.67.106 ttl=255 id=5003 sport=25 flags=R seq=27 win=512
    > rtt=29773.3 ms
    > len=46 ip=216.133.67.106 ttl=255 id=5006 sport=25 flags=R seq=28 win=512
    > rtt=29772.4 ms
    > len=46 ip=216.133.67.106 ttl=255 id=5011 sport=25 flags=R seq=29 win=512
    > rtt=29775.1 ms
    > len=46 ip=216.133.67.106 ttl=255 id=5013 sport=25 flags=R seq=30 win=512
    > rtt=29774.1 ms
    > len=46 ip=216.133.67.106 ttl=255 id=5015 sport=25 flags=R seq=31 win=512
    > rtt=29772.7 ms
    > len=46 ip=216.133.67.106 ttl=255 id=5019 sport=25 flags=R seq=32 win=512
    > rtt=29775.7 ms
    > len=46 ip=216.133.67.106 ttl=255 id=5022 sport=25 flags=R seq=33 win=512
    > rtt=29774.5 ms
    > len=46 ip=216.133.67.106 ttl=255 id=5025 sport=25 flags=R seq=34 win=512
    > rtt=29781.4 ms
    > len=46 ip=216.133.67.106 ttl=255 id=5028 sport=25 flags=RA seq=35 win=512
    > rtt=29772.7 ms
    > len=46 ip=216.133.67.106 ttl=255 id=5030 sport=25 flags=R seq=36 win=512
    > rtt=29775.1 ms
    > ^C
    > --- mail3.zoneedit.com hping statistic ---
    > 66 packets tramitted, 51 packets received, 23% packet loss
    > round-trip min/avg/max = 2.5/21088.1/29787.8 ms
    > dm# host zoneedit.com
    > zoneedit.com has address 69.72.176.180
    > zoneedit.com has address 69.72.176.188
    > zoneedit.com mail is handled by 0 mail3.zoneedit.com.
    > zoneedit.com mail is handled by 0 mail2.zoneedit.com.
    > dm# hping -STp 25 mail2.zoneedit.com
    > HPING mail2.zoneedit.com (vlan4 216.40.250.211): S set, 40 headers + 0
    > data bytes
    > hop=1 TTL 0 during transit from ip=195.16.87.33 name=r3.deadghost.com
    > hop=1 hoprtt=1.9 ms
    > hop=2 TTL 0 during transit from ip=194.126.235.1
    > name=rtr-1.peering.virt-ix.net
    > hop=2 hoprtt=231.4 ms
    > hop=3 TTL 0 during transit from ip=213.193.208.73
    > name=c1201-gateway.trueserver.nl
    > hop=3 hoprtt=248.8 ms
    > hop=4 TTL 0 during transit from ip=87.233.192.2
    > name=10ge-6-0.e600-2.ams5.true.nl
    > hop=4 hoprtt=196.6 ms
    > hop=5 TTL 0 during transit from ip=87.233.192.14
    > name=10ge-6-1.e600-1.ams1.true.nl
    > hop=5 hoprtt=205.0 ms
    > hop=6 TTL 0 during transit from ip=87.233.192.22
    > name=10ge-6-0.e600-2.ams1.true.nl
    > hop=6 hoprtt=197.4 ms
    > hop=7 TTL 0 during transit from ip=213.193.235.158
    > name=wedare-gw.trueserver.nl
    > hop=7 hoprtt=194.7 ms
    > hop=8 TTL 0 during transit from ip=84.244.177.46
    > name=ge-1-1-0.ar3.ams.we-dare.net
    > hop=8 hoprtt=196.6 ms
    > hop=9 TTL 0 during transit from ip=195.69.144.122
    > name=ge-5-1-0.mpr3.ams1.nl.above.net
    > hop=9 hoprtt=192.7 ms
    > hop=10 TTL 0 during transit from ip=64.125.27.222
    > name=64.125.27.222.available.above.net
    > hop=10 hoprtt=200.6 ms
    > hop=11 TTL 0 during transit from ip=64.125.27.165
    > name=so-7-0-0.cr2.dca2.us.above.net
    > hop=11 hoprtt=325.6 ms
    > hop=12 TTL 0 during transit from ip=64.125.29.169
    > name=so-3-0-0.cr2.dfw2.us.above.net
    > hop=12 hoprtt=330.4 ms
    > hop=13 TTL 0 during transit from ip=64.125.29.17
    > name=so-4-1-0.mpr2.iah1.us.above.net
    > hop=13 hoprtt=348.0 ms
    > hop=14 TTL 0 during transit from ip=216.200.251.26
    > name=289.ge-3-2-1.mpr1.iah1.us.above.net
    > hop=14 hoprtt=399.9 ms
    > hop=15 TTL 0 during transit from ip=207.218.245.29
    > name=ivhou-207-218-245-29.ev1.net
    > hop=15 hoprtt=305.9 ms
    > hop=16 TTL 0 during transit from ip=207.218.245.126
    > name=ivhou-207-218-245-126.ev1.net
    > hop=16 hoprtt=344.8 ms
    > len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=16 win=5840
    > rtt=393.6 ms
    > len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=17 win=5840
    > rtt=304.3 ms
    > DUP! len=46 ip=216.40.250.211 ttl=255 id=5122 sport=25 flags=R seq=17
    > win=512 rtt=414.0 ms
    > len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=18 win=5840
    > rtt=304.8 ms
    > len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=19 win=5840
    > rtt=300.2 ms
    > len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=20 win=5840
    > rtt=299.9 ms
    > len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=21 win=5840
    > rtt=354.3 ms
    > len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=22 win=5840
    > rtt=308.0 ms
    > DUP! len=46 ip=216.40.250.211 ttl=255 id=5128 sport=25 flags=R seq=22
    > win=512 rtt=408.2 ms
    > len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=23 win=5840
    > rtt=305.1 ms
    > len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=24 win=5840
    > rtt=305.1 ms
    > len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=25 win=5840
    > rtt=304.4 ms
    > len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=26 win=5840
    > rtt=303.9 ms
    > len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=27 win=5840
    > rtt=302.0 ms
    > DUP! len=46 ip=216.40.250.211 ttl=255 id=5131 sport=25 flags=R seq=27
    > win=512 rtt=403.6 ms
    > len=46 ip=216.40.250.211 ttl=48 DF id=0 sport=25 flags=SA seq=28 win=5840
    > rtt=302.4 ms
    > ^C
    > --- mail2.zoneedit.com hping statistic ---
    > 29 packets tramitted, 32 packets received, -10% packet loss
    > round-trip min/avg/max = 1.9/288.6/414.0 ms
    > dm#


    Solved...

    Every where i had read it poibted me to DNS, sendmail and I was reading and
    reading and reading...

    Turns out the ISP blocked port 25.

    Unblocked now and works..



  5. Re: No route to host

    BP ?

    "Barry Margolin" wrote in message
    news:barmar-3F927A.12445329052006@comcast.dca.giganews.com...
    > In article
    > <447a9fa0$0$7888$5a62ac22@per-qv1-newsreader-01.iinet.net.au>,
    > "McHenry" wrote:
    >
    >> We have a simple network:
    >> a) One Linux server 192.168.1.1
    >> b) One Windows workstation 192.168.1.12
    >>
    >> Both access the internet via an ADSL connection: modem/router@
    >> 192.168.1.254.
    >>
    >> The server runs the apps but does not run a DNS server, DHCP is handled
    >> by
    >> the router.
    >>
    >> The Linux fax server should forward faxes received to an email address
    >> however this is not happening.
    >>
    >> I have tried to diagnose this problem however have gotten nowhere and am
    >> loath to start changing many setting in fear that I turn a relatively
    >> simple
    >> problem into a complex one.
    >>
    >> The following entry, and many others like it, are logged in
    >> /var/log/maillog
    >>
    >> May 29 13:31:52 declan sendmail[6116]: k4RBqD69004136:
    >> to=username@ourdomain.com.au,
    >> ctladdr=
    >> (78/78), delay=1+17:39:39, xdelay=00:00:00, mailer=esmtp, pri=3943029,
    >> relay=mail3.zoneedit.com., dsn=4.0.0, stat=Deferred: mail3.zoneedit.com.:
    >> No
    >> route to host
    >>
    >> Our domain name "ourdomain.com.au" is hosted by zoneedit.com who forward
    >> emails received to this domain to the ISP email accounts.
    >>
    >> I understand from my research that this is not a sendmail problem but
    >> simply
    >> a DNS problem however it intrigues me that the server has associated
    >> ourdomain.com.au with zoneedit.com which implies to me the links are
    >> being
    >> made correctly.

    >
    > Why do you think it's a DNS problem?
    >
    > What happens if you do: telnet mail3.zoneedit.com 25
    >
    > If there's a firewall somewhere blocking port 25, that would result in
    > "No route to host".
    >
    > --
    > Barry Margolin, barmar@alum.mit.edu
    > Arlington, MA
    > *** PLEASE post questions in newsgroups, not directly to me ***
    > *** PLEASE don't copy me on replies, I'll read them in the group ***




+ Reply to Thread