Page 1 of 1

Crash on application launch.

PostPosted: Wed Jan 23, 2013 6:12 pm
by ephemeralkap
Hello.

I've been struggeling for two days trying to resolve this issue, but have not had any luck so far.

Whenever I launch the application, and press login. It crashes and gives me this error message.

Code: Select all
java.lang.RuntimeException: java.net.BindException: Cannot assign requested address: Cannot bind
   at haven.Session.<init>(Session.java:789)
   at haven.Bootstrap.run(Bootstrap.java:170)
   at haven.MainFrame.run(MainFrame.java:247)
   at java.lang.Thread.run(Unknown Source)
Caused by: java.net.BindException: Cannot assign requested address: Cannot bind
   at java.net.DualStackPlainDatagramSocketImpl.socketBind(Native Method)
   at java.net.DualStackPlainDatagramSocketImpl.bind0(Unknown Source)
   at java.net.AbstractPlainDatagramSocketImpl.bind(Unknown Source)
   at java.net.DatagramSocket.bind(Unknown Source)
   at java.net.DatagramSocket.<init>(Unknown Source)
   at haven.Session.<init>(Session.java:787)
   ... 3 more


I've browsed your forums but didn't really find anything that helped me.

So far I tried uninstalling and reinstalling, updating Java.
I tried the Ender's client.
I also portforwarded 1870 and 1871.

I hope you can help me.

Re: Crash on application launch.

PostPosted: Wed Jan 23, 2013 6:23 pm
by MagicManICT
This is most definitely a firewall/router issue. Java is unable to bind to the ports necessary. Make sure both your firewall and router are configured correctly (TCP 1871, UDP 1870). If need be, make sure that java.exe (or salem.jar for some firewalls) is allowed to access the appropriate ports and the internet through the firewall. It may be another program is trying to use the same ports and it's conflicting. You shouldn't need to use port forwarding unless necessary for your network connection.

Re: Crash on application launch.

PostPosted: Wed Jan 23, 2013 6:40 pm
by ephemeralkap
Both firewall and the router are configured correctly. Java is allowed through the firewall, and nothing is using the same ports, according to netstat.

Re: Crash on application launch.

PostPosted: Wed Jan 23, 2013 6:54 pm
by MagicManICT
Dang. Afraid you were going to say that. :( At least you know what you're looking for. I'm horrible at trying to describe these things to a non-tech person.

Easiest of the three: What antivirus/firewall is being used? You don't have to mention publicly if you don't want. Comodo and ESET have both recently caused problems with Salem connections. I believe the issue with Comodo was that the game just wasn't launching and a small fix (adding the -xnosplash switch) got things running. ESET at last known status has Salem (and possibly the game servers and Seatribe sites) flagged as malware. I don't recall without digging up an old error report what exactly it was causing the game to do or not do.

Have you looked into security issues such as certificates blocking a connection? I haven't checked Salem's cert personally, but I understand they're using a "self-signed" certificate and it could be causing issues. (Java usually does pop-ups on this, though.) Related could be another Java security setting auto blocking.
Have you checked to make sure nothing is trying to connect through a proxy, or conversely, a proxy connection isn't properly configured?

That's all I can think of at the moment.

Re: Crash on application launch.

PostPosted: Wed Jan 23, 2013 7:34 pm
by ephemeralkap
You're right, I'm not as techy as I should be ;)

Using standard Windows Firewall, windows 7 64bit.
I'm getting no pop-ups with certificates, which I usually would if there were an error or something's getting blocked.

My Chrome did have some VPN's configured, but I wasn't using them and I'm not sure if they were active or not, I removed them and I'll reboot now to see what happens.

Furthermore, is there any way to check if you're running anything through a proxy? I really shouldn't have any, but I'm not sure if I have something under the hood that I don't know off.

Edit: No luck with that.

Re: Crash on application launch.

PostPosted: Wed Jan 23, 2013 8:15 pm
by MagicManICT
I'm not very familiar with Win 7 yet and still run XP on my personal systems (you'd think I was married to it or something). Windows proxy and VPN settings, if I recall right, use the same settings as Internet Explorer. I'm not aware of Chrome changing these, but I could be wrong. (Chrome should keep these settings internal, but I could be way off base here and need to do some homework on it.)

Unless you specifically configured for a proxy, you shouldn't be connecting through one unless you've got malware on your system. You can always check in "Internet Options" in Windows' Control Panel.

Re: Crash on application launch.

PostPosted: Wed Jan 23, 2013 8:29 pm
by ephemeralkap
Alright, I have no Proxies or VPN's, Java was set up to use any proxies in the browser settings, but there's none. Also tried launching the game with java set to connect directly, without the browser settings. Still no luck.
As of malware, I have a scheduled scanner to sort that out, but I'm running a scan just in case.

Dug this up from the netstat though, I don't know if it tells you something

TCP ###.###.1.3:50352 plymouth:http TIME_WAIT
TCP ###.###.1.3:50356 plymouth:http TIME_WAIT
TCP ###.###.1.3:50359 plymouth:http TIME_WAIT
TCP ###.###.1.3:50360 plymouth:http TIME_WAIT
TCP ###.###.1.3:50362 plymouth:http TIME_WAIT
TCP ###.###.1.3:50365 plymouth:1871 TIME_WAIT
TCP ###.###.1.3:50371 plymouth:http TIME_WAIT
TCP ###.###.1.3:50373 plymouth:http TIME_WAIT
TCP ###.###.1.3:50374 plymouth:1871 TIME_WAIT
TCP ###.###.1.3:50375 plymouth:http TIME_WAIT
TCP ###.###.1.3:50376 plymouth:http TIME_WAIT
TCP ###.###.1.3:50377 plymouth:http TIME_WAIT

TCP ###.###.1.3:50382 plymouth:http TIME_WAIT
TCP ###.###.1.3:50385 plymouth:http TIME_WAIT

TCP ###.###.1.3:50395 plymouth:http TIME_WAIT



TCP ###.###.1.3:50409 plymouth:http TIME_WAIT
TCP ###.###.1.3:50414 plymouth:http ESTABLISHED
TCP ###.###.1.3:50416 plymouth:http ESTABLISHED
TCP ###.###.1.3:50418 plymouth:http ESTABLISHED
TCP ###.###.1.3:50419 plymouth:http ESTABLISHED
TCP ###.###.1.3:50420 plymouth:http ESTABLISHED
TCP ###.###.1.3:50421 plymouth:http TIME_WAIT
TCP ###.###.1.3:50422 plymouth:http TIME_WAIT

Re: Crash on application launch.

PostPosted: Wed Jan 23, 2013 11:30 pm
by MagicManICT
Nothing looks unusual with that.

At this point, I'm not sure what else to suggest checking. There's been a few cases of routers being very problematic (involving a specific brand/model). It might be something worth investigating further.

You might try contacting your service provider to see if they can provide any cheap/free tech support. They can sometimes tell you if specific traffic is coming through to them or not or may provide assistance with setup and such.

Re: Crash on application launch.

PostPosted: Thu Jan 24, 2013 2:33 pm
by fiveous
Try restarting your modem, pull the plug out for a few seconds then plug it back in. Who knows.