Jump to content

A Network Error Occurred


115 replies to this topic

#1 nephilimUK

    Member

  • PipPip
  • Bridesmaid
  • Bridesmaid
  • 31 posts
  • LocationEssex, UK

Posted 25 February 2014 - 12:53 PM

I couldn't log in today pre patch and cant login post patch, same error ;

"A netowrk error occurred"

I can play other games fine, have used the repair tool and have rebooted my router. Pings & tracerts look dandy (but haven't pinged the MWO servers as I dont know address)

premium time burning away

meh

#2 James DeGriz

    Member

  • PipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 374 posts
  • LocationRainham, Kent UK

Posted 25 February 2014 - 01:10 PM

If it's any consolation, I'm in the UK too (Kent) and getting the same issue. Only came back a few days ago after a 6 month break and already wishing I hadn't.

Indeed. Meh.

#3 Ixis

    Member

  • PipPip
  • Bad Company
  • Bad Company
  • 36 posts
  • LocationUK

Posted 25 February 2014 - 02:52 PM

Well then that makes three of us Brits that can't log in to MWO,I've tried restarting my pc,running the repair tool and still nada.

#4 GingerPig

    Member

  • PipPipPip
  • The Defiant
  • The Defiant
  • 57 posts
  • LocationUK

Posted 26 February 2014 - 07:08 AM

BUMP! I'm now getting this issue... highly frustrating when there seems to be no fix

***UPDATE***

Have restarted router and computer several times.

Uninstalled and reinstalled MWO

Sent an email to support

Edited by GingerPig, 26 February 2014 - 10:33 AM.


#5 James DeGriz

    Member

  • PipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 374 posts
  • LocationRainham, Kent UK

Posted 26 February 2014 - 08:46 AM

I logged a call with support this morning, but yet to hear anything.

#6 James DeGriz

    Member

  • PipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 374 posts
  • LocationRainham, Kent UK

Posted 26 February 2014 - 12:02 PM

Well.. not sure what's gone on, but seems to be OK now, but the first line support I got was severely lacking.

My email to them was something along the lines of "Error message: 'a network error occurred'. Restarted PC, router and ran repair tool, but issue persists"

Their first response, "Please try restarting your computer and router".

Really?

#7 Shamous13

    Member

  • PipPipPipPipPipPipPip
  • 684 posts
  • LocationKitchener, Ont.

Posted 26 February 2014 - 12:06 PM

The first question i always ask is "have you turned on the monitor?" you would be surprised how many times this has fixed the problem ;)

#8 James DeGriz

    Member

  • PipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 374 posts
  • LocationRainham, Kent UK

Posted 26 February 2014 - 12:17 PM

You're right I would. Sending an email without the monitor switched on is quite a task.

Although, from the way my support request was handled, I'm not sure the guy answering it had his monitor switched on either.

#9 GingerPig

    Member

  • PipPipPip
  • The Defiant
  • The Defiant
  • 57 posts
  • LocationUK

Posted 26 February 2014 - 12:18 PM

I have had a reply from MWO Support, which is as follows...

"Hello GingerPig,
Let's try these steps to see if we can get you back in there.
Go to your start menu and follow this trail:
Start -> Control Panel -> Internet Options -> Advanced Tab -> Click Reset -> Click Reset again
Now close all the windows and try again. Does this resolve your issue? Please let me know if it works or not. "

Still no luck.

In the meantime I took the time to chat to my ISP and no problems there.

Edited by GingerPig, 26 February 2014 - 12:20 PM.


#10 Flank

    Rookie

  • Bad Company
  • 2 posts
  • LocationUK

Posted 26 February 2014 - 01:55 PM

Same problem here in Devon. No joy logging in today.

Plusnet is my provider should anyone want to start keeping track of such things.

All other games and services running smoothly on all my other machines... just seems to be MWO client that no longer speaks the language of the server.

Weirdness all round, I tells ya!

#11 GingerPig

    Member

  • PipPipPip
  • The Defiant
  • The Defiant
  • 57 posts
  • LocationUK

Posted 26 February 2014 - 02:05 PM

View PostFlank, on 26 February 2014 - 01:55 PM, said:

Same problem here in Devon. No joy logging in today.

Plusnet is my provider should anyone want to start keeping track of such things.

All other games and services running smoothly on all my other machines... just seems to be MWO client that no longer speaks the language of the server.

Weirdness all round, I tells ya!


I'm Dorset and Plusnet... I rung them this evening as well. Weird...

#12 martino2k6

    Member

  • PipPipPip
  • Philanthropist
  • 96 posts
  • LocationEurope

Posted 26 February 2014 - 02:10 PM

Same issue here, in England as well. Running the repair tool, rebooting (PC & router), several times each to no avail.

EDIT: PlusNet here as well. Thought it was BE, I guess I can no longer keep track with all the switches my landlord does.

Edited by martino2k6, 26 February 2014 - 02:13 PM.


#13 DragonsFire

    Member

  • PipPipPipPipPipPipPip
  • Wrath
  • Wrath
  • 655 posts

Posted 26 February 2014 - 02:11 PM

What is the traceroute looking like for you guys?? It would be interesting to see if you're perhaps crossing the same peer on the way to the server.

#14 GingerPig

    Member

  • PipPipPip
  • The Defiant
  • The Defiant
  • 57 posts
  • LocationUK

Posted 26 February 2014 - 02:15 PM

TraceRoute from Network-Tools.com
Hop (ms) (ms) (ms) IP Address Host name 1 1 0 0 8.9.232.73 8-1-18.ear1.dallas1.level3.net
2 103 103 103 4.69.145.254 vlan90.csw4.dallas1.level3.net
3 103 104 103 4.69.151.166 ae-92-92.ebr2.dallas1.level3.net
4 105 105 105 4.69.137.122 ae-3-3.ebr2.newyork1.level3.net
5 105 105 105 4.69.148.34 ae-62-62.csw1.newyork1.level3.net
6 103 103 103 4.69.134.65 ae-61-61.ebr1.newyork1.level3.net
7 103 103 104 4.69.137.65 ae-41-41.ebr2.london1.level3.net
8 103 103 103 4.69.153.142 ae-59-224.csw2.london1.level3.net
9 105 105 108 4.69.139.102 ae-25-52.car5.london1.level3.net
10 103 103 103 217.163.45.182 plusnet-tec.car5.london1.level3.net
11 111 111 113 195.166.129.1 ae1.pcl-cr01.plus.net
12 103 104 135 195.166.129.7 ae2.pcl-cr02.plus.net
13 111 111 111 212.159.0.195 te8-1.pcl-gw02.plus.net
14 124 118 131 212.159.2.163 link-b-central10.pcl-ag01.plus.net
15 Timed out Timed out Timed out
-

16 Timed out Timed out Timed out -
17 Timed out
Timed out Timed out -
18 Timed out Timed out Timed out -
Trace aborted.

Edited by GingerPig, 26 February 2014 - 02:18 PM.


#15 DragonsFire

    Member

  • PipPipPipPipPipPipPip
  • Wrath
  • Wrath
  • 655 posts

Posted 26 February 2014 - 02:22 PM

View PostGingerPig, on 26 February 2014 - 02:15 PM, said:

TraceRoute from Network-Tools.com
Hop (ms) (ms) (ms) IP Address Host name 1 1 0 0 8.9.232.73 8-1-18.ear1.dallas1.level3.net
2 103 103 103 4.69.145.254 vlan90.csw4.dallas1.level3.net
3 103 104 103 4.69.151.166 ae-92-92.ebr2.dallas1.level3.net
4 105 105 105 4.69.137.122 ae-3-3.ebr2.newyork1.level3.net
5 105 105 105 4.69.148.34 ae-62-62.csw1.newyork1.level3.net
6 103 103 103 4.69.134.65 ae-61-61.ebr1.newyork1.level3.net
7 103 103 104 4.69.137.65 ae-41-41.ebr2.london1.level3.net
8 103 103 103 4.69.153.142 ae-59-224.csw2.london1.level3.net
9 105 105 108 4.69.139.102 ae-25-52.car5.london1.level3.net
10 103 103 103 217.163.45.182 plusnet-tec.car5.london1.level3.net
11 111 111 113 195.166.129.1 ae1.pcl-cr01.plus.net
12 103 104 135 195.166.129.7 ae2.pcl-cr02.plus.net
13 111 111 111 212.159.0.195 te8-1.pcl-gw02.plus.net
14 124 118 131 212.159.2.163 link-b-central10.pcl-ag01.plus.net
15 Timed out Timed out Timed out
-

16 Timed out Timed out Timed out -
17 Timed out
Timed out Timed out -
18 Timed out Timed out Timed out -
Trace aborted.



Ginger, what's the IP you're tracing to? You can use this (70.42.29.65) if you aren't already. Also, it would be better to run the trace from your desktop as it would be a more accurate reflection of your routing to the server.

#16 martino2k6

    Member

  • PipPipPip
  • Philanthropist
  • 96 posts
  • LocationEurope

Posted 26 February 2014 - 02:30 PM

View PostDragonsFire, on 26 February 2014 - 02:22 PM, said:



Ginger, what's the IP you're tracing to? You can use this (70.42.29.65) if you aren't already. Also, it would be better to run the trace from your desktop as it would be a more accurate reflection of your routing to the server.

.65 is for MW Tactics, apparently. The MWOClient.exe iis connecting to 70.42.29.74. Anyway, here is mine:

C:\WINDOWS\system32>tracert 70.42.29.74

Tracing route to 70.42.29.74 over a maximum of 30 hops

1 50 ms 97 ms 98 ms dsldevice.lan [192.168.1.254]
2 11 ms 10 ms 10 ms lo0-central10.ptw-ag03.plus.net [195.166.128.197]
3 10 ms 9 ms 10 ms link-a-central10.ptw-gw01.plus.net [212.159.2.152]
4 11 ms 10 ms 10 ms xe-4-3-0.ptw-cr01.plus.net [212.159.0.244]
5 14 ms 12 ms 12 ms te-4-2.car5.London1.Level3.net [217.163.45.249]

6 12 ms 9 ms 12 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]

7 39 ms 10 ms 10 ms ae-228-3604.edge3.London1.Level3.net [4.69.166.158]
8 10 ms 10 ms 10 ms gblx-level3-50g.London1.Level3.net [4.68.110.158]
9 104 ms 105 ms 103 ms INTERNAP.Gi1-0-11.asr1.YYZ1.gblx.net [64.214.196.26]
10 93 ms 92 ms 94 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
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 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


#17 GingerPig

    Member

  • PipPipPip
  • The Defiant
  • The Defiant
  • 57 posts
  • LocationUK

Posted 26 February 2014 - 02:30 PM

C:\Users\GingerPig>tracert 70.42.29.65

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

1 11 ms 99 ms 100 ms dsldevice.lan [192.168.1.254]

2 30 ms 30 ms 28 ms lo0-central10.pcl-ag01.plus.net [195.166.128.182]

3 30 ms 29 ms 29 ms link-b-central10.pcl-gw02.plus.net [212.159.2.162]

4 59 ms 29 ms 29 ms xe-10-0-0.pcl-cr02.plus.net [212.159.0.194]

5 43 ms 29 ms 28 ms ae1.ptw-cr02.plus.net [195.166.129.2]

6 30 ms 28 ms 29 ms ae2.ptw-cr01.plus.net [195.166.129.4]

7 * 118 ms 223 ms te-3-4.car5.London1.Level3.net [217.163.45.181]

8 30 ms 35 ms 29 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]

9 29 ms 29 ms 28 ms ae-225-3601.edge3.London1.Level3.net [4.69.166.146]

10 130 ms 72 ms 29 ms gblx-level3-50g.London1.Level3.net [4.68.110.158]

11 124 ms 122 ms 123 ms 64.210.12.62

12 110 ms 110 ms 112 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]

13 111 ms 111 ms 111 ms relay-1.mwtactics.com [70.42.29.65]

Trace complete.


Is that better?

Edited by GingerPig, 26 February 2014 - 02:31 PM.


#18 DragonsFire

    Member

  • PipPipPipPipPipPipPip
  • Wrath
  • Wrath
  • 655 posts

Posted 26 February 2014 - 02:42 PM

View Postmartino2k6, on 26 February 2014 - 02:30 PM, said:

.65 is for MW Tactics, apparently. The MWOClient.exe iis connecting to 70.42.29.74. Anyway, here is mine:
<snip>

8 10 ms 10 ms 10 ms gblx-level3-50g.London1.Level3.net [4.68.110.158]
9 104 ms 105 ms 103 ms INTERNAP.Gi1-0-11.asr1.YYZ1.gblx.net [64.214.196.26]
10 93 ms 92 ms 94 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]


I always use the MWTactics IP since it responds to ICMP and actually terminates the trace. ;)

View PostGingerPig, on 26 February 2014 - 02:30 PM, said:

<snip>

10 130 ms 72 ms 29 ms gblx-level3-50g.London1.Level3.net [4.68.110.158]

11 124 ms 122 ms 123 ms 64.210.12.62

12 110 ms 110 ms 112 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]

13 111 ms 111 ms 111 ms relay-1.mwtactics.com [70.42.29.65]

Trace complete.

Is that better?


Yep! In regards to both of your routes to the server, I snipped out parts prior to the common hop at Level3. It does seem that your actual routing is allowing you to get to the servers, but there's possibly something in the intermediate hops starting at the common point that's blocking your access to the game. Your hop 11 and Martino's hop 9 differ but I doubt that is the source of the issue.

While it's possible that the problem is local/specific to each of you (and others seeing this problem) given that it's a recent development I think it's more likely that network maintenance was done somewhere and now the traffic is not passing.

Edited by DragonsFire, 26 February 2014 - 02:44 PM.


#19 GingerPig

    Member

  • PipPipPip
  • The Defiant
  • The Defiant
  • 57 posts
  • LocationUK

Posted 26 February 2014 - 02:47 PM

View PostDragonsFire, on 26 February 2014 - 02:42 PM, said:


While it's possible that the problem is local/specific to each of you (and others seeing this problem) given that it's a recent development I think it's more likely that network maintenance was done somewhere and now the traffic is not passing.


Does this mean there is anything we can do? Or have we just got to wait it out?

*UPDATE*

Found this... https://portal.plus....ice_id=adsldial

Edited by GingerPig, 26 February 2014 - 02:53 PM.


#20 DragonsFire

    Member

  • PipPipPipPipPipPipPip
  • Wrath
  • Wrath
  • 655 posts

Posted 26 February 2014 - 02:53 PM

View PostGingerPig, on 26 February 2014 - 02:47 PM, said:


Does this mean there is anything we can do? Or have we just got to wait it out?


With it not being local to you or PGI you might be without an immediate option. One other potential troubleshooting avenue would be to use a proxy to access the server, which should route you around any problem areas. If you still have a network issue then, the chance that it's local increase quite a bit.

The problem with using a proxy though would be that you would likely see a latency increase over what you already have. But it would at least be a viable option from a troubleshooting perspective.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users