"Authenticating..." until "Connection timeout"

[RiverPhoenix]

Hello

I've a feeling I might not get into this game tonight... oh well... maybe later...

Everything loads fine to the login screen, I put in my username and password and hit login and says "Authenticating..." ... after some time it sends me back to the login screen with extra text in red saying "Connection timeout".

What ports does this client use to communicate with the server? I'm guessing this is possibly a firewall issue (excepting if it uses port 80 or 8080).

Thank you for any help you can give me,

River Phoenix

[loftar]

Are you blocking ports by default or something? If you are, Haven uses 1871/tcp (for authentication only) and 1870/udp for the game.

[RiverPhoenix]

Are you blocking ports by default or something? If you are, Haven uses 1871/tcp (for authentication only) and 1870/udp for the game.

Yes, thank you for the info - I guess I should have just sniffed it but this way I'm sure I got them all!

River Phoenix

[kobnach]

Same problem here, except what I see is "Connecting..." followed by could not connect to server". I also got complaints from windows about the program receiving connections. I presume that's the udp, with the tcp connection being initiated from my PC. (Yes, this matters, my firewall cares about where a connection is initiated. I'm much more paranoid about incoming than outgoing.)

[RiverPhoenix]

Same problem here, except what I see is "Connecting..." followed by could not connect to server". I also got complaints from windows about the program receiving connections. I presume that's the udp, with the tcp connection being initiated from my PC. (Yes, this matters, my firewall cares about where a connection is initiated. I'm much more paranoid about incoming than outgoing.)

Actually this is the same problem I had... my firewall will allow responses on the same port as an outgoing request but not incoming requests when I didn't already have an outgoing one - this may be a problem with UDP generally though. You should be able to tell Windows to just let the connection through in future - if you still have a problem and can tell me which version of Windows you are using I can probably tell you how to do this if it isn't obvious

River Phoenix

[kobnach]

All is fine now. My setup allows systems on the inside to initiate connections, but connections initiated from outside need to be specifically authorized. UDP is connectionless, so I have to tell the firewall about each port. This is separate from windows firewall - which had a similar issue, but was willing to accept a blanket authorization for the particular program to receive connections.