Orga1 Posted November 17, 2010 Report Share Posted November 17, 2010 I have trouble logging in, get stuck at log in and then reboot, oh no what next after the reboot? lost connection to global server, the solution Reboot again. Finally get in to server fly to 1st gate and wouldn't you know it CRASH with only a repetitive old stooped error called DoKeyExchange 63, because I believe your port 3810 is really messed up your welcome. Server was at only 24% full and I was in between logging in at a station and flying in space, when all happened. Another words it dominoed. Now why am I posting this because b4 the recent content update, I believe my connection to the server was more stable then it is now...I haven't seen this error sense ST3&ST2. Of course no one is diagnosing it, but it's very annoying error to encounter when I'm in the game. 16/11/10 18:34:17 ---> Server handoff 16/11/10 18:34:17 Received Master login confirm, new UDP port is 3532 Avatar_id = 1073743358 16/11/10 18:34:17 <server> Master Login received - UDP sector port: 3532 16/11/10 18:34:17 >> Commence Login check. 16/11/10 18:34:17 TCP connection on port 3811 closed gracefully 16/11/10 18:34:17 ERROR: DoKeyExchange key_length = 63 16/11/10 18:34:17 >>> Connection verification failed, restart all connections. 16/11/10 18:34:17 Client key exchange failed. Connection thread exiting 16/11/10 18:34:19 TCP connection on port 3810 closed gracefully 16/11/10 18:34:22 TCP Listener unable to bind to socket on port 3810 16/11/10 18:38:29 MVAS thread running 16/11/10 18:38:30 Received Master login confirm, new UDP port is 3532 Avatar_id = 1073743358 16/11/10 18:38:30 <server> Master Login received - UDP sector port: 3532 16/11/10 18:38:30 >> Commence Login check. 16/11/10 18:38:30 Sending Login packet - connection active 16/11/10 18:39:33 ---> Server handoff 16/11/10 18:39:33 Received Master login confirm, new UDP port is 3659 Avatar_id = 1073743358 16/11/10 18:39:33 <server> Master Login received - UDP sector port: 3659 16/11/10 18:39:33 >> Commence Login check. 16/11/10 18:39:33 TCP connection on port 3500 closed gracefully 16/11/10 18:39:33 Sending Login packet - connection active 16/11/10 18:39:35 Sending data file 'GalaxyMap.dat' 16/11/10 18:39:36 Sending StartAck to Server 1534 16/11/10 18:39:38 >> Login check: Login OK 16/11/10 18:45:44 ---> Server handoff Quote Link to comment Share on other sites More sharing options...
Tienbau Posted November 17, 2010 Report Share Posted November 17, 2010 once you see this: ERROR: DoKeyExchange key_length = 63 it's best to restart completely. Terminate Net7Proxy and then the client should go back to Megan, and then shut it down. If the client doesn't terminate use Task Manager, go to processes and end the 'client.exe' process. Don't try to terminate it from the 'applications' tab because that doesn't always work. I have been trying to rectify this problem but so far with limited success. Quote Link to comment Share on other sites More sharing options...
Orga1 Posted November 17, 2010 Author Report Share Posted November 17, 2010 OK just a thought, you how I crashed 3 times in a row? Well possible I was dealing with 2 different bugs and the 1st was the DoKeyExchange error, followed up by a different pattern the double crash/disconnect on log-in screen alone. That has a pattern to it but I don't think the DoKeyEchange error, that appears on the proxy when i gate to desktop lol is linked with the double crash/ disconnect at the log-in screen. I don't know if this helps but it could narrow the problem. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.