You are not logged in.
Not an OS problem. Clearly a server issue. Another case of users who aren't hitting this problem not believing those who DO have the problem.
I have the same tracert. dont accuse me of something I havnt done. take my advise if you want to but this response was uncalled for.
linux shows me the same traceroute but the server simply does not lag like it does with win 10 with a lot of players. dont ask me why. game is stupid
Started lagging for me in dec 21, had been running w10 fine upp until then. Same results with xp and linux, tried at my friend who has a different internett provider - np there.
Im too lazy to change internett provider tough.
Mine the same. Without vpn i have lag spikes that go to 300 and with vpn still a lot of lag, no spikes, but it seems packet loss. Windows 10
1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 9 ms 8 ms 10.10.127.254
3 11 ms 10 ms 10 ms 10.137.200.17
4 20 ms 13 ms 14 ms 10.255.184.98
5 * * * Request timed out.
6 27 ms 27 ms 26 ms be2313.ccr31.bio02.atlas.cogentco.com [154.54.61.101]
7 44 ms 44 ms 43 ms be2315.ccr41.par01.atlas.cogentco.com [154.54.61.114]
8 51 ms 51 ms 50 ms be12265.ccr41.ams03.atlas.cogentco.com [130.117.2.141]
9 55 ms 53 ms 54 ms be3457.ccr21.ams04.atlas.cogentco.com [130.117.1.10]
10 53 ms 51 ms 52 ms worldstream.demarc.cogentco.com [149.11.39.90]
11 54 ms 54 ms 53 ms 109.236.95.227
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.
If someone who DOESNT have this problem would be kind enough to supply a tracert run then we could have some comparison.
Would like to see what happens after 109... or whether it goes another route
Tnx
Ironfart
BTW played for a bit last night.
No problems on Tanks
Last edited by Ironfart (2022-05-01 15:16:06)
I believe a firewall to prevent ddos or spamming attempts tp the server may be responsible.
That would account for the 'request timed out'... but could it affect certain connections?
Same result with ping.exe btw.
Resounding silence on my appeal for a working tracert but would probably yield same result. ie request timed out.
My crusade for a level 'battlefield' for all continues...
Any success would only serve to make the game more appealing to others.
Ironfart
Tnx Zody for ypur comments. Im sure you can understand our frustration.
Last edited by Ironfart (2022-05-04 01:49:47)
Trace the gateway 194.88.105.1 or a neighboring machine instead ex 194.88.105.26
Tracing route to gw.worldstream.nl [194.88.105.1]
over a maximum of 30 hops:
1 * * * Request timed out.
2 48 ms 49 ms 50 ms 45.86.200.253
3 48 ms 49 ms 50 ms vl203.ams-dc1-core-1.cdn77.com [138.199.0.110]
4 50 ms 53 ms 50 ms vl211.ams-nkh-edge-1.cdn77.com [185.229.188.129]
5 50 ms 51 ms 47 ms worldstream-ams.cdn77.com [109.236.95.156]
6 50 ms 49 ms 49 ms 109.236.95.107
7 51 ms 54 ms 54 ms gw.worldstream.nl [194.88.105.1]
Trace complete.
C:\WINDOWS\system32>
Aha!....Tnx Lecter and others.
Well that clearly shows the hop after 109... is.... SIMPLE SERVER!!!! or thereabouts (request timed out)
THAT SEEMS TO BE CAUSING THE PROBLEM SOMEHOW. Problem tracerts all get to 109... easily enough and next stop is Simple!
Whether a timed out request is the same as a connection problem when playing I wouldnt know but something seems amiss.
Correct me if im wrong.
Correct the server if im right.
Heres my tracert to adjacent server fyi
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell https://aka.ms/pscore6
PS C:\WINDOWS\system32> tracert 194.88.105.1
Tracing route to gw.worldstream.nl [194.88.105.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 3 ms 2 ms 2 ms .g.network [My IP]
3 5 ms 4 ms 4 ms 10.102.0.185
4 4 ms 7 ms 1 ms 10.102.0.173
5 5 ms 3 ms 7 ms 10.102.0.145
6 4 ms 2 ms 2 ms 10.102.0.99
7 4 ms 4 ms 5 ms 10.102.0.41
8 3 ms 4 ms 2 ms 10.200.200.6
9 8 ms 10 ms 11 ms gw.worldstream.nl [194.88.105.1]
Works fine Great connection Few Hops low ping
Btw ive changed ISP twice in the last year to no avail!
Tnx
Ironfart
******************************
Actually have just noticed that 109... server is missing from above trace?
Now im really confused.
******************************
Any ideas. I need a supernerd lol!
All the best
Ironfart
Last edited by Ironfart (2022-05-05 01:44:22)
Note that the simplest explanation for "my traceroute doesn't get past 109.236.95.227 when tracing bf1942.team-simple.org" is that the next hop was the Team-SiMPLE server. But the Team-SiMPLE server has ICMP response disabled, or inbound ICMP blocked, to reduce the attack surface.
You can also "ping bf1942.team-simple.org" and not get any response. So traceroute is not going to get any response once it reaches the hop of the actual server, either. This is how traceroute and ping will look for any server with ICMP intentionally disabled.
When traceroute never received any response, it has no idea "we have reached the actual server and there is no need to continue." Traceroute will simply continue trying additional hop after additional hop, no matter how many hops you allow it to attempt.
Here are 2 traceroute listings. The first is from my hard wired 400Mg connection, max 100 hops. The second is using my cell phone as a hot spot. It still shows the timeouts but it gets there with fewer hops. Maybe that's why I never get disconnected and almost never freeze with it though it's still jerky.
C:\Users\Owner>tracert -h 100 bf1942.team-simple.org
Tracing route to bf1942.team-simple.org [194.88.105.25]
over a maximum of 100 hops:
1 1 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 14 ms 14 ms 14 ms cm-134-228-52-2.buckeyecom.net [134.228.52.2]
3 12 ms 14 ms 42 ms cm-24-53-168-97.buckeyecom.net [24.53.168.97]
4 * * * Request timed out.
5 13 ms 13 ms 24 ms cm-24-53-169-53.maxxsouthbb.net [24.53.169.53]
6 45 ms 47 ms 45 ms te0-15-0-1-5.ccr41.ord03.atlas.cogentco.com [38.104.148.33]
7 48 ms 49 ms 50 ms be2766.ccr42.ord01.atlas.cogentco.com [154.54.46.177]
8 57 ms 54 ms 54 ms be2718.ccr22.cle04.atlas.cogentco.com [154.54.7.130]
9 65 ms 63 ms 73 ms be2879.ccr22.alb02.atlas.cogentco.com [154.54.29.174]
10 67 ms 69 ms 70 ms be3600.ccr32.bos01.atlas.cogentco.com [154.54.0.222]
11 127 ms 130 ms 131 ms be2101.ccr42.lon13.atlas.cogentco.com [154.54.82.37]
12 136 ms 137 ms 139 ms be3383.rcr21.rtm01.atlas.cogentco.com [154.54.57.254]
13 142 ms 142 ms 141 ms 149.6.110.74
14 137 ms 136 ms 134 ms 109.236.95.225
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.
31 * General failure.
Trace complete.
================================Cell Hotspot=================
C:\Users\Owner>tracert bf1942.team-simple.org
Tracing route to bf1942.team-simple.org [194.88.105.25]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 172.20.10.1
2 88 ms * 38 ms 107.243.2.138
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 228 ms 188 ms 197 ms 149.6.110.74
15 226 ms 188 ms 197 ms 109.236.95.225
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.
tnx all
these examples are useful
The 109.236... blah blah server seems to be the common component amongst problem connections.
Seems to have high ping as well although an intermittent problem would be lucky to surface in the window afforded by the tracert run!
When the sister server 194.88.105.1 is tracert(ed) the 109 server does not get in the way!
But Ciceros trace from his hot spot (without freeze) goes there too so I dont know if its relevant.
Wonder what this server is. Worth a snoop! I guess thats all that can be done. Ill let you know...
Might have to move house lol.
May all your shots hit,
Ironfart
Well if anyones interested Ive made some progress...
The 10... servers on my tracert are 'Bogon servers! '
Apparently they are unregistered servers and ' have no place on an internet routing table as they are common sources of ddos attacks'! according to some article I just read.
My new fibre is still under three month trial so next stop my ISP!!!
Wish me luck.
Btw the 109 server turned out to be Worldstream (Simple) but not really important now.
Those with con probs I urge you to Google those IPs. You might find something interesting.
All the Best
Ironfart
supporter wrote:Hi guys! I'm at Lisboa, Portugal! Sometimes i have a lots of lag in the game, especially when server is with a lot of people
Any advices for me?! I'm running origin version of the BF1942 and im on Windows 10.Thanks
Hello, como te chamas?
Im from Lisbon too, its crazy here. Which provider are you using? I use NOS.
Abraço
My name is Pedro. Yeah. Same here! My internet provider is NOS.
Btw:
Tracing route to gw.worldstream.nl [194.88.105.1]
over a maximum of 30 hops:
1 8 ms 7 ms 8 ms routertecnico.home [192.168.1.1]
2 * * * Request timed out.
3 17 ms 14 ms 14 ms 10.137.201.225
4 19 ms 19 ms 19 ms 10.255.184.90
5 * * * Request timed out.
6 34 ms 31 ms 31 ms be2314.ccr32.bio02.atlas.cogentco.com [154.54.61.105]
7 48 ms 49 ms 48 ms be2318.ccr42.par01.atlas.cogentco.com [154.54.61.118]
8 57 ms 55 ms 57 ms be12266.ccr42.ams03.atlas.cogentco.com [154.54.56.173]
9 58 ms 56 ms * be3458.ccr21.ams04.atlas.cogentco.com [154.54.39.186]
10 57 ms 56 ms 57 ms worldstream.demarc.cogentco.com [149.11.39.90]
11 59 ms 56 ms 57 ms gw.worldstream.nl [194.88.105.1]
Trace complete.
i have those problems too ping jumps,freezes,disconnects, theres nothing you could do personally, it happens to some people after server moved to netherlands
Last edited by Denny (2022-05-06 18:09:16)
I still use XP most of the time to play BF1942 and dont suffer any lag. (I live in a cow field and only get 2.5mbps, but with a fairly quick latency)
People need to be aware that Windows10 is a peer to peer updating operating system. All the updates you are forced to download are available to other Win10 users in your physical area and you have no say in stopping this, nor when they happen. Try setting your Win10 machines to have a metered internet connection and this may reduce, but not completely eradicate, windows from updating other people's machines when you are not aware.
Microsoft are aXrsholes and watch out for Windows11, its even worse. It takes over your PC's, demands your identity, encrypts all your data and fully controls what you can install. Also it will prevent, in collusion with hardware manufacturers, what OS you can install instead of Windows.
Lecter wrote:supporter wrote:Hi guys! I'm at Lisboa, Portugal! Sometimes i have a lots of lag in the game, especially when server is with a lot of people
Any advices for me?! I'm running origin version of the BF1942 and im on Windows 10.Thanks
Hello, como te chamas?
Im from Lisbon too, its crazy here. Which provider are you using? I use NOS.
Abraço
My name is Pedro. Yeah. Same here! My internet provider is NOS.
Btw:
Tracing route to gw.worldstream.nl [194.88.105.1]
over a maximum of 30 hops:1 8 ms 7 ms 8 ms routertecnico.home [192.168.1.1]
2 * * * Request timed out.
3 17 ms 14 ms 14 ms 10.137.201.225
4 19 ms 19 ms 19 ms 10.255.184.90
5 * * * Request timed out.
6 34 ms 31 ms 31 ms be2314.ccr32.bio02.atlas.cogentco.com [154.54.61.105]
7 48 ms 49 ms 48 ms be2318.ccr42.par01.atlas.cogentco.com [154.54.61.118]
8 57 ms 55 ms 57 ms be12266.ccr42.ams03.atlas.cogentco.com [154.54.56.173]
9 58 ms 56 ms * be3458.ccr21.ams04.atlas.cogentco.com [154.54.39.186]
10 57 ms 56 ms 57 ms worldstream.demarc.cogentco.com [149.11.39.90]
11 59 ms 56 ms 57 ms gw.worldstream.nl [194.88.105.1]Trace complete.
Pedro, we have the same provider...ill try moving to Vodafone next month and test it
Just to recap...
My personal connection problem which seems common isnt O.S or caused by updates...All updates turned off . Use a game booster that turns off other 'stuff' as well. Ive only got 108 processes running and 10% cpu load during game. Cpu and bandwidth wouldnt be touched by minor interference
Definitely a net route problem which of course may never be solved without changing ISP (Again! Might get lucky next time?).
No harm in trying though.
My next port of call is my router...
Port forwarding?
Im stuck at this. Apparently I can set my router for a better direct connection to a game server so Ill look into that next. Get the right numbers in the right place. Most routers are the same?
Ive downloaded a nokia app on my phone which gives me better control over my router.
Might be onto something...Any experience of this would be received gratefully.
tnx
Ironfart
Ill let you know
Changed ISP 2 weeks ago, no more lag after that!