Email problems
- Thread starter bryanh
- Start date
yash, I case you are reading this forum
Here is some more information that might help.
The last two hops in a tracert from me to you are as follows:
12 63 ms 58 ms 60 ms 69.28.191.90
13 61 ms 58 ms 59 ms mail.m****here.biz [204.14.107.1]
I can connect a web browser to 69.28.191.90 - It asks for a password, but I can connect.
The next hop is your mail server. I cannot connect to it (with the same browser on the same machine). Therefore it is without a doubt a problem between hop 12 and 13. Can your NOC use this information or as a company have you just given up and I should just move on?
Thank you
Here is some more information that might help.
The last two hops in a tracert from me to you are as follows:
12 63 ms 58 ms 60 ms 69.28.191.90
13 61 ms 58 ms 59 ms mail.m****here.biz [204.14.107.1]
I can connect a web browser to 69.28.191.90 - It asks for a password, but I can connect.
The next hop is your mail server. I cannot connect to it (with the same browser on the same machine). Therefore it is without a doubt a problem between hop 12 and 13. Can your NOC use this information or as a company have you just given up and I should just move on?
Thank you
Are you suggesting that Jodo cannot be at fault here? For example, perhaps they are blocking a group of IP's on their router when using TCP as the protocol (ICMP obviously works). My ISP's NOC has been trying to work with Jodo's "support" team but it would seem that the people they are dealing with "... are not very network experienced".
In the end, this has to be a router/firewall issue. There is no other explaination. Ping works, tracert works, I can telnet/http to other Jodo servers, and I was able to connect to the "old" mail server (in case you didn't know, the IP of the mail server changed last week, which is exactly when these problems started).
On a side note, are you always so unhelpful and rude. If you cannot contribute to the conversation, why do you even comment? You have already mentioned that you do not have this problem, but there are at least two people that do.
Thank you
In the end, this has to be a router/firewall issue. There is no other explaination. Ping works, tracert works, I can telnet/http to other Jodo servers, and I was able to connect to the "old" mail server (in case you didn't know, the IP of the mail server changed last week, which is exactly when these problems started).
On a side note, are you always so unhelpful and rude. If you cannot contribute to the conversation, why do you even comment? You have already mentioned that you do not have this problem, but there are at least two people that do.
Thank you
SubSpace
Bass
I'm not suggesting anything of the sort.
You were suggesting it cannot possibly be your ISP's or your own fault because of your traceroute. I was merely pointing out that your conclusion was flawed.
Yes, it is possible that somewhere some IP range is being blocked. In that case I suggest you give JodoHost your exact home IP and it should be easy to check firewall and routing tables..
It's also still possible that your ISP is messing things up. The largest cable modem provider in the Netherlands took 3 weeks to realise the problem was at their side, and another 5 weeks to fix it..
You were suggesting it cannot possibly be your ISP's or your own fault because of your traceroute. I was merely pointing out that your conclusion was flawed.
Yes, it is possible that somewhere some IP range is being blocked. In that case I suggest you give JodoHost your exact home IP and it should be easy to check firewall and routing tables..
It's also still possible that your ISP is messing things up. The largest cable modem provider in the Netherlands took 3 weeks to realise the problem was at their side, and another 5 weeks to fix it..
SenseiSimpleton
Perch
i've been having the same problem connecting to email, as well as MSSQL2 for a couple of days now, including trying to go to horde... can't ping it... all other sites and everything works fine.
I'm in texas on time warner's road runner... when i do traceroute, i see that it goes through LEVEL3 in dallas all the way to miami where it goes to another ISP, could there be any problem there? i doubt there's any connection.
In any case, i've contacted my ISP and they havent found any problem, and i connect to my emails hosted elsewhere on port 21, as well as 110 for smtp, as well as webmail OK, so it's not a firewall issue as far as i know...
here's a traceroute from the control panel:
would seem there's something wrong once it gets to the dns servers/ gateway from my ISP.. but they deny anything...
anyone else?
I'm in texas on time warner's road runner... when i do traceroute, i see that it goes through LEVEL3 in dallas all the way to miami where it goes to another ISP, could there be any problem there? i doubt there's any connection.
In any case, i've contacted my ISP and they havent found any problem, and i connect to my emails hosted elsewhere on port 21, as well as 110 for smtp, as well as webmail OK, so it's not a firewall issue as far as i know...
here's a traceroute from the control panel:
would seem there's something wrong once it gets to the dns servers/ gateway from my ISP.. but they deny anything...
anyone else?
Stephen said:
that's his IP. It looks like it's the traceroute from the hsphere control panel, so you're at the top
. (so probably not all that useful for diagnosing problems connecting in the other direction to the mail server...?) here's mine:
traceroute to 69.*.*.* (69.*.*.*), 30 hops max, 38 byte packets
1 69.28.191.90 (69.28.191.90) 0.593 ms 0.575 ms 0.446 ms
2 ge-0-1-0.407.ar2.MIA1.gblx.net (67.17.210.73) 0.490 ms 0.409 ms 0.623 ms
3 so1-3-0-2488M.ar1.DCA3.gblx.net (67.17.68.33) 29.613 ms 29.913 ms 29.663 ms
4 sl-st20-ash-13-0.sprintlink.net (144.232.8.17) 30.304 ms 30.420 ms 29.675 ms
5 sl-st21-ash-12-0.sprintlink.net (144.232.19.241) 29.840 ms 29.649 ms 29.861 ms
6 sl-bb26-rly-5-0.sprintlink.net (144.232.20.149) 31.585 ms 77.879 ms 63.580 ms
7 sl-bb25-chi-3-0.sprintlink.net (144.232.20.89) 57.081 ms 56.481 ms 56.807 ms
8 sl-bb20-chi-9-0.sprintlink.net (144.232.26.114) 56.812 ms 56.541 ms 57.103 ms
9 sl-st20-chi-12-0.sprintlink.net (144.232.8.219) 56.850 ms 56.518 ms 56.559 ms
10 sl-sbcint-4-0.sprintlink.net (144.223.241.58) 56.546 ms 56.405 ms 56.365 ms
11 bb2-p4-0.emhril.sbcglobal.net (151.164.42.138) 57.179 ms 57.693 ms 57.714 ms
12 bb1-p2-0.emhril.ameritech.net (151.164.191.113) 57.191 ms 57.139 ms 57.241 ms
13 151.164.240.195 (151.164.240.195) 58.429 ms 58.721 ms 58.770 ms
14 bb2-p13-0.sfldmi.ameritech.net (151.164.242.38) 66.058 ms 66.299 ms 66.069 ms
15 bb1-p14-0.sfldmi.ameritech.net (151.164.40.177) 66.147 ms 66.173 ms 66.070 ms
16 bb1-p3-0.lgtpmi.sbcglobal.net (151.164.40.101) 69.838 ms 69.800 ms 69.300 ms
17 dist1-vlan30.lgtpmi.ameritech.net (65.42.245.97) 69.475 ms 69.369 ms 69.368 ms
18 rback3-g1-0.lgtpmi.sbcglobal.net (65.42.245.230) 70.186 ms 69.964 ms 70.574 ms
19 * * *
20 * * *
21 * * *
well I just had my ISP tech in my house. The goal was to confirm that the problem was NOT with my PC config, or any other software on my machines. We connect the tech's laptop directly to the cable modem and guess what. He could not connect either.
So - good news - the problem is not in my home. Bad news, everybody says the problem is every body else (Jodo blames my ISP, my ISP says nothing is wrong on their network). If this is not resolved soon I am going to have to find a new web server as it has now been 8 days since I have been able to access my e-mail. I have over 10 megs of e-mail waiting.... This really stinks.
So - good news - the problem is not in my home. Bad news, everybody says the problem is every body else (Jodo blames my ISP, my ISP says nothing is wrong on their network). If this is not resolved soon I am going to have to find a new web server as it has now been 8 days since I have been able to access my e-mail. I have over 10 megs of e-mail waiting.... This really stinks.
