I was able to connect with 3.0, and then DLed the new version.
Now when I try to connect to the server, I get the the following error.
Any tips?
Network Communicaton Error
Details:
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at VASSAL.chat.HttpRequestWrapper.doGet(HttpRequestWrapper.java:90)
at VASSAL.chat.HttpRequestWrapper.doGet(HttpRequestWrapper.java:47)
at VASSAL.chat.DynamicClient.getServerConfig(DynamicClient.java:65)
at VASSAL.chat.DynamicClient.buildDelegate(DynamicClient.java:55)
at VASSAL.chat.DynamicClient$1.doInBackground(DynamicClient.java:85)
at VASSAL.chat.DynamicClient$1.doInBackground(DynamicClient.java:82)
at org.jdesktop.swingworker.SwingWorker$1.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at org.jdesktop.swingworker.SwingWorker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
I don’t have the version 1.4 of the module. I don’t see this problem when
running 1.5 with VASSAL 3.1.0 or 3.1.1.
No, not that I’m aware of.
I have two guesses as to the cause of what you saw:
You were having a connectivity problem.
You were having some kind of strange Windows problem.
In either case, these should be transient, so my suggestion is to reboot
and see if it works for you now. Then, try upgrading to both the current
versions of VASSAL and the module. If, after doing that, you still have
this problem, let me know so we can investigate further.