Introduction
This article will guide you through the process of resolving a common issue with TightVNC on a Windows server where the client connection display resolution is set to 800x600, but the Windows server desktop is configured to 1920x1080.
Understanding the Issue
The issue occurs when the client connecting to the Windows server through TightVNC is unable to match the desktop resolution of the server. This results in a smaller display resolution on the client side, even though the server is configured for a higher resolution.
Resolving the Issue
Step 1: Check the TightVNC Server Settings
The first step is to check the TightVNC server settings to ensure that the correct display resolution is being used. To do this, follow these steps:
-
Right-click on the TightVNC server icon in the system tray and select
Optionsfrom the context menu. -
In the
Optionswindow, select theExperttab. -
Under the
Displaysection, ensure that theFull-coloroption is selected and that theDesktop sizeis set toOriginal.
Step 2: Adjust the Windows Server Display Settings
If the TightVNC server settings are correct, the next step is to adjust the Windows server display settings. To do this, follow these steps:
-
Right-click on the desktop and select
Display settingsfrom the context menu. -
In the
Displaywindow, select the display that you want to adjust. -
Under the
Scale and layoutsection, use theChange the size of text, apps, and other itemsdropdown to select the desired display resolution.
Step 3: Restart the TightVNC Server
After adjusting the Windows server display settings, restart the TightVNC server to apply the changes. To do this, follow these steps:
-
Right-click on the TightVNC server icon in the system tray and select
Exitfrom the context menu. - Start the TightVNC server again by double-clicking on the TightVNC server icon.
In this article, we covered a common issue with TightVNC on a Windows server where the client connection display resolution is set to 800x600, but the Windows server desktop is configured to 1920x1080. We provided a step-by-step guide to resolving the issue, including checking the TightVNC server settings, adjusting the Windows server display settings, and restarting the TightVNC server.