I need some help in trying to get to the source of this problem. This the readout of the command traceroute risingstarmbc.com. I am unable to connect to this email address and I don't know how to resolve it. Could somebody give me instruction on who I can touch base with to get this fixed. There is nothing wrong with my email account. Have already checked that. Nothing wrong with ISP provider. [legraves11@Jehovah ~]$ traceroute risingstarmbc.com traceroute to risingstarmbc.com (204.10.137.200), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 0.184 ms 0.131 ms 0.080 ms 2 c-24-8-64-1.hsd1.co.comcast.net (24.8.64.1) 21.877 ms 22.800 ms 30.888 ms 3 te-8-2-ur06.aurora.co.denver.comcast.net (68.85.107.49) 15.280 ms 16.102 ms 16.069 ms 4 te-0-0-0-0-ar02.aurora.co.denver.comcast.net (68.86.103.37) 16.934 ms 16.921 ms 16.877 ms 5 he-3-9-0-0-cr01.denver.co.ibone.comcast.net (68.86.92.21) 24.427 ms * * 6 pos-2-7-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.54) 33.015 ms 32.134 ms 32.085 ms 7 pos-0-9-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.88.198) 32.873 ms 26.040 ms 26.124 ms 8 as7018-pe01.1950stemmons.tx.ibone.comcast.net (75.149.230.162) 26.123 ms 25.260 ms 25.535 ms 9 cr2.dlstx.ip.att.net (12.123.16.110) 68.047 ms 68.352 ms 68.378 ms 10 cr2.dvmco.ip.att.net (12.122.31.90) 66.818 ms 67.700 ms 77.363 ms 11 cr1.slkut.ip.att.net (12.122.30.25) 73.095 ms 73.039 ms 72.956 ms 12 cr2.slkut.ip.att.net (12.122.30.22) 73.773 ms 73.704 ms 73.739 ms 13 * cr2.sc1ca.ip.att.net (12.122.30.113) 69.787 ms 82.567 ms 14 12.123.155.69 (12.123.155.69) 67.570 ms 64.373 ms 64.488 ms 15 12.88.115.134 (12.88.115.134) 76.745 ms 75.159 ms 72.426 ms 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * [legraves11@Jehovah ~]$
On 10/03/2012 10:15 AM, Lawrence Graves wrote:
I need some help in trying to get to the source of this problem. This the readout of the command traceroute risingstarmbc.com. I am unable to connect to this email address and I don't know how to resolve it. Could somebody give me instruction on who I can touch base with to get this fixed. There is nothing wrong with my email account. Have already checked that. Nothing wrong with ISP provider.
traceroute output is meaningless in this context.
explain what you mean by "unable to connect to this email address".
On 10/02/2012 07:15:38 PM, Lawrence Graves wrote:
I need some help in trying to get to the source of this problem. This the readout of the command traceroute risingstarmbc.com. I am unable to connect to this email address and I don't know how to resolve it.
[snip]
First, what _exactly_is the symptom. All the traceroute shows is how to get to the site. Connecting with a browser proves that the site exists. Neither has any necessary connection with your problem.
On 10/02/2012 07:15 PM, Lawrence Graves wrote:
I need some help in trying to get to the source of this problem.
What problem? They filter ICMP requests, so traceroute doesn't work. That's not really a problem.
I am unable to connect to this email address and I don't know how to resolve it.
So what happens when you try?
Their web site has trouble in spots. It's likely that their IT staff is inexperienced. Try calling the office if you can't email them.
On 10/02/2012 07:15 PM, Lawrence Graves wrote:
14 12.123.155.69 (12.123.155.69) 67.570 ms 64.373 ms 64.488 ms 15 12.88.115.134 (12.88.115.134) 76.745 ms 75.159 ms 72.426 ms
Checking, both of those two IP addresses belong to att.net. There seems to be something wrong between 12.88.115.134 and wherever your traceroute would have gone next. And, judging by the results when I tried tracerouting, it would have been to risingstarmbc.com. If you're still having trouble, I'd check with att.net and see if they can help.
On 10/02/2012 07:30 PM, Geoffrey Leach wrote:
First, what _exactly_is the symptom. All the traceroute shows is how to get to the site. Connecting with a browser proves that the site exists. Neither has any necessary connection with your problem.
In this case I agree, especially as I had no problems getting there via traceroute. However, there are lots of cases where you can find out just where your connectivity issue (including packet loss) is located. Back when I did tech support for an ISP, I had callers do this type of thing all the time in tracking down problems.
On 10/02/2012 07:30 PM, Gordon Messmer wrote:
On 10/02/2012 07:15 PM, Lawrence Graves wrote:
I need some help in trying to get to the source of this problem.
What problem? They filter ICMP requests, so traceroute doesn't work. That's not really a problem.
Actually, traceroute uses UDP probe packets by default and more and more hosts filter them out. I have a workaround for that:
traceroute -I risingstarmbc.com
This uses ICMP Echo packets instead, which are more likely to get through. However, you either need to be root for that, or SUID on /bin /traceroute, which is what I did because I'm the only person using this machine; I'd not do it on a production box just on general principles. In fact, I have an alias for it in .bashrc:
alias tracert=traceroute -I
which works fine. (On a production box, I'd put the alias in root's .bashrc and use su -c to invoke it.)
On 10/03/2012 10:30 AM, Geoffrey Leach wrote:
On 10/02/2012 07:15:38 PM, Lawrence Graves wrote:
I need some help in trying to get to the source of this problem. This the readout of the command traceroute risingstarmbc.com. I am unable to connect to this email address and I don't know how to resolve it.
[snip]
First, what _exactly_is the symptom. All the traceroute shows is how to get to the site. Connecting with a browser proves that the site exists. Neither has any necessary connection with your problem.
FWIW, I rarely use "traceroute" these days since many routers now filter ICMP messages. Since the site being talked about is risingstarmbc.com and since the word "email" was used in the OP's message and since host returns....
[egreshko@meimei ~]$ host risingstarmbc.com risingstarmbc.com has address 204.10.137.200 risingstarmbc.com mail is handled by 20 mx11.hostrack.net. risingstarmbc.com mail is handled by 20 mx12.hostrack.net.risingstarmbc.com. risingstarmbc.com mail is handled by 20 mx13.hostrack.net. risingstarmbc.com mail is handled by 30 risingstarmbc.com.
I use tcptraceroute to check and get....
[egreshko@meimei ~]$ sudo tcptraceroute -n mx13.hostrack.net 25 traceroute to mx13.hostrack.net (204.10.142.245), 30 hops max, 60 byte packets 1 211.75.128.254 17.028 ms 17.153 ms 18.391 ms 2 168.95.229.6 17.571 ms 18.305 ms 18.261 ms 3 220.128.1.158 21.326 ms 22.501 ms 220.128.4.102 22.662 ms 4 220.128.7.153 71.588 ms 220.128.7.21 18.187 ms 220.128.7.153 71.947 ms 5 220.128.30.253 18.633 ms 220.128.6.81 18.601 ms 220.128.6.85 18.559 ms 6 211.72.108.205 147.272 ms 145.270 ms 211.72.108.193 147.468 ms 7 12.250.31.5 158.631 ms 160.829 ms 160.941 ms 8 12.122.137.182 165.511 ms 166.439 ms 166.166 ms 9 12.122.30.121 166.647 ms 165.911 ms 164.458 ms 10 12.123.155.5 160.948 ms 162.950 ms 161.006 ms 11 12.88.115.134 163.689 ms 164.018 ms 162.562 ms 12 204.10.142.245 <syn,ack> 163.922 ms 165.778 ms 165.622 ms
Same is true for all the MX hosts as well as (using the appropriate ports) for pop.risingstarmbc.com and imap.risingstarmbc.com.
sure, use dig to find the ip addr of the MX server for your targeted domain. next ping the ip, get it? next try to connect to mail port, eg, telnet IPADDR 25, get a connect?
make sense?
On Tue, Oct 2, 2012 at 7:15 PM, Lawrence Graves lgraves95@gmail.com wrote:
I need some help in trying to get to the source of this problem. This the readout of the command traceroute risingstarmbc.com. I am unable to connect to this email address and I don't know how to resolve it. Could somebody give me instruction on who I can touch base with to get this fixed. There is nothing wrong with my email account. Have already checked that. Nothing wrong with ISP provider. [legraves11@Jehovah ~]$ traceroute risingstarmbc.com traceroute to risingstarmbc.com (204.10.137.200), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 0.184 ms 0.131 ms 0.080 ms 2 c-24-8-64-1.hsd1.co.comcast.net (24.8.64.1) 21.877 ms 22.800 ms 30.888 ms 3 te-8-2-ur06.aurora.co.denver.comcast.net (68.85.107.49) 15.280 ms 16.102 ms 16.069 ms 4 te-0-0-0-0-ar02.aurora.co.denver.comcast.net (68.86.103.37) 16.934 ms 16.921 ms 16.877 ms 5 he-3-9-0-0-cr01.denver.co.ibone.comcast.net (68.86.92.21) 24.427 ms
6 pos-2-7-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.54) 33.015 ms 32.134 ms 32.085 ms 7 pos-0-9-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.88.198) 32.873 ms 26.040 ms 26.124 ms 8 as7018-pe01.1950stemmons.tx.ibone.comcast.net (75.149.230.162) 26.123 ms 25.260 ms 25.535 ms 9 cr2.dlstx.ip.att.net (12.123.16.110) 68.047 ms 68.352 ms 68.378 ms 10 cr2.dvmco.ip.att.net (12.122.31.90) 66.818 ms 67.700 ms 77.363 ms 11 cr1.slkut.ip.att.net (12.122.30.25) 73.095 ms 73.039 ms 72.956 ms 12 cr2.slkut.ip.att.net (12.122.30.22) 73.773 ms 73.704 ms 73.739 ms 13 * cr2.sc1ca.ip.att.net (12.122.30.113) 69.787 ms 82.567 ms 14 12.123.155.69 (12.123.155.69) 67.570 ms 64.373 ms 64.488 ms 15 12.88.115.134 (12.88.115.134) 76.745 ms 75.159 ms 72.426 ms 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * [legraves11@Jehovah ~]$
-- All things are workable but don't all things work. Prov. 3:5 & 6
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Oh, and one more point, if you dont have telnet, many dont anymore, find & download netcat, it'll work just fine...
hth, ...
On Tue, Oct 2, 2012 at 7:23 PM, Ed Greshko Ed.Greshko@greshko.com wrote:
On 10/03/2012 10:15 AM, Lawrence Graves wrote:
I need some help in trying to get to the source of this problem. This
the readout of the command traceroute risingstarmbc.com. I am unable to connect to this email address and I don't know how to resolve it. Could somebody give me instruction on who I can touch base with to get this fixed. There is nothing wrong with my email account. Have already checked that. Nothing wrong with ISP provider.
traceroute output is meaningless in this context.
explain what you mean by "unable to connect to this email address".
-- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -- Rick Cook, The Wizardry Compiled -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On Thu, 2012-10-04 at 08:25 -0700, Jack Craig wrote:
Oh, and one more point, if you dont have telnet, many dont anymore, find & download netcat, it'll work just fine.
It's only the telnet client that you'd use to test services, that's a simple installation. It's the telnet server that's a very bad idea (*) to have on a system.
* There's no encryption over a telnet link, so logon credentials can be seen by anybody snooping the network. To use a telnet server, you log into it, so username and password are going to be sent unencrypted. But a telnet client can be used to test various servers that you don't log into, so it's safe to use as long as you think about what you send.
-
Ed Greshko -
Geoffrey Leach -
Gordon Messmer -
Jack Craig -
Joe Zeff -
Lawrence E Graves -
Tim