115 replies to this topic

[James DeGriz]

GingerPig, on 28 March 2014 - 03:22 PM, said:

I'm getting a normal ping when in game, just get booted off with the message "server connection lost" then try to log in and get "A network error occurred"

Have just seen this post, so will try this tomorrow. http://mwomercs.com/...or-on-plus-net/

I wouldn't bother. There is no way on this green earth that simply asking your local DHCP server (router for most of us) for a renewed IP lease is going to fix this problem. You could get around the problem completely by simply statically assigning your IP details.

I'm going to re-raise this with MWO Support. I've had all sorts of connection issues over the past couple of days, and looking around the rest of the forums a lot of us are experiencing similar problems regardless of geographical location and ISP.

[Nuk Chorris]

Well i'm another plus net user who is getting the 'Network Error' message. I'm in Northern Ireland and i use their Fibre Optic. I have no other issues with any other game which leads me to believe it's MWO thats to blame.

[James DeGriz]

One thing that is kinda positive. I'll be moving house in 6 weeks or so, and will likely be going with my other halfs ISP, Virgin on a 60MB fibre connection (as opposed to my current ADSL2+ 7MB one). Will be interesting to see if the problem follows me or if it's suddenly OK. At least then same computer on a different ISPs network might give some sort of hint as to what's going on.

Of course, I'd hope it'd be sorted by then, but the way things are going at the moment, that doesn't look terribly likely.

[darqsyde]

Following up my earlier post, I discovered that my router was dieing on me, probably overheating or some sort of memory leak.

With my new router I get rock solid connections*.

So, if you can, try a new router/modem. Perhaps it's borked like mine.

*I still have some lag spiking, but that's almost entirely ISP related, and the weird Toronto-Chicago-Toronto routing I get to take.

[James DeGriz]

Well last night I actually managed to get pings and tracerts to echo what I was experiencing in game. Bare in mind that I usually get pings around 105ms, I ran a tracert followed by a rolling ping and got this:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 15 ms 15 ms lo0-central10.pcl-ag06.plus.net [195.166.128.187
3 21 ms 15 ms 15 ms link-b-central10.pcl-gw02.plus.net [212.159.2.182]
4 15 ms 14 ms 14 ms xe-10-3-0.pcl-cr02.plus.net [212.159.0.214]
5 15 ms 16 ms 20 ms ae2.pcl-cr01.plus.net [195.166.129.6]
6 15 ms 18 ms 21 ms ae1.ptw-cr01.plus.net [195.166.129.0]
7 * 17 ms 16 ms te-3-4.car5.London1.Level3.net [217.163.45.181]
8 15 ms 15 ms 14 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]
9 23 ms 15 ms 15 ms ae-226-3602.edge3.London1.Level3.net [4.69.166.150]
10 82 ms 86 ms 80 ms gblx-level3-50g.London1.Level3.net [4.68.110.158]
11 379 ms 387 ms 340 ms INTERNAP.Gi1-0-11.asr1.YYZ1.gblx.net [64.214.196.26]
12 338 ms 348 ms 352 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
13 357 ms 358 ms 351 ms relay-1.mwtactics.com [70.42.29.65]

Then, I ran a rolling ping and go this:

Reply from 70.42.29.65: bytes=32 time=330ms TTL=46
Reply from 70.42.29.65: bytes=32 time=337ms TTL=46
Reply from 70.42.29.65: bytes=32 time=319ms TTL=46
Reply from 70.42.29.65: bytes=32 time=320ms TTL=46
Reply from 70.42.29.65: bytes=32 time=322ms TTL=46
Reply from 70.42.29.65: bytes=32 time=323ms TTL=46
Reply from 70.42.29.65: bytes=32 time=342ms TTL=46
Reply from 70.42.29.65: bytes=32 time=313ms TTL=46
Reply from 70.42.29.65: bytes=32 time=345ms TTL=46
Reply from 70.42.29.65: bytes=32 time=347ms TTL=46
Reply from 70.42.29.65: bytes=32 time=278ms TTL=46
Reply from 70.42.29.65: bytes=32 time=311ms TTL=46
Reply from 70.42.29.65: bytes=32 time=336ms TTL=46
Reply from 70.42.29.65: bytes=32 time=302ms TTL=46
Reply from 70.42.29.65: bytes=32 time=324ms TTL=46
Reply from 70.42.29.65: bytes=32 time=324ms TTL=46
Reply from 70.42.29.65: bytes=32 time=159ms TTL=49
Reply from 70.42.29.65: bytes=32 time=161ms TTL=49
Reply from 70.42.29.65: bytes=32 time=158ms TTL=49
Reply from 70.42.29.65: bytes=32 time=140ms TTL=49
Reply from 70.42.29.65: bytes=32 time=154ms TTL=49

Amazed at the sudden jump from 320ms to 150ms I ran another tracert:


Tracing route to relay-1.mwtactics.com [70.42.29.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 16 ms 15 ms 14 ms lo0-central10.pcl-ag07.plus.net [195.166.128.188
]
3 25 ms 15 ms 15 ms link-b-central10.pcl-gw02.plus.net [212.159.2.18
6]
4 15 ms 16 ms 14 ms xe-9-0-0.pcl-cr02.plus.net [212.159.0.218]
5 14 ms 14 ms 15 ms ae2.pcl-cr01.plus.net [195.166.129.6]
6 16 ms 15 ms 14 ms ae1.ptw-cr01.plus.net [195.166.129.0]
7 51 ms 220 ms 15 ms te-3-4.car5.London1.Level3.net [217.163.45.181]
8 15 ms 15 ms 15 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]
9 15 ms 14 ms 15 ms ae-226-3602.edge3.London1.Level3.net [4.69.166.150]
10 154 ms 68 ms 62 ms gblx-level3-50g.London1.Level3.net [4.68.110.158]
11 149 ms 153 ms 147 ms INTERNAP.Gi1-0-11.asr1.YYZ1.gblx.net [64.214.196.26]
12 136 ms 133 ms 133 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
13 151 ms 146 ms 142 ms relay-1.mwtactics.com [70.42.29.65]

Trace complete.

Basically it looks like the connection at the UK side of the transatlantic connection from the UK to mainland NA is what is up the Swanee. As this route is what all Plusnet connections are going to be routed through it explains why most of us Plusnet customers are experiencing this problem. It's odd that all this started happening when they did their maintenance back at the beginning of March!

Have included this in my support ticket with them.

Edited by James DeGriz, 01 April 2014 - 09:45 PM.

[DragonsFire]

James DeGriz, on 01 April 2014 - 09:43 PM, said:

<snip>

Is this happening during peak time? I agree that the hops you highlighted are definitely a problem area given that a London-London (hops 9 and 10) handoff should not have spike that high. Tough to say exactly what the issue is, and it sucks that it's hitting all Plusnet users.

[James DeGriz]

It's definitely worse at peak times (i.e. from about 7.30pm - 8pm BST weekday and weekend evenings) and tends to get worse as the evening progresses. By 10pm BST, pings of 1500 or so make the game virtually unplayable.

Compare that with early ish on a Saturday morning, and it's absolutely fine.

As I say though, I'll be moving house in a month or so and be on a fibre connection with a different ISP. Will be interesting to see what the performance is like with them, and of course, the route their network takes across the Atlantic.

[James DeGriz]

Just as an aside, possibly what sucks even more is the woeful support from MWO that I've received during this. Even when I showed the representative I've been dealing with those traceroutes, he was still insisting that changing my DNS server settings would improve the results.

[DragonsFire]

James DeGriz, on 03 April 2014 - 07:01 AM, said:

Just as an aside, possibly what sucks even more is the woeful support from MWO that I've received during this. Even when I showed the representative I've been dealing with those traceroutes, he was still insisting that changing my DNS server settings would improve the results.

I would advise caution on painting a whole support group based on the efforts of one or two individuals, that's generally not a fair course to take. They can also only do the best that they have to work with, and in this case, the only network related variable that they can assist with from a troubleshooting perspective is DNS.

There are also cases where changing your DNS to a public one such as Google (8.8.8.8), would actually be an effective measure, if the one you're currently using is not resolving MWO related stuff properly. That's not to say that's what the case is in this instance but again, they can't exactly alter your peering/routing, service provider, or even offered IP scope.

[James DeGriz]

DragonsFire, on 03 April 2014 - 11:22 AM, said:

I would advise caution on painting a whole support group based on the efforts of one or two individuals, that's generally not a fair course to take. They can also only do the best that they have to work with, and in this case, the only network related variable that they can assist with from a troubleshooting perspective is DNS.

There are also cases where changing your DNS to a public one such as Google (8.8.8.8), would actually be an effective measure, if the one you're currently using is not resolving MWO related stuff properly. That's not to say that's what the case is in this instance but again, they can't exactly alter your peering/routing, service provider, or even offered IP scope.

To be clear, I did say the support was woeful in this instance, so I wasn't by any means tarring the whole support team.

Secondly, DNS can only really speed up connections during web browsing because once a host as been resolved by an IP address, that address is locally cached and further connections to the host by name are resolved by it. Additionally, the tests we're doing here were direct to the IP, and so DNS would never be used.

I wasn't expecting them to be able to alter the routing, but I would expect them to be able to correctly identify the source of the fault and advise me accordingly, rather than banging on about something that clearly wasn't going to have any affect at all based on the information I'd provided. Advising a change of DNS on the basis of poor client connection, fine. Advising a change of DNS AFTER a tracert had shown there to be a problem with the routing, not so much, especially when I'd already made the change in an earlier step.

Edited by James DeGriz, 03 April 2014 - 09:29 PM.

[James DeGriz]

I believe I've had some success with this after posting my last lot of traceroutes to Plusnet and a couple of phone conversations with them during this week. They acknowledged where the problem was, but as it was outside of their network couldn't give me any guarantees they'd be able to do anything about it, but after a router reboot last night I can see the traffic is being routed differently.

Tracing route to relay-1.mwtactics.com [70.42.29.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 45 ms 20 ms lo0-central10.pcl-ag07.plus.net [195.166.128.188]
3 13 ms 13 ms 14 ms link-a-central10.pcl-gw01.plus.net [212.159.2.184]
4 13 ms 13 ms 30 ms xe-9-0-0.pcl-cr01.plus.net [212.159.0.216]
5 13 ms 13 ms 13 ms xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
6 22 ms 28 ms 20 ms vl-3201-ve-128.ebr2.London2.Level3.net [4.69.202.177]
7 20 ms 20 ms 20 ms ae-42-42.ebr1.Paris1.Level3.net [4.69.159.86]
8 20 ms 20 ms 20 ms ae-71-71.csw2.Paris1.Level3.net [4.69.161.82]
9 20 ms 20 ms 20 ms ae-2-70.edge3.Paris1.Level3.net [4.69.168.70]
10 20 ms 20 ms 20 ms global-crossing-xe-level3.paris1.level3.net [4.68.63.230]
11 104 ms 102 ms 103 ms INTERNAP.Gi1-0-11.asr1.YYZ1.gblx.net [64.214.196.26]
12 103 ms 120 ms 103 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
13 103 ms 103 ms 103 ms relay-1.mwtactics.com [70.42.29.65]

Trace complete.

Only had a couple of games last night, but all of them had rock solid pings of around 100-105.

Not sure this particular enemy mech is destroyed yet, but I think its CT is definitely on red

[Cold Soul]

I am having network error myself and only just managed to get forums back up after going through the piranha games link. In Australia there is a telecommunications industry ombudsman, I hope you have similar in UK cause it makes a huge difference in problem resolution. The ISP here hate you going to the ombo as it blackmarks them, but you get a speedy resloution, rather then a succession of lame arses going over the same ground again and again. My login tool showed red as in no server information and I was network errorred out of a drop.

Make waves and guys I wish you all a speedy resolution to your problem[local newspapers with stories like"Plusnet Sucks' may also light a fire under them]

[Cold Soul]

I am okay now, before going through the Piranha Games site to their MWO forums link. I could not get MWO pages to load for maybe 36hrs, they would just time out. After writing above post, started login/patcher tool and server status was green and I have logged in to game.
I am prob the most least internet savy dude playing this game, and it could just be coincidence , but give it a try
http://piranhagames.com/#GAMES

I have no explanation for how or why it got me up again, I will leave that for others, I really hope to see you guys online asap

[CH4CH]

Hello! I am in Thailand and I got the same problem as your guys. It just happened 4 days ago, at first the popup said like server is under maintenance, the followed with the network error (408). I had posed this issue at the announcement section and e-mail it to the support of PGI, but still don't have any response yet.

[MekBeth]

Reviving
Hey guys, getting network errors all the time this evening. Played this afternoon and everything worked fine. But now... Couldn't even log in.
Been pausing MWO for a year and just two weeks ago revived my account. Probably I missed the workaround for this: Anyone any ideas, how I can handle this issue? Is there a folder with tmp-data to erase or sth like that? pls help - thx.
Mek

[Ironicus]

MekBeth, on 01 October 2015 - 02:15 PM, said:

Reviving
Hey guys, getting network errors all the time this evening. Played this afternoon and everything worked fine. But now... Couldn't even log in.
Been pausing MWO for a year and just two weeks ago revived my account. Probably I missed the workaround for this: Anyone any ideas, how I can handle this issue? Is there a folder with tmp-data to erase or sth like that? pls help - thx.
Mek

Getting the same problem since beginning of the week myself, keep getting chucked out of games, won't even let the map load before back to mech lab.

I have tried everything except a fresh re-install which I am attempting now. I'm with Virgin Media, in Devon. But it was all working perfectly fine until the latest patch - the patch itself stopped working so I had to run the repair tool, since then no joy.

I'll post an update if the fresh install works.


***UPDATE***

Fresh reinstall worked for me.

Edited by Ironicus, 09 October 2015 - 10:47 AM.