0001896: 2nd login attempt problems in client 2.0.3.

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001896

SphereServer

executable - generic

public

23-01-11 17:19

23-01-11 17:57

Reporter

Mirravin

Assigned To

Priority

normal

Severity

minor

Reproducibility

always

Status

closed

Resolution

not fixable

Platform

Windows / Linux

OS Version

Product Version

Target Version

Fixed in Version

Summary

0001896: 2nd login attempt problems in client 2.0.3.

Description

If you enter an incorrect password on login in client 2.0.3, on 2nd login attempt you get a "Verifying Account" and can't login without client restart. Problem NOT occurs in client 6.0.14.3.
Client encryption, UseAsyncNetwork, UsePacketPriority, EF_NetworkOutThread don't make a difference.

Steps To Reproduce

1) 1st login attempt with incorrect password:
18:12:DEBUG:Receiving new connection
18:12:DEBUG:Retrieving IP history for '127.0.0.1'.
18:12:DEBUG:Incoming connection from '127.0.0.1' [blocked=0, ttl=300, pings=0, connecting=0, connected=0]
18:12:DEBUG:0:Allocated slot for client (376).
18:12:DEBUG:0:Clearing client state.
18:12:DEBUG:0:Initialising client
18:12:0:Client connected [Total:1] ('127.0.0.1' 1/1)
18:12:DEBUG:0:Opening network state
18:12:DEBUG:0:Determining async mode
18:12:DEBUG:0:State initialised, registering client instance.
18:12:DEBUG:0:Client successfully initialised.
18:12:DEBUG:0:Receiving old client login handshake.
18:12:DEBUG:0:Client connected with a seed of 0x4f8459b0 (new handshake=0, seed length=4, received=66, version=0x0).
18:12:0: 'abc' bad password
18:12:ERROR:0:Bad Login 3 (The password entered is not correct)
18:12:DEBUG:0:Client being closed by read-thread
18:12:DEBUG:0:Flushing data for client.
18:12:DEBUG:0:Client being closed by read-thread
18:12:DEBUG:0:Client being closed by write-thread
18:12:DEBUG:0:Client is being cleared since marked to close.
18:12:DEBUG:0:Clearing client state.
18:12:0:Client disconnected [Total:0] ('127.0.0.1')

2) 2nd login attempt with correct password:
18:13:DEBUG:Receiving new connection
18:13:DEBUG:Retrieving IP history for '127.0.0.1'.
18:13:DEBUG:Incoming connection from '127.0.0.1' [blocked=0, ttl=208, pings=1, connecting=0, connected=0]
18:13:DEBUG:1:Allocated slot for client (372).
18:13:DEBUG:1:Clearing client state.
18:13:DEBUG:1:Initialising client
18:13:1:Client connected [Total:1] ('127.0.0.1' 1/1)
18:13:DEBUG:1:Opening network state
18:13:DEBUG:1:Determining async mode
18:13:DEBUG:1:State initialised, registering client instance.
18:13:DEBUG:1:Client successfully initialised.
18:13:DEBUG:1:Receiving old client login handshake.
18:13:DEBUG:1:Client connected with a seed of 0x4f8459b0 (new handshake=0, seed length=4, received=4, version=0x0).

3rd and next login attempt:
NOTHING IN CONSOLE.

Issue History
Date Modified	Username	Field	Change
23-01-11 17:19	Mirravin	New Issue
23-01-11 17:57	MrSugarCube	Note Added: 0000862
23-01-11 17:57	MrSugarCube	Status	new => closed
23-01-11 17:57	MrSugarCube	Resolution	open => not fixable

Notes
(0000862) MrSugarCube (administrator) 23-01-11 17:57	This is a bug with the 2.0.3 client. After a failed login attempt it does not send any data to the server on subsequent attempts (you have to restart the exe).

Relationships