Tidtelnet.Disconnect cannot be disconnected about indy HOT 2 CLOSED

DisconnectNotifyPeer() is intentionally empty at the TCP level. It is a virtual method, various protocol-specific descendants override it when they need to send messages to peers while closing connections. But there is nothing in the Telnet protocol to notify a peer about when closing the connection, which is why TIdTelnet does not override DisconnectNotifyPeer(). TIdTelnet overrides Disconnect() itself instead, to shut down its internal reading thread while closing the connection.

Typically, the only way that Connect() would think the socket is already connected after a Disconnect() is if there is unread data left behind in the IOHandler's InputBuffer. Even though the physical socket has been closed, Indy will still allow reads to succeed until the InputBuffer is exhausted. This is by design.

So, to make sure the connection is fully closed, try clearing the InputBufer before calling Connect() again, eg:

IdTelnet1.Disconnect;
if Assigned(IdTelnet1.IOHandler) then
  IdTelnet1.IOHandler.InputBuffer.Clear; // <-- ADD THIS
IdTelnet1.Connect;

from indy.

Thank you! According to the code you provided, it worked!

from indy.