Let me in the frak'n QGW R-32 (connection issues)!

This is for troubleshooting of problems with the FAF client and Forged Alliance game.

Moderator: PhilipJFry

Forum rules


BEFORE POSTING read


Our wiki contains a lot of helpful material about technical issues, try looking there first!

Use the search function before opening a thread! (https://www.faforever.com/forums/search.php)

Read this before posting here: https://wiki.faforever.com/index.php?ti ... cal_Issues
Post a reply

Let me in the frak'n QGW R-32 (connection issues)!

Postby FreePointz » 02 Jan 2012, 19:54

Hello!
I cannot connect to any games via FAF. Specifically, FAF works perfectly fine, I can login, chat, watch replays and DL maps, but when I try to connect to a listed game, FA starts up and hangs on the connecting screen (black screen with "connecting to server" with abort connection option).


Here's the relevant part of FA.log
Code: Select all
info: GPGNET: setting nat handler to 0x22090004
info: LOBBY: Game port 6112[UDP] opened.
info: LOBBY: starting with local uid of 8314 [FreePointz]
info: GPGNET: entering lobby state.
info: GPGNET: sending nat packet to 91.229.20.50:30351
info: GPGNET: sending nat packet to 188.232.192.71:6112
info: GPGNET: sending nat packet to 188.232.192.71:6112
info: NET: using deflate compression for sends to dynamicip-188-232-192-71.pppoe.omsk.ertelecom.ru:6112.
info: LOBBY: Connecting to host "ARIEC" [dynamicip-188-232-192-71.pppoe.omsk.ertelecom.ru:6112, uid=236]
info: Can't add chat text -- no chat display
info: text="Connecting to game host..."
info: GPGNET: sending nat packet to 91.156.13.123:6164
info: GPGNET: sending nat packet to 91.156.13.123:6164
info: NET: using deflate compression for sends to a91-156-13-123.elisa-laajakaista.fi:6164.
info: LOBBY: Adding peer "Kalez" [a91-156-13-123.elisa-laajakaista.fi:6164, uid=6492]
info: Can't add chat text -- no chat display
info: text="Connecting to Kalez..."
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: NET: using deflate compression for sends to p5DC11401.dip.t-dialin.net:6112.
info: LOBBY: Adding peer "Ra" [p5DC11401.dip.t-dialin.net:6112, uid=1337]
info: Can't add chat text -- no chat display
info: text="Connecting to Ra..."
info: GPGNET: sending nat packet to 84.103.0.13:6112
info: GPGNET: sending nat packet to 84.103.0.13:6112
info: NET: using deflate compression for sends to 13.0.103.84.rev.sfr.net:6112.
info: LOBBY: Adding peer "Burnout" [13.0.103.84.rev.sfr.net:6112, uid=1177]
info: Can't add chat text -- no chat display
info: text="Connecting to Burnout..."
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: sending nat packet to 84.114.34.27:6112
info: GPGNET: sending nat packet to 84.114.34.27:6112
info: NET: using deflate compression for sends to chello084114034027.14.vie.surfer.at:6112.
info: LOBBY: Adding peer "techflex" [chello084114034027.14.vie.surfer.at:6112, uid=982]
info: Can't add chat text -- no chat display
info: text="Connecting to techflex..."
info: GPGNET: sending nat packet to 176.212.5.29:43781
info: GPGNET: sending nat packet to 176.212.5.29:43781
info: NET: using deflate compression for sends to dynamicip-176-212-5-29.pppoe.kirov.ertelecom.ru:43781.
info: LOBBY: Adding peer "BOTANIK" [dynamicip-176-212-5-29.pppoe.kirov.ertelecom.ru:43781, uid=7089]
info: Can't add chat text -- no chat display
info: text="Connecting to BOTANIK..."
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: NET: using deflate compression for sends to HSI-KBW-46-223-150-43.hsi.kabel-badenwuerttemberg.de:6112.
info: LOBBY: Adding peer "Kryo" [HSI-KBW-46-223-150-43.hsi.kabel-badenwuerttemberg.de:6112, uid=917]
info: Can't add chat text -- no chat display
info: text="Connecting to Kryo..."
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: received nat packet from 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: sending nat packet to 93.193.20.1:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: received nat packet from 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: GPGNET: sending nat packet to 46.223.150.43:6112
info: Minimized true
info: Minimized false
info: GPGNET: sending nat packet to 77.181.85.102:6112
info: GPGNET: sending nat packet to 77.181.85.102:6112
info: NET: using deflate compression for sends to dsdf-4db55566.pool.mediaWays.net:6112.
info: LOBBY: Adding peer "Karottenrambo" [dsdf-4db55566.pool.mediaWays.net:6112, uid=813]
info: Can't add chat text -- no chat display
info: text="Connecting to Karottenrambo..."
info: GPGNET: sending nat packet to 176.212.5.29:43781
info: GPGNET: sending nat packet to 176.212.5.29:43781
info: NET: using deflate compression for sends to dynamicip-176-212-5-29.pppoe.kirov.ertelecom.ru:43781.
info: LOBBY: Adding peer "BOTANIK" [dynamicip-176-212-5-29.pppoe.kirov.ertelecom.ru:43781, uid=7089]
info: Can't add chat text -- no chat display
info: text="Connecting to BOTANIK..."
info: GPGNET: setting nat handler to 0x00000000
info: CNetTCPBuf::Read(): recv() failed: WSAEINTR
info: Run time: 0h01m01s


I also ran NATTrace, passed all 16 tests.
Code: Select all
NATTrace report (v1.01)

Generated: 1/2/2012 11:36:49 AM (1/2/2012 5:36:49 PM UTC)
Hostname: MadiPower
adapter: Broadcom NetLink (TM) Gigabit Ethernet
  addresses: fe80::6102:2acf:8ea5:8ec9%10, 192.168.1.2
  gateway: 192.168.1.1
adapter: Software Loopback Interface 1
adapter: Microsoft ISATAP Adapter
adapter: Teredo Tunneling Pseudo-Interface

Tests:
Test 1: SUCCESS - Connect to fixed IP
  success
Test 2: SUCCESS - Check NATTrace version
  success
Test 3: SUCCESS - Perform DNS lookup
  success
Test 4: SUCCESS - Connect to named host
  success
Test 5: SUCCESS - Direct TCP to fixed IP
  success
Test 6: SUCCESS - Direct TCP (web) to named host
  success
Test 7: SUCCESS - Direct TCP (6112) to named host
  success
Test 8: SUCCESS - Direct UDP (6112) to fixed IP
  success
Test 9: SUCCESS - Direct UDP (6112) to named host
  success
Test 10: SUCCESS - NAT check, port 6112
  success
Test 11: SUCCESS - Direct UDP (port 9103)
  success
Test 12: SUCCESS - NAT check, port 9103
  success
Test 13: SUCCESS - Direct UDP (port 30350)
  success
Test 14: SUCCESS - NAT check, port 30350
  success
Test 15: SUCCESS - Direct UDP (port 30351)
  success
Test 16: SUCCESS - NAT check, port 30351
  success

0 tests failed


I have ports 6112,9103,30350-30351 udp/tcp opened (both on my router firewall as well as my pc firewall), as well as application exceptions the relevant exes (included the modified one from the faf install). I have also tried disabling my firewall/anti virus and designating my computer as a DMZ, despite that I was still unable to join.

I have gone through most of the topics here: http://forums.gaspowered.com/viewtopic.php?t=2531 and whatever experience I have had with setting up ut2k4,dow2,ss2, and fs for multiplayer. Any advice?

Thanks,
FreePointz
FreePointz
 
Posts: 3
Joined: 31 Dec 2011, 03:51
Has liked: 0 time
Been liked: 0 time
Top

Re: Let me in the frak'n QGW R-32 (connection issues)!

Postby FreePointz » 07 Jan 2012, 18:14

Alright ladies and gents I have figured out how to remote access the QGW R-32 and got everything working. In fact I beamed ALL parts of myself to a single location (I shudder to think of the results of debugging a Quantum Gates for 'connection issues'). For all those who are having weird connection difficulties and are pretty sure it is not a router/ personal firewall issue (http://www.wireshark.org/ wireshark can help with diagnosis, recieving packets etc), try accessing your modem. I have an ATT modem (2210-02-1) and turning the option "Let LAN device share Internet address" to "yes..." fixed my problems.
FreePointz
 
Posts: 3
Joined: 31 Dec 2011, 03:51
Has liked: 0 time
Been liked: 0 time
Top
Post a reply

Return to Tech Support

Who is online

Users browsing this forum: No registered users and 1 guest