VoIP causing connection Issues

[BloodBane611]

Alright, this is driving me nuts. Tried turning off all my norton protections, didn't help.

Weirdly enough I've been able to play for hours at a time on the TCombat server, while almost every other server I connect to I get dumped from.

I'm gonna see if EA has an opinion. They probably won't.

[SnipingCoward]

m8, have you checked on the overheating problem - easy way would be to just open the side of the pc and leave it open - testing it for some days
also check your fans for dust and such - don't know if you already did

and sorry to bother you again with this but - have you tried disableing "EAX" in audio options? (uncheck the box)

also you did not reply to me about deaktivating onboard sound in the bios
have you tried it? or is that a no-go? - but again that would help narrow it down

it really bugs me that you said you don't have this problem when deactivating voip - which would lead me to further claims:
1) sound card driver(s) is crap
2) router problems (recognizing voip as dos-attack? - prolly not)

edit: whats your motherboard (e.g. mine is known to have probs with bf2 - causing "connection lost"-blabla thingy)
and since when do you have this problem?
whats your inet connection?

further edit:
also - while we are desperate now and since it might be a sound problem check this post from a HELP thread NOT in the HELP SECTION but in the FEEDBACK SECTION - god knows how it got there - and why it stays there - in a sub forum...
Link to Thread

[BloodBane611]

Motherboard is: Dell ORY206 - Searched this on google and got 2 hits, one in an asian language and the other totally unrelated.

Checked overheating, fans are clean, disabled EAX, and got the new creative .dll from the thread above. No dice. Gonna try disabling the onboard sound now.

*Edit* Disabling the onboard sound did not help either.

Could it be some BF VoIP setting? I have looked around for these, but haven't found them. The fact that it works consistently on 1 server and fails consistently on all the rest leads me to believe that its a server/client setting interaction of some kind.

Also, no VoIP problems in vanilla BF2.

[SnipingCoward]

this would mean that there is a network related problem which can be every where: your software firewall, windows firewall, router firewall, ISP policies, or network drivers

maybe your network drivers conflict with your sounds?

have you tried it with the usb headset plugged off?

could you try using a different lan slot for the connection with the router?

again: since when do you have this problem?

[BloodBane611]

I only noticed this in late december, I believe right before .7

I'm going to try rolling back my network drivers to see if that helps.

It still doesn't work with the USB disconnected, and no difference with the changed LAN slot.

[composition4]

I have had this exact problem since i first played BF2. i think it is because i use a wireless modem because i have had the problem on 2 different computers and the modem is the only constant.

Unfortunately i don't have a solution but i have found when i join server with less or around 10 people on them i do not get the connection problem.However as more people begin to join the connection gets more laggy and eventually i am kicked but i have been able to stay on a full 64player server a few times.

i looked long and hard for a proper fix for this but its not a common problem and the only advice DICE gave was to turn of VOIP which isn't really a viable option if you want to play PR.....

[BloodBane611]

Yeah, I just recently figured out that it works with servers under 30ish people. The thing is I'm on an entirely wired connection, although there are 2 wireless connections running along with the wired. Out of curiosity, what router were/are you using?

*EDIT*
So max number of people depends on the server, but appears to be about 25. The only exception to the rule is TCombat, which for some reason works 100%.

[SnipingCoward]

maybe your router is a bit sensitive and he takes traffic as dos-attacks
check the router's log if you find anything suspicious

[composition4]

Originally Posted by BloodBane611

Out of curiosity, what router were/are you using?

the make is belkin

[BloodBane611]

It does appear to be the router:
01/05/2003 17:42:37 **UDP Flood to Host** 192.168.2.100, 55523->> 72.233.30.138, 55333 (from WAN Outbound)
01/05/2003 17:41:28 **UDP Flood to Host** 192.168.2.100, 55123->> 193.33.186.46, 55125 (from WAN Outbound)
01/05/2003 17:39:55 **UDP Flood to Host** 192.168.2.100, 55123->> 195.149.21.237, 55125 (from WAN Outbound)
01/05/2003 17:38:41 **UDP Flood to Host** 192.168.2.100, 55143->> 69.12.76.31, 55145 (from WAN Outbound)
01/05/2003 17:23:03 **UDP Flood to Host** 192.168.2.100, 55143->> 69.12.76.31, 55145 (from WAN Outbound)
01/05/2003 17:21:38 **UDP Flood to Host** 192.168.2.100, 16644->> 74.86.162.143, 16643 (from WAN Outbound)


So what can I do about this?