Multiplayer BUG! - Printable Version +- 2DWorlds Forums (http://2dworlds.buildism.net/forum) +-- Forum: 2DWorlds (http://2dworlds.buildism.net/forum/forumdisplay.php?fid=4) +--- Forum: Bug Reports (http://2dworlds.buildism.net/forum/forumdisplay.php?fid=23) +--- Thread: Multiplayer BUG! (/showthread.php?tid=7481) |
Multiplayer BUG! - Nice - 07-31-2011 Java-plugin 1.6.0_24 Använder JRE-version 1.6.0_24-b07 Java HotSpot Client VM Användarens hemkatalog = C:\Documents and Settings\erik ---------------------------------------------------- c: töm systemfönster f: slutför objekt i slutföringskö g: skräpinsamling h: visa det här hjälpmeddelandet l: dumpa classloader-lista m: skriv ut minnesförbrukning o: utlösarloggning q: dölj konsol r: ladda policykonfiguration på nytt s: dumpa system- och distributionsegenskaper t: dumpa trådlista v: dumpa trådstack x: töm classloader-cache 0-5: ange spårningsnivån till <n> ---------------------------------------------------- [2011-07-31 18:43:11] Connecting to 97.102.15.242 java.net.ConnectException: Connection timed out: 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 java.net.Socket.<init>(Unknown Source) at java.net.Socket.<init>(Unknown Source) at net.buildism.d.c.<init>(Client.java:64) at net.buildism.object.NetworkClient$5.run(NetworkClient.java:89) at net.buildism.f.p(Main.java:688) at net.buildism.MainApplet.run(MainApplet.java:209) at java.lang.Thread.run(Unknown Source) When I try to join a multiplayer server it says that I can't connect to the server... (Failed to connect to the server) Please could someone tell me what it is 'bout and how can I fix it? RE: Multiplayer BUG! - Jacob__mybb_import1 - 07-31-2011 The server you were trying to connect to might have been down, or the host didn't set up their router/firewall correctly. |