Mohaa query port

[Redeye]

Mohaa servers are default supplied with a queryport which is the same as the gameport 12203. The queryport is not supplied in the startupline, since it default add 97 to work. 12300 would be the correct port. However, on my windows machine it only opens 12203 UDP. I can query it using ase, and using the controlpanel, but my client can't?

 

Does this ring any bells on someone?

[JasonF]

If your game port is 12203, try the query port 12300. That is what Qtracker uses and what I have to use to query client servers using it. What are your clients using to query the server?

[Redeye]

Qtracker does not find the server. It's online and ase can connect. GM also sees the server and we can join without a problem.

 

The scripts they use are unclear atm, i have sent them an email with the question.

 

What I don't understand is that if the gameserver would listen on 12203 and 12300 it should both be listed on netstat -anm which only list 12203. :s

 

(TCPview shows the same)

[xpservers]

Airborne servers use random query ports so its imposible for TCA to query the server status. if you notice HLSW also does not support MOHAA due to this.

[ECF]

Actually most UT3 based games have this same issue. Unfortunately Epic has so far not fixed it.