

A Network Error Occurred
#61
Posted 05 March 2014 - 02:58 PM
#62
Posted 05 March 2014 - 10:48 PM
I think I'm going to download Wireshark and go through the motions with Plusnet, then forward that info to PGI to see if we can get a resolution. Hopefully this time I'll get something a little more involved than "Have you restarted your router". Maybe if enough of us do that it'll highlight a problem that's something more global.
#63
Posted 06 March 2014 - 05:48 AM
James DeGriz, on 05 March 2014 - 10:48 PM, said:
I think I'm going to download Wireshark and go through the motions with Plusnet, then forward that info to PGI to see if we can get a resolution. Hopefully this time I'll get something a little more involved than "Have you restarted your router". Maybe if enough of us do that it'll highlight a problem that's something more global.
Yea it'll be worthwhile. I'll finish going through stuff with Plusnet. I've got a ticket open with MWO too which I will keep going too.
#64
Posted 06 March 2014 - 12:49 PM
#65
Posted 08 March 2014 - 02:22 PM
#66
Posted 08 March 2014 - 05:52 PM
This is not a problem with our internet connection. This is a problem with teh MWO servers.
If we all send in support questions, they might actualy fix it.
I just spent IRL money on this game. After the first day i cant log on to play again.
#67
Posted 08 March 2014 - 07:15 PM
Busterguy, on 08 March 2014 - 05:52 PM, said:
This is not a problem with our internet connection. This is a problem with teh MWO servers.
If we all send in support questions, they might actualy fix it.
I just spent IRL money on this game. After the first day i cant log on to play again.
Hey Busterguy,
While there is certainly a possible issue with the MWO servers, there are a few signs that point to this being a regional/Service Provider issue.
If the MWO servers, or even the peering point for the datacenter that they reside in, there would be more folks having connectivity issues. In this regard, the issue seems to be specific to Plus.net users, such as GingerPig. Even he is able to connect intermittently.
The more likely culprit is either some form of traffic throttling being done by Plus.net or by one of it's peers in between yourself and the MWO servers, or some other specific service provider issue.
Again, this is not to say that the MWO servers are in the clear either, but there just doesn't seem to be enough evidence to indicate that it's an issue.
One recommendation I would suggest, try manually assigning your DNS server to one of Google's (I use 8.8.8.8). It may not solve the issue but if it's as simple as your DNS server timing out during certain times of the day when attempting to resolve it will help you get around that.
#68
Posted 08 March 2014 - 08:06 PM
Amusing aside....I'm probably living within 50-100km of the servers. Think I'll have a word with my ISP.
Tracing route to relay-1.mwtactics.com [70.42.29.65]
over a maximum of 30 hops:
...
9 38 ms 14 ms 34 ms ae0-115.tor10.ip4.tinet.net [173.241.130.133]
10 32 ms 29 ms 29 ms xe-3-0-0.chi12.ip4.tinet.net [141.136.107.65]
11 182 ms 214 ms 124 ms as3549.ip4.tinet.net [213.200.66.58]
12 32 ms 34 ms 29 ms internap.gi1-0-11.asr1.yyz1.gblx.net [64.214.196
.26]
13 32 ms 29 ms 34 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.1
96]
14 31 ms 29 ms 34 ms relay-1.mwtactics.com [70.42.29.65]
Trace complete.
Tracing route to relay-1.mwtactics.com [70.42.29.65]
over a maximum of 30 hops:
...
9 28 ms 29 ms 29 ms ae0-115.tor10.ip4.tinet.net [173.241.130.133]
10 67 ms 49 ms 34 ms xe-3-0-0.chi12.ip4.tinet.net [141.136.107.65]
11 33 ms 24 ms 29 ms as3549.ip4.tinet.net [213.200.66.58]
12 32 ms 29 ms 34 ms internap.gi1-0-11.asr1.yyz1.gblx.net [64.214.196
.26]
13 35 ms 29 ms 39 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.1
96]
14 46 ms 39 ms 29 ms relay-1.mwtactics.com [70.42.29.65]
Trace complete.
Tracing route to relay-1.mwtactics.com [70.42.29.65]
over a maximum of 30 hops:
...
9 23 ms 19 ms 29 ms ae0-115.tor10.ip4.tinet.net [173.241.130.133]
10 33 ms 74 ms 34 ms xe-3-0-0.chi12.ip4.tinet.net [141.136.107.65]
11 52 ms 119 ms 24 ms as3549.ip4.tinet.net [213.200.66.58]
12 38 ms 29 ms 34 ms internap.gi1-0-11.asr1.yyz1.gblx.net [64.214.196
.26]
13 41 ms 39 ms 34 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.1
96]
14 35 ms 39 ms 34 ms relay-1.mwtactics.com [70.42.29.65]
Trace complete.
Edited by darqsyde, 08 March 2014 - 09:00 PM.
#69
Posted 09 March 2014 - 02:23 AM
#70
Posted 09 March 2014 - 04:48 AM
BeyondBounds, on 09 March 2014 - 02:23 AM, said:
I have effectively sent in two requests for the game to be prioritised with plus.net hopefully they'll action it this week.
#71
Posted 09 March 2014 - 04:59 AM
Annoyingly i had 90 days of premium time saved up which i activated the weekend before all this happened and now i cant log in to use it.
#72
Posted 09 March 2014 - 09:44 AM
#73
Posted 09 March 2014 - 10:51 AM
My ticket came back with basically "theres nothing wrong with your connection" when i didnt even say I had a connection issue. I told them that the wireshark trace I sent showed that MWO traffic was treated as lowest priority
I have no idea how far traffic tagging goes through the backbone as my tracerts show that alls fine till it reaches a border in the states and then either a huge delay or no futher at all
I have also seen my premium time burn away as I can't play for blocks of sometimes 18 hrs or so and its really pissing me off. Occasionaly rebooting my router puts me on a different backbone border point during the day but night time it makes no difference
#74
Posted 09 March 2014 - 09:30 PM
DragonsFire, on 08 March 2014 - 07:15 PM, said:
One recommendation I would suggest, try manually assigning your DNS server to one of Google's (I use 8.8.8.8). It may not solve the issue but if it's as simple as your DNS server timing out during certain times of the day when attempting to resolve it will help you get around that.
From what I've seen it's more likely to do with routing than it is to do with name resolution.
#75
Posted 10 March 2014 - 08:45 AM
James DeGriz, on 09 March 2014 - 09:30 PM, said:
From what I've seen it's more likely to do with routing than it is to do with name resolution.
Yeah, based on some of the posts above, it seems to be a routing/packet priority issue happening. I just threw the DNS solution out there as that has impacted users before and if they aren't a Plus.net customer they might be seeing something different.
Darqsyde's routing is also completely hosed for being that close physically to the servers, there is some very odd peering going on, with a pretty large latency increase on that 1 hop in particular, just getting to the servers.
#76
Posted 10 March 2014 - 02:08 PM
**** this.
#78
Posted 10 March 2014 - 03:03 PM
Edited by GingerPig, 10 March 2014 - 03:05 PM.
#79
Posted 11 March 2014 - 12:29 PM
#80
Posted 11 March 2014 - 01:05 PM
Go to your Internet Explorer (yes, IE) and go to settings and from the general settings press ''Use default'' or something (under the homepage url). It has worked on several games for me, and apparently for other MWO players.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users