3.1 Autoreconnect loop


Just upgraded to 3.1...and now when I log off it re-connects me to these sessions.

I have enabled show confirm dialog on disconnect, and I have told the conenction not to re-connect and not to show again, and it still re-connects!!!!
Closed Aug 7, 2013 at 4:18 PM by jirkapok


digitlman wrote Jul 17, 2013 at 12:24 PM

Let me clarify - I am RDPing into these PCs.

I am manually logging off them (start - log off).

I have told Terminals not to re-connect and it always does.

digitlman wrote Jul 17, 2013 at 12:29 PM

ERROR 2013-07-17 08:28:36,299 27911ms Terminals lient_OnLogonError - There was a logon error returned from the RDP Connection, details:

Logon Code:-2

Logon Description:Winlogon is continuing with the logon process.

This is all I can find in the logs.

digitlman wrote Jul 17, 2013 at 12:34 PM

Sorry to spam, but here is some further testing.

I confirmed that I have both the "show confirm on close or warn on disconnect" and "ask to reconnect when connection is lost due to Shutdown or reboot (RDP only".

I log into the PC, and then log off normally. Terminals asks if I want to try and reconnect. I say No and check do not show again. Everything is fine.

The next time I log into the same PC, and log off normally, Terminals then autoreconnects without any dialog box.,

Furthermore, the ask to reconnect when connection is lost due to Shutdown or reboot (RDP only". is unchecked again!

This is a (files Store) install.

Please fix!

nielsvdc wrote Jul 17, 2013 at 8:18 PM

Hi Jiri. The problem is in RDPConnection.cs > DecideToReconnect. && should be ||
private static bool DecideToReconnect(IMsTscAxEvents_OnDisconnectedEvent e)
     // 516 reason in case of reconnect expired
     // 2308 connection lost
     // 2 - reboot or shutdown
    if (e.discReason != 2308 && e.discReason != 2)
        return false;

digitlman wrote Jul 22, 2013 at 11:30 AM

Will there be a fix for this soon?

jerryjerry wrote Jul 23, 2013 at 3:36 PM

I can confirm this behavior....
Any Updates on a fix or a workaround?
With this bug noone can use terminals anymore:(

jirkapok wrote Jul 23, 2013 at 6:19 PM

@Niels: No, it is not so funny. The RDP gives the reason = 2 for both usual logout and also for forced logout because of restart or shutdown.
Workaround: Dont use regular logout, use the connection tab close button.

digitlman wrote Jul 23, 2013 at 7:02 PM

This is still a bug.

Please re-read my notes and fix.

nielsvdc wrote Jul 24, 2013 at 8:01 AM

@Jiri, the problem is that if you do a clean logoff via the startbutton, the remote session should logoff and not reconnect. Disconnecting using the tab close button is not an option. Clean logoff should be available.

jirkapok wrote Jul 24, 2013 at 8:49 PM

I know, that it is not an option, that is only a workaround (we don't have better one). I will check in solution in a while.

wrote Jul 24, 2013 at 9:49 PM

Associated with changeset 103495.

wrote Jul 24, 2013 at 9:53 PM

Associated with changeset 103496.

CajunBoy wrote Jul 25, 2013 at 2:06 PM

I had the same issue. I uninstalled v3.1 and deleted the install directory. I installed v3.0 and imported the favorites from registry. The loop went away and I'll wait until the issue is fixed before upgrading.

jirkapok wrote Jul 25, 2013 at 7:45 PM

Please tests the latest state, so can be sure i didn't forget anything.

digitlman wrote Jul 25, 2013 at 7:57 PM

I installed the latest binaries from today and it is working properly now.

tinkerman wrote Jul 25, 2013 at 11:53 PM

Still having this issue. Just installed 3.1.
@digitlman: If you updated the binaries - dare to share how you did it?

digitlman wrote Jul 26, 2013 at 11:39 AM

Back up Terminals dir, downloaded binaries, extracted zip, copied into Terminals dir and overwrote. re-launched program.

Went into the options and unchecked show confirm dialog on close and ask to reconnect.

Works fine now.

gonzalocontento wrote Jul 26, 2013 at 2:51 PM

I compared the binaries and they are the same. Just for fun, I overwrote them like you mentioned but no change at all (of course).
@digitlman: did you downloaded them from the official link?

xenoranger wrote Jul 29, 2013 at 2:33 PM

I have confirmed the same issue in Terminals 3.1.0.

The only work around I have found is to log off then quickly close the tab. It's dirty, but it works.

kenoten wrote Jul 29, 2013 at 7:27 PM

Where are the binaries to download for a workaround to this issue? Is the official link going to be updated soon?

I have disconnected sessions online all over the place due to this bug. Looks like I am spending this afternoon RDP'ing into them the old fashioned way just to log off each of them.

jirkapok wrote Jul 30, 2013 at 9:23 PM

To test the fix, you have to download and use the latest nightly build binaries. Link can be found in documentation - developer guide.

gonzalocontento wrote Jul 31, 2013 at 6:00 PM

Confirmed! it is working well. I downloaded the nightly build from http://goo.gl/bTlqr
Much appreciated.

Zoltanar wrote Aug 1, 2013 at 1:49 PM

I also confirm that downloading the latest build (from the 28th of July I believe) and only replacing my existing EXE fixed the issue.
Only issue I can still see is the occasional lockup of a terminal window...but it already is far better now :D Thanks for your hard work and such a great tool!

Zoltanar wrote Aug 1, 2013 at 3:51 PM

..Actually - I am now facing something else : when I try to add a new RDP connection to my favorite list, it whypes my favorites.xml file, and therefore I loose all connections saved.
I am glad I had a backup of that file because of the 100s items I have in there.
I am not sure if this bug was part of the latest build I downloaded, or if it was already present before - it's been a while I didn't have to add a new server.

Anyone else have this issue?
BTW, I am running it in Portable mode, so the config files are under the Data sub folder of the install directory. Also, make sure you sometimes make a backup of these XML files - they hold all your configurations!

Zoltanar wrote Aug 1, 2013 at 3:57 PM

I can confirm that my backup of version 3.0 also does the same thing - it whypes my favorite.xml file as well.

varismii wrote Aug 5, 2013 at 8:52 AM

I have this problem too. Just installed few days ago. I quick fix would be appreciated, as I use this tool daily for customer support work. Great tool BTW!