From 1051c22c7d71e4b6767f25c0b6482b1d728e0fc6 Mon Sep 17 00:00:00 2001
From: Pavel Jirasek <pavel.jirasek@vsb.cz>
Date: Thu, 28 Jun 2018 12:10:05 +0200
Subject: [PATCH] Display number 102

---
 .../accessing-the-clusters/graphical-user-interface/vnc.md      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs.it4i/general/accessing-the-clusters/graphical-user-interface/vnc.md b/docs.it4i/general/accessing-the-clusters/graphical-user-interface/vnc.md
index ce7e0a84c..986502bda 100644
--- a/docs.it4i/general/accessing-the-clusters/graphical-user-interface/vnc.md
+++ b/docs.it4i/general/accessing-the-clusters/graphical-user-interface/vnc.md
@@ -76,7 +76,7 @@ username :102
 ```
 
 !!! note
-    The VNC server runs on port 59xx, where xx is the display number. So, you get your port number simply as 5900 + display number, in our example 5900 + 61 = 5961. Another example for display number 102 is calculation of TCP port 5900 + 102 = 6002. **Please, calculate your own port number and use it instead of 5961 from examples below!**
+    The VNC server runs on port 59xx, where xx is the display number. So, you get your port number simply as 5900 + display number, in our example 5900 + 61 = 5961. Another example for display number 102 is calculation of TCP port 5900 + 102 = 6002 but be aware, that TCP ports above 6000 are often used by X11. **Please, calculate your own port number and use it instead of 5961 from examples below!**
 
 To access the VNC server you have to create a tunnel between the login node using TCP port 5961 and your machine using a free TCP port (for simplicity the very same) in next step. See examples for [Linux/Mac OS](#linuxmac-os-example-of-creating-a-tunnel) and [Windows](#windows-example-of-creating-a-tunnel).
 
-- 
GitLab