Unable to Host Games - Client is using random UDP port

Since configuring the firewall on my router to allow UDP 6073, 6112-6132 (configured in ImpulseReactorOptions.exe) I've had no problems joining games.  I have been unable to host any games though.  I looked into it today, and the client is trying to use a random UDP port when initialy requesting to host a game.

In the screen shot below it tried to use port 2362 over UDP. In the several tests I did, I've seen it try the following UDP ports: 1493-1495, 1511-1513.

When I turned my firewall off, it did not maintain the connection on the random UDP port.  Once I was in the lobby of the game I was hosting, the only port open was 6073.

It would be nice if we could configure the client to use a specific port for whatever call it is making on this random UDP port so that it can be configured in our firewalls.  This may explain why other people who have only opened the recommended udp ports cannot host as well  (recommended being 6073, 6100-6200).  I'm fine with just joining games for now but once my friends pick up the game, I'll have to start relaxing my firewall to host games for them.

Thanks

 

 

1,374 views 11 replies
Reply #1 Top

Aren't those ports just used for some outbound connections to the stardock servers?

Btw. do you think the NAT facilitator erros is related to this? I can't join or host any games, because I always get this error.

Reply #2 Top

With port forwarding in place for 6073, 6112-6132, when I select the "Host Game" button it hangs and then returns the error I posted.  Monitoring my ports, I noticed it was trying to connect to a random port outside of the range we are told to use. 

The TCP ports in my screenshot are not the problem, it's the random UDP port outside the range we are told to use that's not getting past my firewall.

Reply #4 Top

Hm, when I host a game, tcpview shows mit port 6073 UDP and 6250 UDP (I configured the port range to be between 6200 and 6250). Try using different values in the ImpulseReactorOptions.exe, maybe the tool has a bug when you use the default values.

Reply #5 Top

I'm in the US.  Again, what's odd is that if I disable my firewall I'm able to host and that random port connection is gone once I'm in the lobby of my game.  So the connection on that port doesn't need to remain open the entire time, it's just at the initial request to host the Custom game. With my firewall off, the connection to the port opens and closes so fast I can barely see it while monitoring my open ports.

I think the ImpulseReactorOptions.exe is only setting what ports to connect to your peers on.  The connection to the NAT facilitator is always 6073 (from what I've seen).

 

 

 

 

Reply #6 Top

I haven't been getting NAT facilitator errors, but I haven't been able to connect to any games since I switched over to a new router config. Forwarding the same ports I did last time, no new firewalls, but now it just sits at "Has not connected to anybody" for the better part of forever, and I can't even seem to get updates on other people connecting to other people anymore.

Reply #7 Top

Kordesh, I'm not sure your problem is related to what I've posted.  I'm able to join games and connect to peers without issue.  The problem I've described is only when attempting to host Custom games.

Reply #8 Top

Quoting xxplayxx, reply 7
Kordesh, I'm not sure your problem is related to what I've posted.  I'm able to join games and connect to peers without issue.  The problem I've described is only when attempting to host Custom games.

Oops. Guess I didn't quite get what you were getting at. I kinda skimmed over it.

Reply #9 Top

Use tcpview for a more accurate view on the actual ports open.

Reply #10 Top

With TCPView:

 

Scenario: Firewall on router is up with ports open for 6073, 6112-6132.  In the screenshot, I had  just selected 'Host Game'.  TCPView shows Demigod.exe trying to open UDP port 2967.  After the connection attempt timed out, I received the error posted in my OP.