v2023.2.6.2 errors with 0x0000000D when using Duo Network Gateway
Hopefully this doesn't turn in to finger pointing, but RDM v2023.2.5.1 works fine with MacOS 13.4.1(c) and v2023.2.6.2 gives me 0x0000000D when connecting through the RDP proxy that Duo Network Gateway (DNG) provides. Direct RDP connections seem to work fine.
the DNG logs show this
2023-07-13 20:46:25+0000 [HTTPConnection,69,] Using ws spec (draft 17) 2023-07-13 20:46:25+0000 [portal] req_trace_group=fb99188d7504bd116b3734a5 - req_trace=f5794c267a57a7f1c0c0b8ec794f57c3 : Upgraded Connection SID (19c368a4-63a2-4743-8a7c-5ed47e855eca) to websocket 2023-07-13 20:46:25+0000 [portal] req_trace_group=fb99188d7504bd116b3734a5 - req_trace=f5794c267a57a7f1c0c0b8ec794f57c3 : Buffer shrink failed. Ack number is negative. ack: (-1) relay_session.read_count: (19) 2023-07-13 20:46:25+0000 [portal] req_trace_group=fb99188d7504bd116b3734a5 - req_trace=f5794c267a57a7f1c0c0b8ec794f57c3 : Error: Connection SID (19c368a4-63a2-4743-8a7c-5ed47e855eca) Unable to shrink buffer. 2023-07-13 20:46:25+0000 [portal] req_trace_group=fb99188d7504bd116b3734a5 - req_trace=f5794c267a57a7f1c0c0b8ec794f57c3 : calling loseWriteConnection() 2023-07-13 20:46:25+0000 [portal] TCPProtocol: writeConnectionLost 2023-07-13 20:46:25+0000 [portal] TCPProtocol: Lost connection to server. Reason: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion.
Hello
We're tracking a regression on the 2023.6.x release with certain RDP authentication scenarios. Could you check if it's the same issue by setting "Authentication > SSPI > SSPI Module" to "System" on one of the affected entries and let me know if it corrects the issue?
I apologize for the inconvenience. Please let me know if you have a question or something isn't clear
Thanks and kind regards,
Richard Markievicz
bingo. Same issue. Setting "Authentication > SSPI > SSPI Module" to "System" allows it to connect.
Hello again
Thanks for confirmation. I apologize for the regression and the inconvenience caused. We will fix this as soon as possible.
In the meantime, the possible workarounds are:
Once again, I do apologize and assure you we're working hard to correct that.
Please don't hesitate if you have other questions or concerns
Kind regards,
Richard Markievicz
Thanks for the quick response. That makes up for the inconvenience. I've reverted back to 2023.2.5.1 for now.
Hello again
Thank you. We've added this post to the internal trouble ticket and will post an update once we have one.
Thanks again and kind regards,
Richard Markievicz
Hello,
I'm glad to say that the issue has been resolved and will be included in the next update.
While we cannot provide a specific timeframe for the release of the update, rest assured that the resolution is on its way.
Best regards,
Carl Marien
Hello,
Could you try to install the latest update of RDM on your Mac? this new version should resolve the problem you are encountering.
We appreciate your patience and cooperation in working through this matter.
Best regards,
Carl Marien
Just installed 2023.2.7.1 and all my connections work! Thanks for the great communication and quick fix. Love this tool!