See below post (though you're still welcome to post what router you're using if you're unable to log in since the 5/17 update)
I still can't log in, long form detail heavy [linksys WRT54G issue] [semi solved]
Ok-
Before the update on the 17th, I have been unable to log in from the machine on which I've been playing SK since beta.
I've tried logging in from an XP and a Win 7 machine over the same connection, both get the same error.
Once the client opens, you enter your user name and password, it says 'logging in' and then eventually "you have been disconnected from the server"
I've tried from several accounts, including ones created after the update, all get the same error.
I have-
Uninstalled Spiral Knights
Installed the latest video drivers for my video card
Downloaded the latest java
First validated my firewall settings, then disabled the software firewall entirely
Deleted the app data folder created when you use the 'play' button
Cleared my registry of all spiral knights entries
Rebooted my machine
Rebooted my modem
Rebooted my router
Reinstalled Spiral Knights
From various error logs-
"javaIOE IOE the existing connection was forcibly closed by the remote host"
this is my projectx.log 2011/05/20 13:02:12:138 INFO M$a.a: Logging to 'C:\Program Files\Three Rings Design\Spiral Knights\.\projectx.log'. Loading: net.java.games.input.DirectAndRawInputEnvironmentPlugin 2011/05/20 13:05:38:216 INFO M$a.a: Idle state changed. [idle=true] 2011/05/20 13:07:29:028 INFO M$a.a: Idle state changed. [idle=false] 2011/05/20 13:07:42:653 INFO M$a.a: Connecting [host=game.spiralknights.com/184.73.192.155, port=47624] 2011/05/20 13:07:43:403 INFO M$a.a: Datagram connection established [port=47624] 2011/05/20 13:10:05:247 INFO M$a.a: Connection failed java.io.IOException: An existing connection was forcibly closed by the remote host at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at com.threerings.io.r.a(SourceFile:106) at com.threerings.projectx.client.A.l(SourceFile:107) at com.threerings.presents.client.BlockingCommunicator.k(SourceFile:486) at com.threerings.presents.client.BlockingCommunicator$c.c(SourceFile:699) at com.samskivert.util.W.run(SourceFile:60) 2011/05/20 13:10:05:247 INFO M$a.a: Connection failed java.io.IOException: An existing connection was forcibly closed by the remote host at sun.nio.ch.SocketDispatcher.write0(Native Method) at sun.nio.ch.SocketDispatcher.write(Unknown Source) at sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.write(Unknown Source) at sun.nio.ch.SocketChannelImpl.write(Unknown Source) at com.threerings.presents.client.BlockingCommunicator.b(SourceFile:399) at com.threerings.projectx.client.A.b(SourceFile:73) at com.threerings.presents.client.BlockingCommunicator$d.c(SourceFile:783) at com.samskivert.util.W.run(SourceFile:60) 2011/05/20 13:10:05:419 WARNING M$a.a: Invocation director unable to subscribe to client object [cloid=13374, cause=com.threerings.presents.dobj.ObjectAccessException: Client connection closed]!] 2011/05/20 13:11:18:216 INFO M$a.a: Idle state changed. [idle=true] 2011/05/20 13:24:18:638 INFO M$a.a: Idle state changed. [idle=false]
Here is a project x log from the same account on a different network
2011/05/20 19:27:39:594 INFO M$a.a: Logging to 'C:\Program Files\Three Rings Design\Spiral Knights\.\projectx.log'.
Loading: net.java.games.input.DirectAndRawInputEnvironmentPlugin
2011/05/20 19:27:51:469 INFO M$a.a: Connecting [host=game.spiralknights.com/184.73.192.155, port=47624]
2011/05/20 19:27:52:297 INFO M$a.a: Datagram connection established [port=47624]
2011/05/20 19:28:02:406 INFO M$a.a: Connecting [host=game.spiralknights.com/184.73.192.155, port=47624]
2011/05/20 19:28:03:265 INFO M$a.a: Datagram connection established [port=47624]
2011/05/20 19:28:06:218 INFO M$a.a: Moving at request of server [zoneId=16777217, sceneId=3]
2011/05/20 19:28:06:453 WARNING M$a.a: Failed to find property. [name=portal, object=[actor=null, location=[]]]
2011/05/20 19:28:06:453 WARNING M$a.a: Failed to find property. [name=scene_id, object=[actor=null, location=[]]]
2011/05/20 19:28:06:453 INFO M$a.a: Issuing zoned moveTo(1:1, 3, 26).
2011/05/20 19:28:06:687 INFO M$a.a: Connecting [host=/50.17.57.74, port=47629]
2011/05/20 19:28:07:500 INFO M$a.a: Datagram connection established [port=47629]
2011/05/20 19:28:08:156 INFO M$a.a: Issuing zoned moveTo(1:1, 3, 26).
2011/05/20 19:28:08:578 INFO M$a.a: Updating outgoing message throttle [msgsPerSec=15]
2011/05/20 19:28:22:062 WARNING M$a.a: Long invoker unit [unit=News Reader (class com.threerings.projectx.client.at), time=2344ms].
Having tried EVERYTHING else I could think of or was suggested, I pulled my router and connected directly to my modem, which is a 'dumb box' aka cannot be logged into or have settings, no firewall, etc.
And I can log in %$#*@!
I go BACK to my last response from support
"Cronus - May 20 at 4:26am:
I just wanted to take a moment to let you know that we're still looking into this. While we do that, I'd suggest that you take a moment to check if your firewall might be causing your difficulty. I know that it's possible you've done this already, but it never hurts to try another tactic. Default Windows XP Firewall: Add 'java.exe' and 'javaw.exe' to the list of allowed programs/exceptions. Hardware Firewall/Router: Make sure traffic is allowed on ports 47624 through 47634 inclusive on both TCP and UDP. Other Firewall Programs: Make sure the game server addresses are not blocked. There are too many game servers to list, but some sample addresses are: 184.73.192.155, 184.73.171.119, 50.17.200.213."
I mess around with my router, I add all the exceptions, I even forwarded the ports to my machine. I update the firmware on my router, I reset it to factory defaults..
Can't log in &%$#*@!
So I get an OLD OLD router without wireless capabilities (note- my connection has always been wired) out of storage and plug it in.
And I can log in %$#&*@!
I copy all the settings from the old router to the new router
And I can't log in &%$#*@!
There is no reason that this one model of router should be borked and the only thing I know is that I could play fine with this setup before the 5/17 update
For reference, I have the Linksys WRT54G, same as this user
This user also has the same router with the same error.
Im having the exact same issue as well.
Beryl- The exact same as Korobugs router.
I fixed mine, I don't recommend it tho- I installed linux on my router...it's something with this model...
![Dogrock's picture Dogrock's picture](https://forums.spiralknights.com/sites/default/files/avatar_selection/sk_fan11.png)
Questions:
What is the revision on the router? You'll find it under the sticker with the model.
Did you by chance install DD-WRT as your Linux?
The WRT54G(S/L) is a great series of router, but I haven't used the stock firmware on it in ages since DD-WRT completely blows it out of the water in terms of... well every metric.
Version 6, and yes, I installed DD-WRT
Mine is Version 6 as well.
Edit; sorry, I guess impatience leads to a double post on these forums ^^;
![Dogrock's picture Dogrock's picture](https://forums.spiralknights.com/sites/default/files/avatar_selection/sk_fan11.png)
Version 6 is when Cisco systems started shipping with a different OS installed. This Lasted for another two full revisions until Cisco realized that no one liked the new setup very much. Basically, if had a very short support life and received few updates.
DD-WRT is a great firmware to use on these devices and if you understand the risks of flashing your device I recommend it if no other option works for log in errors. I've set up more than a few WRT54G's and WRT54GL's with DD-WRT for people, the devices will chug along for years.
I flashed my WRT54G2 today and installed DD-WRT. Am now able to log into the game again.
But this is definitely not a good solution to the problem for the average Spiral Knights player using these Cisco routers!
It's Cisco's fault for writing such terrible firmware. >_<
I stopped buying from them a long time ago because of their terrible support...
Were you all able to play through just an ethernet connection to your modem, no router at all? That might be an inelegant but simpler solution for less savvy players.
Have you tried daisy-chaining the wireless router to the wired router, which is then connected to the modem and your PC? That should still allow you to get an outbound on the wireless while letting you play SK without messing with the firmware...
Or it could just be more complicated. Depends on how many CAT 5 cables you have lying around.
I was able to log in directly through my modem as above, but it's a 'dumb box' so no hardware firewall >.<
Also, I'm guessing most users (like me) have other people in their houses who want to use the internet.
I did consider daisy chaining routers, making the wireless into a wap instead and using the wired as my router, but the linux install happened instead.
Regardless of Cisco's 'terrible firmware', I and other players with this router could play before the 5/17 update, and none of these solutions are anything that a company should be expecting their players to do.
We should plug in, download and play like everyone else. Anything else is bad customer relations.
Same issue, same router. Plugging in directly works, but as you can guess this inconveniences other members of the house-hold. Not looking forward to flashing the router. Any updates on this issue?
![Dogrock's picture Dogrock's picture](https://forums.spiralknights.com/sites/default/files/avatar_selection/sk_fan11.png)
The Dev team have acknowledged the issue and are looking into this problem.
![Eurydice's picture Eurydice's picture](https://forums.spiralknights.com/sites/default/files/avatar_selection/sk_admin5.png)
Yep, this is on the radar. If you could email support@spiralknights with the log files from your game directory attached, that would be a great help.
This data would be useful, but you really should try to keep your problem to one thread if it is indeed the same issue as earlier. I understand your frustration, but if you could provide us with more information about YOUR problem, instead of just asking about others (who obviously didn't follow the instructions in your last thread) we could start looking for solutions.