im stuck at connecting... help pls

im having that problem too...like for a week now....sometimes i can connect...like alternate..now i can play then tommorow stuck again on connecting to online services...how to fix this?last month it was working smoothlty like no problems at all...but now...damn..i cant play!!its just a big luck if i connect without any problem nowadays

viewtopic.php?f=30&t=9515 #10

how to do that?is there any tutorial?btw my router is dlink dir 300

how to do that?is there any tutorial?btw my router is dlink dir 300

Here http://portforward.com/english/routers/port_forwarding/Dlink/DIR-300/Call_of_Duty_-_Modern_Warfare_3.htm

how to do that?is there any tutorial?btw my router is dlink dir 300

Here http://portforward.com/english/routers/port_forwarding/Dlink/DIR-300/Call_of_Duty_-_Modern_Warfare_3.htm

Uh, why would he do that on his router ?

Open up your windows firewall and then add the 3074 port as an exception.

Port 3074 is being blocked. Open exception rules for port 3074 UDP on whatever firewall that might be blocking it (either windows, anti-virus or router firewall).

Isn't what I said a tutorial on how to open the router firewall?

Port 3074 is being blocked. Open exception rules for port 3074 UDP on whatever firewall that might be blocking it (either windows, anti-virus or router firewall).

Isn't what I said a tutorial on how to open the router firewall?

In most cases(seriously like 90% +) it's connected to the windows firewall.

Port 3074 is being blocked. Open exception rules for port 3074 UDP on whatever firewall that might be blocking it (either windows, anti-virus or router firewall).

Isn't what I said a tutorial on how to open the router firewall?

In most cases(seriously like 90% +) it's connected to the windows firewall.

Ok, sorry, just following what the Common Errors/Fixes/Solutions post said.

how to open exception rules for port 3074 UDP??Help please!!any tutorial?sorry coz i dint know much about it!!

This topic was about that problem happening on dedicated servers, wich usually fixed with a winsock reset (as mentioned on the common fixes topic).

I'm locking this now, as this topic is derailing into a client issue wich is caused by different problems. You can find tons of fixed topics on that, here on IW5M section.