Forum

Posts by jlafontaine (jlafontaine)

jlafontaine
jlafontaineDevolutions staff
Posts: 134

I'll try to replicate on my side nonetheless and if you encounter any keyboard issues in the next release, let me know.

Jonathan Lafontaine

signaturesignature

9 days Shift key doesn't work over Apple Remote Desktop (Mac OS Catalina)
jlafontaine
jlafontaineDevolutions staff
Posts: 134


Hi,

The shift key issue has been fix internally and should be available in the next release.
Do you have an example control key combination that is currently not working?
I could try to replicate the issue on our side.

Jonathan Lafontaine

signaturesignature

9 days Shift key doesn't work over Apple Remote Desktop (Mac OS Catalina)
jlafontaine
jlafontaineDevolutions staff
Posts: 134


Hi,

Yes, so far, I've only been able to reproduce this issue on Catalina.

I can confirm that connecting with a standard VNC client or RDM with a VNC session does work.
However, in that case, the ARD protocol is not used.
The ARD protocol brings a couple of improvements over the standard VNC connection

- encrypted inputs
- optimized image encodings.
I'm actively working on it but as ARD is a closed protocol, this is not an easy task.

Jonathan Lafontaine

signaturesignature

13 days Shift key doesn't work over Apple Remote Desktop (Mac OS Catalina)
jlafontaine
jlafontaineDevolutions staff
Posts: 134


hi axaeaxam



I will update the DSM plugin in RDM to the version distributed by UltraVNC.



As for your other issue, I think we already support it.
While connected to a UltraVNC server using the RDM viewer, right click on the connection's tab, and click on "Select Full desktop/ Switch Monitor" in the Special Command sub menu.


Regards

Jonathan Lafontaine

signaturesignature

4 mths Update RDM to latest UVNC to latest version and features
jlafontaine
jlafontaineDevolutions staff
Posts: 134


Hi,

Thank you for sharing the vm with us.
I was able to reproduce 2 of your issues and fix them.
Point 'a' and 'b' should now be working properly.

I was not able to reproduce point 'c' but fixes for text selection might have fixed this point too.
If you still encounter problems when the screen is locked, let me know.

A beta version that hopefully solves your issues should be available our website later today.

Regards

Jonathan Lafontaine

signaturesignature

5 mths Embedded VNC: Unable to highlight text on the default text editor.
jlafontaine
jlafontaineDevolutions staff
Posts: 134

Let me know the outcome.

Jonathan Lafontaine

signaturesignature

6 mths KVM & Intel AMT
jlafontaine
jlafontaineDevolutions staff
Posts: 134


Hi Kevin,

Would it be possible for you to post a screenshot of Mesh Commander's system status page?
Also, have you tried connecting from RDM with a ATM or VNC session?

The port used will vary depending on how your server is configured.
A server configured for encrypted port redirection will use port 16995.
A server configured for unencrypted port redirection will use port 16994.
A server configured without port redirection will use port 5900.

Port redirection, encrypted or not, is the preferred method if I'm not mistaken.

Jonathan Lafontaine

signaturesignature

6 mths KVM & Intel AMT
jlafontaine
jlafontaineDevolutions staff
Posts: 134


I'll take you up on that vm offer.
If we are able to reproduce your issue before you have time to work on a vm, I'll let you know.

Regards

Jonathan Lafontaine

signaturesignature

6 mths Embedded VNC: Unable to highlight text on the default text editor.
jlafontaine
jlafontaineDevolutions staff
Posts: 134


Hi,

I've tried to replicate your issue on what I have available but, unfortunately, was not able.
My setup does not match yours so I've ask your IT department to build a server as close to your specs as possible.
That being said, would it be possible for you to provide a restricted access to one of your server?
That might be the easiest way to me to replicate your issue.

Regards

Jonathan Lafontaine

signaturesignature

6 mths Embedded VNC: Unable to highlight text on the default text editor.
jlafontaine
jlafontaineDevolutions staff
Posts: 134

I'll look into that.

Jonathan Lafontaine

signaturesignature

6 mths Embedded VNC: Unable to type special character which require pressing ALT+KEY
jlafontaine
jlafontaineDevolutions staff
Posts: 134


I know my setup doesn't match yours completely but here's what I have:

TigerVNC server running as a service on a Windows 10 host.
Italian layout locally and remotely.

Connecting with RDM default viewer, AltGr+ò doesnt print @.
I had to restart my vnc server before I was able to make this combination. Looks like sending the wrong key combination (normal alt+ò) screwed my server.

If you have not already, could you please try to restart your vnc server and try again?

Jonathan Lafontaine

signaturesignature

6 mths Embedded VNC: Unable to type special character which require pressing ALT+KEY
jlafontaine
jlafontaineDevolutions staff
Posts: 134

What is your local keyboard layout?

Jonathan Lafontaine

signaturesignature

6 mths Embedded VNC: Unable to type special character which require pressing ALT+KEY
jlafontaine
jlafontaineDevolutions staff
Posts: 134

What version was RDM updated to?

Jonathan Lafontaine

signaturesignature

6 mths Embedded VNC: Unable to type special character which require pressing ALT+KEY
jlafontaine
jlafontaineDevolutions staff
Posts: 134


Hi,

I was able to reproduce and fix your issue.
The next release should let your correctly use alt-gr key combinations.

To fully support alt-gr, your VNC session should be set to apply windows key combinations on the remote computer.
To do so, in the "Advanced" tab of the VNC session properties, set "Apply Windows key combinations" to "On the remote computer".

Let me know if you have any questions or experience any other problems with the alt-gr key.
Regards

Jonathan Lafontaine

signaturesignature

6 mths Embedded VNC: Unable to type special character which require pressing ALT+KEY
jlafontaine
jlafontaineDevolutions staff
Posts: 134


Hi,

Thank you for the detailed explanation.
I will look into this issue.

Regards

Jonathan Lafontaine

signaturesignature

6 mths Embedded VNC: Unable to type special character which require pressing ALT+KEY
jlafontaine
jlafontaineDevolutions staff
Posts: 134


Hi,

I tried to replicate this issue but so far i've been unsuccessful.

My test setup.
Ubuntu 18.04 running MATE.
tigervnc 1.9 started with x0vncserver

Is there anything else I should have done to match your setup?

Jonathan Lafontaine

signaturesignature

6 mths Embedded VNC and Mate environment: Stuck on the first connection if screen is locked
jlafontaine
jlafontaineDevolutions staff
Posts: 134

Hi Brian,

In your entry settings, under the Advanced tab, have you set 'Apply Windows key combinations" to "On the remote computer"?
It might be what you are referring to by "all captured or none captured".

Setting it to "On the remote computer" should let you use any Meta+key combination on the remote computer reliably.
If it is not the case, let me know and I will investigate your issue.

As for the scroll wheel not doing anything, I was not able to reproduce on my end.
If you have physical access, could you validate that scrolling is working locally?

Regards

Jonathan Lafontaine

signaturesignature

12 mths Keyboard shortcuts via ARD from Windows
jlafontaine
jlafontaineDevolutions staff
Posts: 134

Hello,

Concerning Internal VNC, I was able to reproduce and fix the keyboard and Caps/Num lock issues.
These fixes will be included in the next release available soon.

Regards

Jonathan Lafontaine

signaturesignature

12 mths Embedded VNC fails to start
jlafontaine
jlafontaineDevolutions staff
Posts: 134

Hi Pedro,

I couldn't reproduce your issue using our Server Core instance.
Would it be possible for you to send us your RDP logs?
You can enable logging in the Session Logs dialog, located in the help menu.
Make sure your Server Core has sandboxing turn on as this will generate a log only for the this particular session.

Also, are you aware if any settings in link with display or graphic modes was changed on the server?

Regards

Jonathan Lafontaine

signaturesignature

2 yrs Remote access to Server Core does not work
jlafontaine
jlafontaineDevolutions staff
Posts: 134

Hi Luciano,

I was wondering what VNC server you were connecting to?

Jonathan Lafontaine

signaturesignature

2 yrs Couldn't use Numlock
jlafontaine
jlafontaineDevolutions staff
Posts: 134

Hi Patrick,

I've done some more testing today with the vPro and a standalone RealVNC server.
Unfortunately, short of reversing VNC protocol 4.0, there doesn't seem to be anything we can do to solve this issue.
Event VNC Viewer+, once limited to protocol version 3.3, cannot correctly handle the different layouts anymore.

I will add reversing of the 4.0 protocol to our R&D todo list but can't provide a time frame as to when it's gonna be tackled.

Jonathan Lafontaine

signaturesignature

2 yrs VNC Keyboard Layout (Intel AMT)
jlafontaine
jlafontaineDevolutions staff
Posts: 134

That's unfortunate.

I hope my test with the RealVNC Server will yield some useful information.

Jonathan Lafontaine

signaturesignature

2 yrs VNC Keyboard Layout (Intel AMT)
jlafontaine
jlafontaineDevolutions staff
Posts: 134

Click the blue text beside Remote Desktop.

Jonathan Lafontaine

signaturesignature

2 yrs VNC Keyboard Layout (Intel AMT)
jlafontaine
jlafontaineDevolutions staff
Posts: 134

Once connected, on the System Status page, you should see a line related to port 5900 or legacy mode with blue text next to it.
If you click the blue text, it will open the settings dialog for this particular option and let you enable it.

Jonathan Lafontaine

signaturesignature

2 yrs VNC Keyboard Layout (Intel AMT)
jlafontaine
jlafontaineDevolutions staff
Posts: 134

Technically, the way VNC is designed, the server should change it's protocol to match the client.
We advertise version 3.8 to AMT but since it's a licensed product, it's possible they ignore it.

I think I have a RealVNC Server license at work, I could install one to see if I can get the same behavior.
Something else you could try is turning on the legacy mode on vPro.
Using MeshCommander, you can activate the port 5900 to use any vnc client to connect.
Not all AMT features are supported in this mode but it would be a good test.
Unfortunately, when I tried to enable this mode on my device earlier today, MeshCommander return error 400: cannot set value, so looks like it's a test I will not be able to replicate.

Jonathan Lafontaine

signaturesignature

2 yrs VNC Keyboard Layout (Intel AMT)
jlafontaine
jlafontaineDevolutions staff
Posts: 134

Yes, I've tested on a proper vPro vnc server.
I'm not at work and can't validate the AMT version right now but if definitely behave differently than a normal VNC Server.

Jonathan Lafontaine

signaturesignature

2 yrs VNC Keyboard Layout (Intel AMT)
jlafontaine
jlafontaineDevolutions staff
Posts: 134

I've tested with a regular vnc server, ultra vnc in this case, and almost all combinations have the right output so I don't think RDM is sending the wrong keys.
But it's possible that some settings, only available in protocol version 4.0, can change what layout the server expects.

Jonathan Lafontaine

signaturesignature

2 yrs VNC Keyboard Layout (Intel AMT)
jlafontaine
jlafontaineDevolutions staff
Posts: 134

Here's the top row on a US keyboard: !@#$%^&*()_+
When my layout is US and the vPro is Swiss German, I get °+"*ç%&/()=?`

Anything else I've tried so far gives me something like `à(%/_)=`_°

Yes, I'm talking about he language options in the Windows settings. Did this impact your results in any way?


So far, wireshark confirmed that I'm sending the same key code as VNC Viewer+ for most keys.
What's weird is that you experience no problem when a Swiss German keyboard layout is used on both side but I do.

Jonathan Lafontaine

signaturesignature

2 yrs VNC Keyboard Layout (Intel AMT)
jlafontaine
jlafontaineDevolutions staff
Posts: 134

I added the Swiss German keyboard layout to the English (United States) language options.
I then connected with different layout combinations from both RDM and VNC Viewer+ and typed the number row shifted and compared the results.

I started looking at wireshark captures to figure out what VNC Viewer+ is sending vs RDM.
VNC Viewer+ being the official vPro viewer uses vnc protocol 4.0 which is not publicly available, RDM uses vnc protocol 3.8.

As for a workaround, you could instead use a standard vnc session set to external and configure VNC Viewer+ as the VNC application.
Command line arguments for the entry would look like this "-uri kvm://<username>:<password>@<host_computer>"

Jonathan Lafontaine

signaturesignature

2 yrs VNC Keyboard Layout (Intel AMT)
jlafontaine
jlafontaineDevolutions staff
Posts: 134

Hi Patrick,

I've done a bit more testing with VNC Viewer+ and here's what I've got.

VNC Viewer+ with a Swiss German local layout connecting to a vPro using a Swiss German Layout, most special characters are wrong.
RDM with a Swiss German local layout connecting to a vPro using a Swiss German Layout, most special characters are also wrong but not necessarily the same.


VNC Viewer+ with a Swiss German local layout connecting to a vPro using a US Layout, most special characters are wrong.

RDM with a Swiss German local layout connecting to a vPro using a US Layout, I have mostly the same output with some minor differences.

VNC Viewer+ with a US local layout connecting to a vPro using a Swiss German Layout, everything looks fine.
RDM with a US local layout connecting to a vPro using a Swiss German Layout, everything looks fine.

Am I getting close?

Jonathan Lafontaine

signaturesignature

2 yrs VNC Keyboard Layout (Intel AMT)