BF2 Connection

**BigHub** · 04-30-08, 07:24 PM

When I try to play on BF2 or even BF2142, I can make it into the game... But once I get on TTP, I play for like 1-2 minutes then get a "Connection has been lost" or some shit.

Never happens in CS, TF2, DoD, CoD4, or anyother games I play. Just BF games.

Anybody got any ideas?

My firewall is turned on, but I allowed BF2 and BF2142 to get through. I also manually updated PB.

**CivilWars** · 04-30-08, 07:25 PM

First thing I would try is a manual punkbuster update. www.evenbalance.com If that does not work someone smarter than me can probably help you.

**w4jchosen** · 04-30-08, 07:26 PM

You are not getting any kind of message? If you are, what is it?

**BigHub** · 04-30-08, 07:28 PM

Originally Posted by BigH?b

When I try to play on BF2 or even BF2142, I can make it into the game... But once I get on TTP, I play for like 1-2 minutes then get a "Connection has been lost"

Never happens in CS, TF2, DoD, CoD4, or anyother games I play. Just BF games.

Anybody got any ideas?

My firewall is turned on, but I allowed BF2 and BF2142 to get through. I also manually updated PB.

**Allane** · 04-30-08, 07:29 PM

(Ok, Hub beat me to you guys) I suggest posting a tracert, and we can see where the thing goes haywire. From there, I don't have a lot to suggest.

Don't forget that EA has been on the fritz lately, I'm not trusting them hardcore at the moment.

**BigHub** · 04-30-08, 07:38 PM

I did it 3 times. As you can see, there are some spikes... Is that causing it to totally lose connection though?

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 172.17.106.1
2 1 ms 1 ms 5 ms rrcs-71-42-146-1.sw.biz.rr.com [71.42.146.1]
3 6 ms 10 ms 10 ms gig3-0-0.austtxa-pe-rtr01.texas.rr.com [24.93.60.157]
4 7 ms 11 ms 6 ms gig2-0-0.wacotxmhe-p-rtr01.texas.rr.com [24.93.60.159]
5 5 ms 7 ms 7 ms gig3-0-0.wacotxmhe-pe-rtr01.texas.rr.com [24.93.60.129]
6 7 ms 6 ms 15 ms gig2-0-0.dllatxl3-p-rtr01.texas.rr.com [24.93.60.131]
7 6 ms 10 ms 10 ms gig4-2-0.dllatxl3-rtr1.texas.rr.com [24.93.60.62]
8 11 ms 10 ms 11 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
9 15 ms 15 ms 203 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179][
10 10 ms 15 ms 14 ms 64.132.69.65
11 12 ms 16 ms 15 ms hagg-03-ge-1-0-0-459.dlfw.twtelecom.net [64.129.234.20]
12 15 ms 16 ms 15 ms 63.164.96.databank.com [63.164.96.58]
13 16 ms 16 ms 17 ms lt-pod2b.lt.com [63.164.96.238]
14 * * * Request timed out.
15 15 ms 15 ms 16 ms 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]

Trace complete.

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 172.17.106.1
2 6 ms 6 ms 5 ms rrcs-71-42-146-1.sw.biz.rr.com [71.42.146.1]
3 10 ms 11 ms 10 ms gig3-0-0.austtxa-pe-rtr01.texas.rr.com [24.93.60.157]
4 17 ms 200 ms 206 ms gig2-0-0.wacotxmhe-p-rtr01.texas.rr.com [24.93.60.159]
5 13 ms 4 ms 9 ms gig3-0-0.wacotxmhe-pe-rtr01.texas.rr.com [24.93.60.129]
6 6 ms 10 ms 10 ms gig2-0-0.dllatxl3-p-rtr01.texas.rr.com [24.93.60.131]
7 14 ms 6 ms 10 ms gig4-2-0.dllatxl3-rtr1.texas.rr.com [24.93.60.62]
8 12 ms 11 ms 10 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
9 15 ms 15 ms 16 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
10 16 ms 14 ms 14 ms 64.132.69.65
11 123 ms 75 ms 37 ms hagg-03-ge-1-0-0-459.dlfw.twtelecom.net [64.129.234.20]
12 16 ms 16 ms 15 ms 63.164.96.databank.com [63.164.96.58]
13 17 ms 13 ms 21 ms lt-pod2b.lt.com [63.164.96.238]
14 * * * Request timed out.
15 16 ms 16 ms 18 ms 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]

Trace complete.

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 2 ms 4294967294 ms 4294967295 ms 172.17.106.1
2 1 ms 1 ms 1 ms rrcs-71-42-146-1.sw.biz.rr.com [71.42.146.1]
3 6 ms 6 ms 6 ms gig3-0-0.austtxa-pe-rtr01.texas.rr.com [24.93.60.157]
4 10 ms 6 ms 6 ms gig2-0-0.wacotxmhe-p-rtr01.texas.rr.com [24.93.60.159]
5 4 ms 4 ms 4 ms gig3-0-0.wacotxmhe-pe-rtr01.texas.rr.com [24.93.60.129]
6 6 ms 7 ms 6 ms gig2-0-0.dllatxl3-p-rtr01.texas.rr.com [24.93.60.131]
7 10 ms 6 ms 10 ms gig4-2-0.dllatxl3-rtr1.texas.rr.com [24.93.60.62]
8 7 ms 10 ms 11 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
9 11 ms 11 ms 11 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
10 15 ms 20 ms 10 ms 64.132.69.65
11 13 ms 12 ms 17 ms hagg-03-ge-1-0-0-459.dlfw.twtelecom.net [64.129.234.20]
12 11 ms 11 ms 12 ms 63.164.96.databank.com [63.164.96.58]
13 12 ms 13 ms 13 ms lt-pod2b.lt.com [63.164.96.238]
14 * * * Request timed out.
15 11 ms 13 ms 12 ms 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]

Trace complete.

**w4jchosen** · 04-30-08, 07:41 PM

Okay here is a shot in the dark, but try updating your graphic card drivers if you haven't in a while.

**BigHub** · 04-30-08, 07:42 PM

Trust me, I keep that shit up-to-date.

**w4jchosen** · 04-30-08, 07:45 PM

Okay I'll make two more suggestions. Make sure your bf2 is checked off in windows firewall security or whatever firewall you are using and also make sure pnkA and pnkB are enabled.