HOME No, AAS for OA does not need any client side addons at this stage.Originally Posted by RogueBlade
No, AAS for OA does not need any client side addons at this stage.
No, but some routers are falsely dropping small network packets, which could be the case for you too.
What router model do you have and did you have the same problem with the previous one (in case you played ArmA 2 / OA before)?
Yep same problem with old router
In game name: Josh
Also, could you please go to Start(->Run...) and enter cmd. Then try the following command and tell me if you get timeouts: "ping bistudio.com -l 7".
Netgear DNG1000
Ok well this doesn't look good:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Josh>ping bistudio.com -l 7
Pinging bistudio.com [81.0.236.117] with 7 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 81.0.236.117:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Josh>
What does this mean? I can play in non-battle eye servers just fine such as Charlie Foxtrot as well as all my other games
Last edited by RogueBlade; Aug 7 2010 at 14:52.
Read this thread: http://forums.bistudio.com/showthread.php?t=103247. I had reports of the DGN1000 causing this problem before, so there definitely seems to be a serious issue with this model.
It means that your router is dropping small packets, which shouldn't be happening.
Could you please create a support ticket at https://my.netgear.com/myNETGEAR/support.asp and refer to my ticket #12632987 in it (simply say you have the very problem I described there)? So far Netgear refused to escalate this issue to their dev team, because they want a user of this router to test a few things first. Another user that I talked to said that he talked to them on the phone, and after trying a few things they said it was the ISP's fault. However, I had another report about a user fixing this issue by using another router, so this can't really be true.
Also, what sort of router did you have before? And are you sure you had the same problem back then?
Ok ticket submitted. My router before hand was another modem/router in one which was the Netgear DG834G v3. Now that I think about it. When I was using that, I was playing AAS (Battle Eye) servers just fine! But I can't use the old router anymore because it is my landlords.
So yes, despite my initial claims, this must be a router issue. What more can I do?
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Josh>ping bistudio.com -l 0
Pinging bistudio.com [81.0.236.117] with 0 bytes of data:
Reply from 81.0.236.117: bytes=0 time=64ms TTL=49
Reply from 81.0.236.117: bytes=0 time=64ms TTL=49
Reply from 81.0.236.117: bytes=0 time=64ms TTL=49
Reply from 81.0.236.117: bytes=0 time=65ms TTL=49
Ping statistics for 81.0.236.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 65ms, Average = 64ms
C:\Users\Josh>ping bistudio.com -l 1
Pinging bistudio.com [81.0.236.117] with 1 bytes of data:
Reply from 81.0.236.117: bytes=1 time=66ms TTL=49
Reply from 81.0.236.117: bytes=1 time=64ms TTL=49
Reply from 81.0.236.117: bytes=1 time=65ms TTL=49
Reply from 81.0.236.117: bytes=1 time=65ms TTL=49
Ping statistics for 81.0.236.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 66ms, Average = 65ms
C:\Users\Josh>ping bistudio.com -l 2
Pinging bistudio.com [81.0.236.117] with 2 bytes of data:
Reply from 81.0.236.117: bytes=2 time=64ms TTL=49
Reply from 81.0.236.117: bytes=2 time=64ms TTL=49
Reply from 81.0.236.117: bytes=2 time=64ms TTL=49
Reply from 81.0.236.117: bytes=2 time=65ms TTL=49
Ping statistics for 81.0.236.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 65ms, Average = 64ms
C:\Users\Josh>ping bistudio.com -l 3
Pinging bistudio.com [81.0.236.117] with 3 bytes of data:
Reply from 81.0.236.117: bytes=3 time=64ms TTL=49
Reply from 81.0.236.117: bytes=3 time=64ms TTL=49
Reply from 81.0.236.117: bytes=3 time=64ms TTL=49
Reply from 81.0.236.117: bytes=3 time=64ms TTL=49
Ping statistics for 81.0.236.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 64ms, Average = 64ms
C:\Users\Josh>ping bistudio.com -l 4
Pinging bistudio.com [81.0.236.117] with 4 bytes of data:
Reply from 81.0.236.117: bytes=4 time=64ms TTL=49
Reply from 81.0.236.117: bytes=4 time=64ms TTL=49
Reply from 81.0.236.117: bytes=4 time=64ms TTL=49
Reply from 81.0.236.117: bytes=4 time=64ms TTL=49
Ping statistics for 81.0.236.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 64ms, Average = 64ms
C:\Users\Josh>ping bistudio.com -l 5
Pinging bistudio.com [81.0.236.117] with 5 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 81.0.236.117:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Josh>ping bistudio.com -l 6
Pinging bistudio.com [81.0.236.117] with 6 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 81.0.236.117:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Josh>ping bistudio.com -l 7
Pinging bistudio.com [81.0.236.117] with 7 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 81.0.236.117:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Josh>ping bistudio.com -l 8
Pinging bistudio.com [81.0.236.117] with 8 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 81.0.236.117:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Josh>ping bistudio.com -l 9
Pinging bistudio.com [81.0.236.117] with 9 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 81.0.236.117:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Josh>ping bistudio.com -l 10
Pinging bistudio.com [81.0.236.117] with 10 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 81.0.236.117:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Josh>
Everything after 4 times out.
Last edited by RogueBlade; Aug 7 2010 at 17:38.
Unfortunately nothing right now, just make sure you follow their instructions and tell them that you didn't have this problem with the previous router. Netgear needs to fix this with a firmware update.
---------- Post added at 19:55 ---------- Previous post was at 19:35 ----------
Yes, others reported the same (0 to 4 works, 5 to X times out, 32 is known to be working again). This of course makes the problem even weirder and shows that something isn't right with Netgear's firmware.
You could do some more tests to find out at which size the timeouts stop. I suggest posting these test results in your support ticket as well.
Mine works at 11 and onwards. Seems only to be after 4 to 10. I'll add that to my ticket
Well I got a reply from NETGEAR support and the guy confirms that
"I understand that small UDP packets of size 5-10 bytes are getting dropped while using NETGEAR DGN1000 Router."
He asked for this info which I gave him:
1) Do you have any firewall software's running in your computers? if yes, please disable it.
2) Have you tried resetting and reconfiguring the NETGEAR DGN1000 Router after updating the latest firmware?
3) Who is your internet service provider?
4) What is the ADSL port ip address and Router firmware?
So hoping for a useful response. I told him with my old router no such issue existed
Posting Permissions
Reply With Quote