Port ford sessions won't save port 3389. They reset to 0 and are unusable.
Port ford sessions won't save port 3389. They reset to 0 and are unusable.
Update, I edited the title based on further testing..
Howdy,
Strange one today. Have a user who worked fine yesterday but this morning she can't connect to any of our Port Forward connections. When I check her settings, all of the Destination Ports are showing as 0 instead of 3389. I checked my machine and some others and only hers was showing the problem.
When I opened up the properties she shows 0s for all the ports but when I check the same thing I see 3389. When she opened one up and then clicked OK instead of Cancel, it then wrote the 0's back into the database and broke everything for everyone else.
Any idea what might have caused this?
And is there any way to do a mass edit to change them all back to the proper port? Maybe an Export, CSV modification, and re-import or something?
Attached Problem 1 shows the 0's that should be 3389. Problem 2 shows what it should look like.
rdm port forward problem 2.jpg
rdm port forward problem 1.jpg
All Comments (11)
OK, Now I just found out that if I open up any of my Port Forward sessions and make an edit to any of the entries, everything else then changes to destination port 0. So now all my port forward sessions are broken. :(
OK, more to the story. Any item I edit and put in port 3389 as the Destination won't save. As soon as I close and re-open the setting it has gone back to 0. Please Help. ;)
Hi,
Thanks for reporting the issues, I was able to reproduced the problem. I just transfer the information to the engineering department.
Best regards,
David Grandolfo
Attaching a couple screenshots but it sounds like you verified it. Please let me know if there's any way I can force it to work. This has rendered most of what we use RDM for completely unusable.
Do you have a direct link to the previous version?
Actually, I named the files backwards....
rdm after save.jpg
rdm before save.jpg
Hi,
The problem is only present in RDM 12.9.5, you can download 12.9.4 at the URL below.
https://cdn.devolutions.net/download/Devolutions.RemoteDesktopManager.Bin.12.9.4.0.zip
Best regards,
David Grandolfo
That link is to a zip file and not an installer. Do I just unzip it over the top of my current files?
Hi,
It's an option or you could download the msi files below:
https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.12.9.4.0.msi
Best regards,
David Grandolfo
I extracted the file over the top of mine and it seemed to work fine. Looks like it's only a problem when you save the settings. I was able to fix up our sessions on the .4 version and as long as none of the rest of the people with .5 try to open and modify anything, it should keep the settings safe. I'll wait for a .6 and hope that takes care of it.
Thanks.
Hi,
The engineering department explained me that the problem was reproduced and they will repair it. Probably in the next version or the version after RDM won't have the problem.
Best regards,
David Grandolfo
Any update on this by chance? It's come back up randomly for people and downgrading everyone isn't something I really want to have to do.
Hello,
The issue has been resolved and the fix will be available in the next release of RDM.
However, I cannot provide you any date and time for the delivery of this next beta release.
Sorry about that.
Best regards,
Jeff Dagenais