Help with Bitvise SSH Add On
Hi all, I've installed the Bitvise SSH add-on and created Sessions that use my existing Bitvise client profiles. When logging into a saved profile with SSH using the actual Bitvise client, I clicked "Accept and Save" for Host Key Verification and I'm no longer prompted. However, when using a session in RDM using the same profile, I'm prompted for it again and "Accept and Save" is greyed out.
I also have the Bitvise SSH profiles set to open RDP automatically once SSH is connected. However, in RDM, the RDP session opens fullscreen. In the options of the Bitvise session, it's set to External and I'm unable to change it. I guess this is because it's a Bitvise connection and it doesn't need the option to be embedded..?
Unfortunately, the SSH client gets the RDP port info from the server once SSH is established so I can't configure a separate RDP session in RDM and choose to use an existing session because I don't know what port(s) to use. Probably no way around this, it's just one of those things.
All Comments (3)
Hello,
For the Host Key Verification being prompted every time, try checking the "Use Registry" checkbox in RDM. When it's checked, I don't encounter your problem. The saving of the verification is probably saved in the registry.
Could you provide a screenshot of what your Bitvise profile looks like in the Remote Desktop tab? I'm not sure what you mean by "external" and not being able to change it. If I input a width and a height and uncheck fullscreen (which is what I assume you mean by external), it works perfectly fine in RDM when loading this profile for me. Same thing when checking fullscreen.
As for the last part, I don't think there is a way to get the port number for use in RDM.
Regards,
Hubert Mireault
Hi Hubert,
Thanks for that. Ticking the "Use Regsistry" checkbox did the trick for that.
With regard to having the RDP sessions in tabs instead of external, I don't think I explained it very well sorry. I've setup the Sessions as Btivise SSH Client ones using the *.bscp profiles from the actual SSH client. These are set to open remote desktop automatically but it goes full screen\external and there's no way of changing that in the session properties. I guess this is because it's not an actual RDP session I'm using?
Since the actual SSH client gets the port forwarding info from the Winsshd running on the servers (and uses random ports it seems), I can't use an RDP session and like you said, there's probably no way of passing the port number from the client to the RDP session. Hope that makes sense :)
Hello,
Thank you for clarifying. Sadly, I don't think it's possible to set if you want the RDP connection to open in fullscreen or in external because the command line parameters don't include anything relating to that. It would be a good feature to implement as soon as the command line supports it.
Regards,
Hubert Mireault