Could not connect to server

[Cirda]

Hey all,

Just signed up with a Beta key I recently acquired and haven't been able to log in yet. I have been browsing the forums looking for possible solutions, but I have not seen anything similar so I apologize if this is covered elsewhere. I have the client file, but when I enter in my login information in the client it goes to Authenticating, then goes to Connecting, but then never passes Connecting and eventually comes back saying Could not connect to server.

Now I've found the link to the server stats here: http://plymouth.seatribe.se/ss So it looks like the server is currently up.

Are there ports necessary to forward via my router? Or possibly something else I'm missing? Thanks!!!

[dullahx]

hi

There aren't any port forwarding needed, but you need to allow outgoing connections in your firewall settings.
Are you using one ?

[Cirda]

Hi dullahx, thanks for the response. I've tried as you suggested adding outgoing exceptions for my firewall, but still the same result. Authentication works, stops at Connecting and says Could not connect to server.

Just for kicks I disabled my firewall (temporarily mind you) and I was able to connect. So it is definately a firewall issue. Does anyone know what ports specifically Salem uses?

[MagicManICT]

UDP port 1870 and TCP port 1871

[dullahx]

i believe the ports are given by the OS to the java process, so could change if they aren't available, so there aren't specific ports.

[Cirda]

1870 and 1871 appear to be correct (according to wireshark anyways), but adding exceptions for javaws and 1870/1871 in/out still won't let me connect. It's close, something else must be missing here.

[dullahx]

let us know which kind of firewall you are using

[Cirda]

Sorry I have Norton Security Suite. Managing the firewall adding Program Rules to Allow for javaws and setting Traffic Rules for inbound/outbound 1870/1871 TCP/UDP set to allow.

[MagicManICT]

You'll need to set those for javaw.exe, too, as that is the process that runs the client. javaws.exe handles the .jnlp file and prepares it to be launched for the first time. After that, the processing off to javaw.exe until the applet is closed.

[Cirda]

Thanks for the responses. I added my multiple versions of javaw.exe to allow traffic with no luck. I gotta log off for the night but I'll pick this up tomorrow. Still the only way to get it working was to add a catch-all allow in the firewall... at which point what is the firewall doing exactly