telnet and traceroute use very differing methods of reaching the destination. It is not uncommon to be able to traceroute to a dest, but not telnet, or to be able to telnet, but not traceroute. Typically, if you can telnet but not traceroute, then someone is blocking the traceroute via a firewall rule. There's another command called tracepath which sometimes works better than traceroute. The connection problem your seeing might be due to a routing issue, however, that seems contrary to what traceroute is reporting. Do you have a firewall up? Does the remote host? It's possible that they're blocking a range of IP addresses, or you're blocking access to them. David [EMAIL PROTECTED] wrote: > Dear All, > > I receive some strange problems lately, > my mailserver logs many CANT_MAKE_SMTP_CONNECTION.#4.4.1 > > So I took some domains from the logs and tried to examine the connection to > each domains. > What I did is I connect to internet using 2 connection, 1 my leased line > conn, and 1 other ISP. and then tried to traceroute and telnet to port 25. > > There are some sites where I CANT TRACEROUTE using both conn, so I suppose > the routing could be the problem, but from the ISP, I CAN TELNET to the > site's port 25, in the other hand, I CAN'T TELNET using my own mailserver > (leased line). It's strange to me. > > From ISP side, if it cannot traceroute, why it can telnet? > > Anyone can help me? > > Thanks! > > Chrisanthy -- A Panagram To be or not to be: that is the question, whether tis nobler in the mind to suffer the slings and arrows of outrageous fortune. In one of the Bard's best-thought-of tragedies, our insistent hero, Hamlet, queries on two fronts about how life turns rotten.
