Help?Quote:
[4/8/2011 9:01:01 PM] Failed to get server stats: ConnectivityProblem -- TIMEOUT!
Already allowed through firewall. Also uninstalled a few times already/:shrug:
Printable View
Help?Quote:
[4/8/2011 9:01:01 PM] Failed to get server stats: ConnectivityProblem -- TIMEOUT!
Already allowed through firewall. Also uninstalled a few times already/:shrug:
Hmm...MJ12 uses port 80 which is no different than any other HTTP traffic so it should be passing through. That error message appears sometimes for me too because my whole connection is being used up so the stats update is "crowded out" so-to-speak. Do you mean the whole node can't connect or just that error message?
It won't even log in.
Same situation with my other computer.
When did this begin to happen? Do you remember installing any Windows/AV/firewall updates around that time?
Maybe related to this? http://www.majestic12.co.uk/forum/vi...363&highlight=
That said I am getting buckets OK just now. Not one of those wrong computer time and date issues is it
If I understand right lkiller's problem is he can't not only get buckets but also can't log in under the personal tab in options menu. My best bet would be some setting in the firewall.
Try this: Click Start then click the RUN button. Type in cmd.exe and hit enter. In the command window type: tracert 195.191.106.74
That IP above is the MJ12 registration server so the trace route command will let you know if you're successfully reaching it or not. Post your results here(you can edit out your IP address if you'd like).
Sorry for the late reply.
Quote:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\PoonFamily>tracert 195.191.106.74
Tracing route to aston74.majestic12.co.uk [195.191.106.74]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms home [192.168.1.254]
2 11 ms 11 ms 108 ms adsl-68-123-235-254.dsl.irvnca.pacbell.net [68.1
23.235.254]
3 50 ms 11 ms 11 ms 67.114.50.194
4 21 ms 13 ms 11 ms 151.164.102.178
5 13 ms 12 ms 13 ms la2ca02jt.ip.att.net [12.123.30.133]
6 45 ms 17 ms 35 ms 0.xe-4-3-0.BR3.LAX15.ALTER.NET [204.255.168.133]
7 28 ms 30 ms 35 ms 0.ae3.XL4.LAX15.ALTER.NET [152.63.113.190]
8 83 ms 84 ms 84 ms 0.xe-3-2-0.IL1.DCA6.ALTER.NET [152.63.43.69]
9 84 ms 83 ms 84 ms 0.ge-1-2-0.IL1.DCA4.ALTER.NET [152.63.43.78]
10 174 ms 166 ms 169 ms ge-0-1-0.XT1.LND9.ALTER.NET [146.188.14.169]
11 168 ms 166 ms 167 ms POS2-0.CR1.MAN3.ALTER.NET [158.43.253.186]
12 168 ms 206 ms 168 ms POS6-0.CR1.BHX2.ALTER.NET [158.43.253.158]
13 171 ms 223 ms 176 ms POS0-0-0.GW2.BHX2.ALTER.NET [158.43.187.138]
14 166 ms 169 ms 165 ms 193.128.161.12
15 165 ms 165 ms 179 ms 195.191.106.17
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28
The good news is that it is not your firewall or router. It looks like the problem is either your ISP or on Alex's server end? I remember someone having this exact problem before due to the server blocking their IP range(if I remember correctly). I would open a thread on the Majestic 12 forum saying you can't reach the registration server and post that tracert log above.
I had a problem where my ISP blocked my MJ-12 traffic. Called them and they opened it again in a week.Quote:
Originally Posted by DeadlyFire
Alrighty, thanks DF! :)
No problem lkiller! :up: Has Alex responded to you about it? Have you tried to connect again recently with the same results?
Er forgot about this. Way too busy these days.
On the bright side, I just got my U-verse connection. Hope I can get everything sorted out before they enforce the cap starting on May. :D
Ah - damn caps :shakes: Is U-verse by AT&T?