Sorry for the insistence, but I’d like to understand why VNC links often have problems. The credits inside the router are always there, and updates are always done to the latest stable version.
It worked for about an hour earlier and now it doesn’t. Also, it only worked on the PC and not on mobile devices.
I’m waiting for explanations to give to the customers.
Thanks in advance
Thanks in advance.
Best regards
This issue is also applicable on our side. please look into this.
Greetings,
Please have a look at this reply on your other topic:
Best Regards,
Justinas
Hi ,
I tried restarting VNC and RUT, and now I can’t see the link even from my PC. Later, the router went offline on its own and after a few seconds, it came back online, so I was able to connect again only from my PC; others still can’t see the link.
It seems that restarting the router enabled the link visibility only on my PC.
I hope this information helps you understand the problem.
I look forward to your feedback.
Thanks
Best regards
Hi everyone, I found that setting the screen scale to 100% in the PC settings, as shown in the image below, makes the RMS VNC work correctly.
I hope this helps and we’re waiting for Teltonika to fix the issue.
This fixed the issue we were having with VNC as well. Cheers!
Hope you get this sorted soon — connectivity issues that work intermittently like that are always the most frustrating to explain to customers. Fingers crossed someone from the team jumps in with a fix.
Hello everyone,
I am experiencing what appears to be the same issue with several customers using Teltonika RMS Remote Access VNC, from Windows PCs to different types of remote equipment, mainly industrial controllers/PLCs.
After investigating the issue, I noticed that the behavior seems to depend on the combination of two local display settings:
Windows display scaling: Settings → System → Display → Scale
Browser zoom level, in my case Google Chrome
The important point is that neither setting seems to be the sole cause. The issue appears to depend on the combination of Windows scaling and browser zoom.
When the wrong combination is used, the Remote Access VNC session opens but the display remains completely black or white and is unusable.
I used the following procedure:
Generate an RMS Remote Access link.
Open the link in a new Chrome tab.
Change either:
the Windows display scaling, or
the Chrome zoom level.
Close the Remote Access tab.
Reopen the same Remote Access link.
The Remote Access link itself does not need to be regenerated.
In my tests, reopening the page after changing the scaling/zoom setting is enough for the new behavior to appear. A simple page refresh may even be sufficient, although I have mainly tested by closing and reopening the tab.
There is no need to:
clear the browser cache,
restart Chrome,
log out of RMS,
disconnect/reconnect the RMS session,
or generate a new Remote Access link.
On one customer’s PC, and across several Remote Access connections, I obtained the following results:
| Windows display scaling | Chrome zoom | RMS Remote Access VNC |
|---|---|---|
| 100% | 100% | Working |
| 100% | 80% | NOT working |
| 125% | 80% | Working |
| 125% | 100% | NOT working |
This behavior was repeatable.
For this particular customer, Windows display scaling is normally set to 125%. As a workaround, I asked the user to set the Chrome zoom level to 80%, and Remote Access VNC then works correctly.
So, at least on this workstation:
125% Windows scaling + 100% Chrome zoom = VNC unusable
125% Windows scaling + 80% Chrome zoom = VNC working
This strongly suggests that the problem is related to how the RMS Remote Access web client handles browser rendering, DPI/display scaling, or viewport dimensions, rather than to the remote VNC destination itself.
I have seen similar symptoms with several customers and different destination devices, which is why I do not believe the problem is specific to one PLC or one VNC server.
I do not currently have enough information to determine whether the issue also depends on:
screen resolution,
physical monitor size,
Windows DPI,
multiple-monitor configurations,
different scaling values between monitors,
or browser/device pixel ratio.
Has anyone else observed or reproduced the same behavior?
Could the Teltonika team ( @Justinas ) also confirm whether this issue is already known and currently being investigated?
This problem is causing significant inconvenience for customers because, depending on their local display configuration, RMS Remote Access VNC can suddenly appear completely unusable even though the connection itself is established.
The scaling/zoom workaround is effective in my tests, but obviously it would be preferable for the Remote Access interface to work independently of the user’s Windows scaling and browser zoom configuration.
Thank you.
