Sign in to follow this  
Followers 0
wargod

Netcode 2 error

2 posts in this topic

Get this everytime I spawn, trying to nail down the problem. Found an old post where somebody said to trace this route so I did that and here it is.

Microsoft Windows [Version 6.1.7601]

Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\James>tracert -d 66.28.6.226

Tracing route to 66.28.6.226 over a maximum of 30 hops

1 40 ms 31 ms 30 ms 66.174.115.229

2 37 ms 19 ms 21 ms 69.83.27.162

3 40 ms 27 ms 31 ms 69.83.26.49

4 28 ms 27 ms 37 ms 69.83.27.33

5 41 ms 36 ms 37 ms 69.83.27.66

6 43 ms 37 ms 40 ms 69.83.17.196

7 * * * Request timed out.

8 49 ms 39 ms 38 ms 66.174.9.129

9 50 ms 30 ms 40 ms 152.179.65.73

10 101 ms 26 ms 39 ms 152.63.38.177

11 38 ms 40 ms 38 ms 152.63.38.13

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17 154.54.13.137 reports: Destination net unreachable.

Trace complete.

C:\Users\James>tracert -d 204.70.193.9

Tracing route to 204.70.193.9 over a maximum of 30 hops

1 29 ms 39 ms 37 ms 66.174.115.229

2 29 ms 20 ms 39 ms 69.83.27.162

3 38 ms 47 ms 32 ms 69.83.26.49

4 36 ms 39 ms 39 ms 69.83.27.33

5 38 ms 39 ms 39 ms 69.83.27.66

6 42 ms 39 ms 39 ms 69.83.17.196

7 * * * Request timed out.

8 47 ms 41 ms 38 ms 66.174.9.129

9 40 ms 39 ms 39 ms 152.179.65.73

10 36 ms 38 ms 41 ms 152.63.4.106

11 39 ms 40 ms 38 ms 152.63.39.121

12 38 ms 40 ms 38 ms 208.173.52.81

13 30 ms 38 ms 38 ms 204.70.197.246

14 85 ms 79 ms 89 ms 204.70.196.213

15 78 ms 77 ms 79 ms 204.70.193.9

Trace complete.

What can I do to fix this?

Share this post


Link to post
Share on other sites

Try pinging 66.28.6.226 and 204.70.193.9 to verify connectivity instead of trace route. Some routers/firewalls don't reply back to tracert packets, or ping packets for that matter. Doesn't mean a connection can't be made.

I can recommend a couple things that MIGHT help, its not 100% solution, and don't hold me liable for anything.

1: Make sure that ports "27015" through "27020" are all open. This is used by the game. Make sure they are forwarded/open on your PC's windows firewall/etc and make sure its forwarded/open on your router.

2: Your TCP/IP protocol stack. Its the protocol suite of software used by your computer for internet connections. It can be tweaked/modified by changing the registry values for it. Why do this? Sometimes the default TCP/IP settings aren't good enough for gaming, OR virus/bot/trojan/malware changed the values.

You can get on Regedit and do it manually, or...

I personally use TCP/IP Optimizer www.speedguide.net to make the change easy. Just put your connection speed in and click on "optimal", restart your computer and its done! easy as that.

3. Your Network Card adapter settings. Go to change adapter settings on windows and go to properties. Just double check to see if IPv4 is checked, and if its all default settings for it. Might as well check IPv6 too while your at it, it can't hurt and people are making the slow switch to IPv6 also.

4. Battleground Europe itself. Use the "Best connection" setting, since it automagically chooses between the primary and secondary setting anyways for you. Adjust the amount of visible players, you might have to set it to "low" to save some bandwidth. Also try running windows compatibility and try making WW2.exe and Playonline.exe compatible with windows XP and make sure to RUN IT AS ADMINISTRATOR.

This is all I can think of, I get this error sometimes to. Hope this helps.

P.S. At the end of the day, it really comes down to your ISP/Internet connection and its quality. Packet loss will cause the Netcode2 error. If your using DSL, expect packet loss and dodgy quality. This is not easy to change, because not everyone can simply change their Internet Service Providers or upgrade their internet connections easily.

Edited by elenrod

Share this post


Link to post
Share on other sites
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.