#6119 - Errors 126 and 20033

[narg]

Feedback needed:

Error 20033:

Are you still getting this?

Error 126:

How often do you get this. Is it on every session?

126, still getting it. Only really get it when I fly, should ask others tho.

20033 I haven't seen in ages, doesn't mean it's not there though, my playing time has fallen significantly.

[surskis]

Yesterday it was the 126, today I'm getting 20033. Usually happens 5-60 seconds after entering the world.

Any fixes yet?

[GOPHUR]

I'll have a test exe tomorrow we can try out. Maybe later today...

I need more information. How often are you getting this error 20033? 30 seconds after every spawn? How many times in a row, what time of day, did you try spawning in the middle of no where and still getting it?

What's your connection like? Are you having any auto-updaters running in the background? Any other programs?

Can you download and run this bat file and tell me if there are any anomalies in the output file?

http://downloads.wwiionline.com/playnettrace.bat

1) download to desktop

2) right click run as administrator or run

3) look at output file playnettrace.txt

[Tigger6]

Slightly silly. Normal traceroute (laptop):

root@tigger:/home/rasto# traceroute 66.28.224.141

traceroute to 66.28.224.141 (66.28.224.141), 30 hops max, 60 byte packets

1 owl (10.0.0.1) 3.226 ms 3.578 ms 4.742 ms

2 * * *

3 217-168-57-193.static.cablecom.ch (217.168.57.193) 17.444 ms 17.592 ms 17.663 ms

4 172.31.208.77 (172.31.208.77) 17.818 ms 18.262 ms 18.475 ms

5 84-116-130-49.aorta.net (84.116.130.49) 130.997 ms 132.713 ms 126.283 ms

6 us-was03a-rd1-xe-0-3-0.aorta.net (84.116.130.66) 132.820 ms 121.943 ms 84.116.136.153 (84.116.136.153) 115.195 ms

7 us-was02a-ri1-ge-4-1-0.aorta.net (84.116.130.206) 121.258 ms 115.885 ms 119.353 ms

8 te-4-1.car3.Washington1.Level3.net (4.79.168.201) 119.364 ms 126.004 ms 120.095 ms

9 ae-1-60.edge2.Washington4.Level3.net (4.69.149.16) 121.235 ms te-4-1.car3.Washington1.Level3.net (4.79.168.201) 119.379 ms 114.676 ms

10 ae-1-60.edge2.Washington4.Level3.net (4.69.149.16) 118.103 ms COGENT-COMM.edge2.Washington4.Level3.net (4.68.63.174) 116.293 ms ae-1-60.edge2.Washington4.Level3.net (4.69.149.16) 120.776 ms

11 te0-4-0-1.mpd22.dca01.atlas.cogentco.com (154.54.41.249) 117.188 ms COGENT-COMM.edge2.Washington4.Level3.net (4.68.63.174) 120.493 ms te0-4-0-5.mpd22.dca01.atlas.cogentco.com (154.54.41.253) 122.534 ms

12 te0-1-0-5.mpd22.dca01.atlas.cogentco.com (154.54.26.121) 125.347 ms te0-3-0-7.mpd22.atl01.atlas.cogentco.com (154.54.27.98) 156.398 ms 154.884 ms

13 te0-3-0-2.mpd22.atl01.atlas.cogentco.com (154.54.27.94) 147.935 ms te0-0-0-1.mpd22.iah01.atlas.cogentco.com (154.54.29.10) 154.095 ms te0-1-0-2.mpd22.atl01.atlas.cogentco.com (154.54.28.194) 153.947 ms

14 te0-2-0-7.mpd22.iah01.atlas.cogentco.com (154.54.42.221) 154.729 ms te0-2-0-1.ccr22.dfw01.atlas.cogentco.com (154.54.25.97) 147.454 ms te0-3-0-2.ccr22.dfw01.atlas.cogentco.com (154.54.0.202) 147.419 ms

15 te0-3-0-2.ccr22.dfw01.atlas.cogentco.com (154.54.0.202) 152.437 ms te4-4.ccr01.dfw02.atlas.cogentco.com (154.54.26.34) 155.414 ms te0-4-0-1.ccr22.dfw01.atlas.cogentco.com (154.54.24.2) 154.168 ms

16 te4-4.ccr01.dfw02.atlas.cogentco.com (154.54.26.34) 158.742 ms Playnet.demarc.cogentco.com (66.28.30.146) 151.667 ms !X te4-4.ccr01.dfw02.atlas.cogentco.com (154.54.26.34) 146.865 ms

Weird OS on desktop:

Tracing route to 66.28.224.141 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.1.1

2 * * * Request timed out.

3 15 ms 9 ms 9 ms 217.168.57.193

4 12 ms 9 ms 31 ms 172.31.208.77

5 117 ms 119 ms 117 ms 84.116.134.25

6 118 ms 113 ms 114 ms 84.116.136.153

7 134 ms 114 ms 112 ms 84.116.130.153

8 112 ms 130 ms 112 ms 213.46.190.190

9 114 ms 117 ms 111 ms 4.79.168.201

10 118 ms 150 ms 114 ms 4.69.149.16

11 114 ms 115 ms 114 ms 4.68.63.174

12 115 ms 114 ms 115 ms 154.54.26.121

13 148 ms 146 ms 147 ms 154.54.28.194

14 147 ms 146 ms 147 ms 154.54.29.14

15 149 ms 147 ms 146 ms 154.54.0.202

16 145 ms 188 ms 147 ms 154.54.26.34

17 66.28.30.146 reports: Destination net unreachable.

Trace complete.

Is .146 firewall?

Edited December 8, 2011 by Tigger6

[GOPHUR]

Yes. 146 is the firewall. You're at the game server then.

[Tigger6]

Yes. 146 is the firewall. You're at the game server then.

It probably isn't available for only a few seconds. I could keep a ping running, but I get no 126s anymore.

[wayloss]

After Update last night I started to get 20033 and despawn errors. i did not have these before the host update. i also had 1 incident where I spawned into the despawn spiral and was then despawned.