Unknown Failure
#1
Posted 30 September 2014 - 11:53 AM
#2
Posted 30 September 2014 - 12:05 PM
On the east coast in WV. I can connect sometime then get booted, sometimes I can't connect at all. Other time I can log in and then it disconnects.
Not my internet connection for once.
was fine before about 12-1pm EST.
Edited by Bigbacon, 30 September 2014 - 12:06 PM.
#3
Posted 30 September 2014 - 01:31 PM
-disconnects from the mechbay "connection to server was lost"
-disconnects while in game "server connection was lost"
-cannot change load outs on mechs "failure to save changes"\
-2 to 4 minute wait on connecting screen
-"unknown error" during login
-high ping during game play
#4
Posted 30 September 2014 - 01:43 PM
Subject heading "Connection Errors"
Your location
Trace Route:
- Press Windows Key + R
- Type CMD
- Click OK
- In the Command Prompt, type: tracert 192.99.109.129
- Take a screenshot of the results and attach it to your reply.
Ping test:
- Press Windows Key + R
- Type CMD
- Click OK
- In the Command Prompt, type: ping -n 100 192.99.109.129
- Take a screenshot of the results attach it to your reply.
#5
Posted 30 September 2014 - 01:44 PM
I will do this now i'm still having this issue. My internet is usually sort of slow between 4pm and 10pm EST but I can usually still play no problem just with a ping of 200-400.
lots of ping time outs..
pinging something else, like google.com, yields no real issues.
I added that as a screen shot as well for comparison. to the MWO IP I had a 35% loss to google.com 4%
Edit:
Support email sent.
Edited by Bigbacon, 30 September 2014 - 01:58 PM.
#6
Posted 30 September 2014 - 02:01 PM
#7
Posted 30 September 2014 - 02:27 PM
If you continue to experience this issue, please contact your local ISP to determine whether they are experiencing any known issues with services in your area. If they show no issues and your connection problems persists, please follow the instructions in the post above.
#8
Posted 30 September 2014 - 02:38 PM
Ping statistics for 192.99.109.129:
Packets: Sent = 100, Received = 82, Lost = 18 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 92ms, Maximum = 129ms, Average = 98ms
Normal Ping for me is 65ms - 75ms in game, and i have see it around 150 today when i am able to get in game.
#9
Posted 30 September 2014 - 02:46 PM
Ping Test = Just kept repeating ; Request timed out
the Tace route was between 75 and 65 ms. Sorry couldn't get screen shot to work.
Edited by Invictus51, 30 September 2014 - 03:04 PM.
#10
Posted 30 September 2014 - 03:07 PM
I've been able to connect a few times but it takes at least 2 minutes. Lag in game is 80-180 and my lag is usually 40-55. I haven't crashed during gameplay though.
#11
Posted 30 September 2014 - 03:07 PM
can everyone else post who their ISP is and their connection type and maybe we can come up with an answer or at least maybe we can come up with something that is the same between all of us?
Edited by Bigbacon, 30 September 2014 - 03:07 PM.
#12
Posted 30 September 2014 - 03:16 PM
I have also created a ticket and submitted it.
Edited by Ramrod AI, 30 September 2014 - 03:17 PM.
#13
Posted 30 September 2014 - 04:25 PM
#14
Posted 30 September 2014 - 05:19 PM
here are the problem routers in my area.
10 23 ms 23 ms 23 ms ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.97]
11 96 ms 97 ms 94 ms if-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5]
12 * * * Request timed out.
13 77 ms 70 ms 78 ms if-2-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.1]
14 95 ms 94 ms * if-3-2.tcore2.NJY-Newark.as6453.net [216.6.87.10]
15 90 ms 87 ms 94 ms if-2-2.tcore1.NJY-Newark.as6453.net [66.198.70.1]
16 * 109 ms * 192.99.146.48
those "tcore" routers belong to a company called tatacommiunications
Edited by SoggyGorilla, 30 September 2014 - 05:23 PM.
#15
Posted 01 October 2014 - 08:58 AM
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 17 ms 10 ms 11 ms cpe-72-179-0-1.austin.res.rr.com [72.179.0.1]
3 21 ms 14 ms 11 ms cpe-72-179-0-1.austin.res.rr.com [72.179.0.1]
4 13 ms 13 ms 18 ms tge2-5.rdrktxaz02h.texas.rr.com [66.68.6.145]
5 12 ms 12 ms 11 ms tge0-11-0-32.ausxtxir02r.texas.rr.com [24.175.41
.26]
6 34 ms 19 ms 19 ms agg22.hstqtxl301r.texas.rr.com [24.175.41.48]
7 20 ms 22 ms 19 ms 107.14.19.94
8 22 ms 22 ms 23 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
9 24 ms 24 ms 27 ms ae1.pr1.dfw10.tbone.rr.com [107.14.17.234]
10 25 ms 20 ms 17 ms ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.
97]
11 64 ms 60 ms 62 ms if-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5
]
12 59 ms 52 ms 59 ms if-10-3.tcore1.AEQ-Ashburn.as6453.net [66.198.15
4.117]
13 * 65 ms 56 ms if-2-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.1
]
14 55 ms 58 ms 63 ms if-11-2.tcore2.NJY-Newark.as6453.net [216.6.87.1
38]
15 67 ms 59 ms 58 ms if-2-2.tcore1.NJY-Newark.as6453.net [66.198.70.1
]
16 89 ms * * 192.99.146.48
17 85 ms 81 ms 80 ms bhs-g2-6k.qc.ca [198.27.73.207]
18 83 ms 79 ms 80 ms 198.27.73.233
19 81 ms 79 ms 88 ms 192.99.109.129
Trace complete.
It appears that tatacommiunications has resolved the issue overnight.
thank god.
#16
Posted 01 October 2014 - 09:04 AM
thanks Alex for looking into it.
#17
Posted 02 October 2014 - 12:03 AM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users