-
quatermass
- 8
- Posts: 13
- Joined: 2006-06-27 14:23
- Contact:
Invalid VNC server specified error
I’m using V1.02 in Windows XP pro sp2 and when I connect to a remote PC and save the .vnc file then when I double click on it I get the error —
invalid vnc server specified. Usage includes:…
Popping up.
How can I fix this?
The contents of the file look ok.
Isn’t the .vnc file meant to be double-clicked upon?
I’ve tried using ‘open with..’ and assigning it to the vncviewer.exe but it didn’t help.
Can someone help?
-
bevtech
- 800
- Posts: 2168
- Joined: 2005-08-03 14:07
- Location: Pennsylvania, United States
Re: Invalid VNC server specified error
Post
by bevtech » 2007-12-24 18:07
When installing uvnc did you have it associate with the *.vnc extension??
Bevtech
Windows XP Home, Pro SP2, Windows 2003 SBS server SP2(EN), Windows Media Center Editon 2005,Windows Vista Home Prem.,Fedora Core 6,Win9X, PChelpware Rel 1.0,
UVNC V 1.0.8.2
User not developer..
-
redge
- 1000
- Posts: 6797
- Joined: 2004-07-03 17:05
- Location: Switzerland — Geneva
Re: Invalid VNC server specified error
Post
by redge » 2007-12-24 21:22
this not work as my experience for unknown reason.
work around.
uninstall uvnc and install uvnc and don’t forget to see v checked «associate UltraVNC viewer with the .vnc extension
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
-
quatermass
- 8
- Posts: 13
- Joined: 2006-06-27 14:23
- Contact:
Re: Invalid VNC server specified error
Post
by quatermass » 2007-12-24 23:05
bevtech wrote:When installing uvnc did you have it associate with the *.vnc extension??
I can’t remember. What’s the registry setting so I can check it?
regedit shows .vnc has a default value of ‘VncViewer.Config’
and Classes root of ‘VncViewer.Config’ has:
Code: Select all
[HKEY_CLASSES_ROOTVncViewer.Config]
@="VNCviewer Config File"
[HKEY_CLASSES_ROOTVncViewer.ConfigDefaultIcon]
@="C:\UVNC\vncviewer102.exe,0"
[HKEY_CLASSES_ROOTVncViewer.ConfigShell]
[HKEY_CLASSES_ROOTVncViewer.ConfigShellopen]
[HKEY_CLASSES_ROOTVncViewer.ConfigShellopencommand]
@=""C:\UVNC\vncviewer102.exe" -config "%1""
Looks ok to me.
Last edited by quatermass on 2007-12-24 23:10, edited 1 time in total.
-
bevtech
- 800
- Posts: 2168
- Joined: 2005-08-03 14:07
- Location: Pennsylvania, United States
Re: Invalid VNC server specified error
Post
by bevtech » 2007-12-26 19:09
I would try to completely uninstall reboot the machine then install it making sure that you check the option by redge above. I have seen really weird things happen once in a while and if you get a fresh clean install of it. The problems seem to go away..
Tip: Other flavors of vnc can cause issues with uvnc because they are alike. Any kind of spyware and registry defender can also cause issues if they stop uvnc from installing properties
Bevtech
Windows XP Home, Pro SP2, Windows 2003 SBS server SP2(EN), Windows Media Center Editon 2005,Windows Vista Home Prem.,Fedora Core 6,Win9X, PChelpware Rel 1.0,
UVNC V 1.0.8.2
User not developer..
-
quatermass
- 8
- Posts: 13
- Joined: 2006-06-27 14:23
- Contact:
Re: Invalid VNC server specified error
Post
by quatermass » 2007-12-26 21:24
bevtech wrote:I would try to completely uninstall reboot the machine then install it making sure that you check the option by redge above. I have seen really weird things happen once in a while and if you get a fresh clean install of it. The problems seem to go away..
Is there not a simple list of the registry settings it requires somewhere?
Then I can simply do a comparison?
-
Jymi
- Posts: 1
- Joined: 2009-11-09 09:47
Re: Invalid VNC server specified error
Post
by Jymi » 2009-11-09 09:51
Just change in registry:
HKEY_CLASSES_ROOT/vnc_auto_file/shell/open/command to
C:folder_namevncviewer.exe /config %1
where folder_name is Your vnc location folder
-
rah
- Posts: 6
- Joined: 2009-10-08 18:46
- Contact:
Re: Invalid VNC server specified error
Post
by rah » 2015-01-20 17:44
I was just trying to resolve this issue on a Windows 7 PC. I tried to use the regedit setting suggested earlier but with Win 7 there’s double-quotes to contend with. Below is the combination that finally got it working for me.
«C:Program Filesuvnc bvbaUltraVNCvncviewer.exe» -config «%1»
Hopefully, it will save you some time.
-
clemo
- Posts: 1
- Joined: 2021-01-27 10:47
Re: Invalid VNC server specified error
Post
by clemo » 2021-01-27 14:15
None of the answers deals with the original problem. You are discussing file association, but file association is ok. When I double-click a vnc file, UVNC says «invalid vnc server specified». This is a message by UVNS so it means UVNC is opening the file by default. This is very weird because the vnc file was created by UVNC itself from a running session so the ip:port should be stored properly.
-
Rudi De Vos
- Admin & Developer
- Posts: 6602
- Joined: 2004-04-23 10:21
- Contact:
Re: Invalid VNC server specified error
Post
by Rudi De Vos » 2021-01-27 16:42
Did you check the file association ?
If this is wrong (like you manual attach .vnc to the vncviewer) the association is
«C:Program Filesuvnc bvbaUltraVNCvncviewer.exe «%1» and not «C:Program Filesuvnc bvbaUltraVNCvncviewer.exe» -config «%1»
In that case
vncviewer myhost.vnc is executed and vncviewer give the error that he can’t find server «myhost.vnc»
The vncviewer is using the filename as hostname and not as config file.
TightVNC is a free remote control software package derived from the popular VNC software. With TightVNC, you can see the desktop of a remote machine and control it with your local mouse and keyboard, just like you would do it sitting in the front of that computer. TightVNC is:
- free, GPL-licensed, with full source code available;
- useful in remote administration, remote customer support, education, and for many other purposes;
- cross-platform, available for Windows and Unix, compatible with other VNC software.
[May 8, 2007] TightVNC 1.3.9 is available. This version is a new stable release which should replace TightVNC 1.2.9.
some new features are:
- file transfers,
- improved server performance with mirror video driver,
- improved user interface,
- support for the latest version of the protocol
Contents
- 1 Download
- 2 DFMirage mirror display driver
- 3 Windows Installation
- 4 Linux/UNIX Installation
- 5 Windows Firewall
- 6 Troubleshooting
- 6.1 Issue: Invalid VNC server specified error
Download
- tightvnc-1.2.9-setup.exe — The Windows installer
- tightvnc-1.3.9_unixsrc.tar.gz Unix source code in Tar+Gzip archive
DFMirage mirror display driver
To achieve best performance under Windows 2000, Windows XP and above, download and install DFMirage mirror display driver. TightVNC Server can use this driver to detect screen updates and grab pixel data in a very efficient way. DFMirage driver is free just like TightVNC is.
Windows Installation
Linux/UNIX Installation
Windows Firewall
Microsoft Windows XP Firewall can be an annoyance to users of VNC. To run a VNC Server from your PC MS WinXP you must allow TCP port to be opened.
Remember, even when Windows Firewall is DISABLED, it still BLOCKS incoming traffic before the user is logged on. Windows XP Firewall is ALWAYS ENABLED at the login screen. So if you wish to use VNC Server to access the Windows XP login screen or reboot remote, you must allow TCP Port 5900 in the Windows XP Firewall exceptions — EVEN IF YOU DISABLE the Firewall!
- Goto START, SETTINGS, CONTROL PANEL
- Click «Network Connections» icon
- Right-Click on «Local Area Connection» (or the name of the connection you use) choose PROPERTIES
- Click on «Advanced» tab
- Under «Windows Firewall» click SETTINGS button
- Click EXCEPTIONS tab
- Click «Add Port»
- Enter «VNC» for name, 5900 for Port Number, and TCP for protocol and click OK
Troubleshooting
Issue: Invalid VNC server specified error
After saving the vnc session to a .vnc config file, double clicking that .vnc file should restore the vnc session. If instead the error message «Invalid VNC server specified error» is generated, the problem is in how the file extension has been associated in windows. See, the /config command line switch is required.
Using regedit.exe locate the following key:
HKEY_CLASSES_ROOTvnc_auto_fileshellopencommand
Change (wrong)
"C:internettightvncvncviewer.exe" "%1"
To (correct)
"C:internettightvncvncviewer.exe" "/config" "%1"
The /config command line parameter is needed for vncviewer to parse the .vnc text configuration file, otherwise it will treat it is a direct address.
I use TightVNC Viewer version 1.4.0 and want to save 75% scale and Full-screen mode settings. When I set them, close connection and then open it again, settings are default again.
How to save it permanently? Is it possible to save a password?
asked Mar 6, 2010 at 11:53
For Windows XP:
- When you have the settings as you like them, hold down the Ctrl key, and press Esc.
- Right-click on the TightVNC in your task bar, and select «Save connection info as…» (it will ask if you want to save the password).
- Use the saved .vnc file instead of the TightVNC executable to launch your remote session
For Windows 7 (Right clicking in the Task Manager doesn’t display the correct menu):
- Get the settings the way you want them.
- If that includes full screen, hold down Ctrl, Alt, and Shift, and press the F key.
- Click on the program icon above the toolbar and select «Save session to a .vnc file…» (it will ask if you want to save the password)
- If you want full screen, open the saved file and change
fullscreen=0tofullscreen=1. - Use the saved .vnc file instead of the TightVNC executable to launch your remote session.
answered Mar 6, 2010 at 20:26
BenBen
4743 silver badges10 bronze badges
3
If you are using TightVNC 2.x, on Windows it is not straight forward like you would expect.
You should save connection info to .vnc file, and you cannot just Open with… tvnviewer.exe
The full procedure is that you should Copy shortcut of your existing VNC Viewer, rename it to your connection name and right click it, click Properties and inside Target editbox put parameter called optionsfile. The final Target should look like this:
"C:Program FilesTightVNCtvnviewer.exe" -optionsfile="C:fullpathsavedconnection.vnc"
answered Feb 23, 2015 at 5:31
"C:Program FilesTightVNCtvnviewer.exe" -optionsfile=FILENAME.vnc
Kevin Panko
7,21622 gold badges43 silver badges52 bronze badges
answered Mar 8, 2014 at 2:49
2
I am a TightVnc newbie but am ‘familiar’ with ‘programming’ techniques (well, just about keeping my head above the waterline). This question is a bit old but it had me stumped for a while. Here’s what I did to get a copy of the TnvViewer ‘OptionsFile’:
- Open/Load TightVnc Viewer on my Windows 10 PC; ie connect to the other PC.
- On the toolbar of the TightVnc viewer window > click the ‘save’ icon («Save session to .vnc file».
- This opens a Windows Explorer ‘save’ window to my Windows PC; navigate to my chosen folder, create a filename, and click ‘Save’.
- I now have a ‘standard/basic’ options file to play with.
Apologies, as I cannot confirm what all the options do; I was just pleased to get the file.
As long as the Windows Explorer ‘Open With’ link connects the options file with TnvViewer, double clicking the options file puts me straight into TnvViewer on my nominated PC.
Hope this helps other Newbies.
answered Jan 25, 2018 at 15:57
In my version of TightVNC 1.2.9, the target must look like this (/config instead of -optionsfile= in Arunas’ answer):
"C:Program Files (x86)VNCvncviewer_T129.exe" /config "C:Users...vncmysettings.vnc"
answered Mar 20, 2019 at 14:58
mjavumjavu
12 bronze badges
3
The configuration options you mentioned are options of the vncviewer program, so, the answer depends on what kind of viewer you use. There are already several answers applicable in case you run vncviewer on windows machine.
In case your client machine is linux and you use vncviewer installed together with tigervnc package, the viewer configuration file located at ~/.vnc/default.tigervnc.
You have to create the file manually, example of file contents (first string is magic, must be exactly like like this):
TigerVNC Configuration file Version 1.0
MenuKey=F12
FullScreen=1
RemoteResize=0
Available options are described in man:
man vncviewer
answered Mar 19, 2020 at 7:53
lesniklesnik
1612 silver badges8 bronze badges
On current TightVNC version: start a session, then click the diskette on the button bar. You’ll be asked to save the password there. If you do and then double click on the saved session, the connection will be opened immediately without asking for password. Unfortunately, TightVNC is too stupid to offer profiles as Putty does.
answered Nov 14, 2020 at 0:16
Smit JohnthSmit Johnth
5916 silver badges15 bronze badges
Проблема
Ошибка сервера VNC: «A VNC server is already running as :X во время перезапуска vncserver.
VNC-сервер не запускается и выдает следующую ошибку.
# service vncserver restart Shutting down VNC server: 3:testuser 5:testuser2 [FAILED] Starting VNC server: 3:ctmagt70 New 'test1:3 (testuser)' desktop is test1:3 Starting applications specified in /tsc/apps/testuser/.vnc/xstartup Log file is /tsc/apps/testuser/.vnc/tscpinf001:3.log 5:testuser2 A VNC server is already running as :5 [FAILED]
Коренная причина
Эта ошибка может произойти из-за другого процесса, работающего в порту 6005, который препятствовал соединению vnc.
VNC-сервер прослушивает соединения для VNC-клиента по следующим TCP-портам.
5800+x, 5900+x, and 6000+x ( где x - это дисплей, который по умолчанию начинается с нуля)
Например:
- VNC-сервер на дисплее 5 будет прослушивать TCP-порты 5805, 5905 и 6005
- Дисплей 2 будет прослушивать TCP-порты 5802, 5902 и 6002
- Дисплей 18 будет прослушивать TCP-порты 5818, 5918 и 6018
Следующее уравнение объяснит предопределенное использование каждого порта, связанного с сервером VNC.
- 5800 + x – используется для отправки пользователю приложения vncviewer на основе java (при подключении из веб-браузера к порту 5800 + x)
- 5900 + x – VNC клиентский порт. Сам протокол VNC работает через этот порт.
- 6000 + x – X Серверный Порт
Вы можете проверить вывод netstat, чтобы убедиться, что зарезервированные порты vnc свободны на момент выпуска.
tcp 0 0 216.75.201.48:6005 216.75.201.48:46968 ESTABLISHED 505 217168781 26544/pmrepagent off (0.00/0/0)
Обходной путь
– Сделайте так, чтобы программа прослушивала порт 6000 + X, чтобы прослушивать другой порт.
– Временное решение: добавить параметр -nolisten в /usr/bin/vncserver, чтобы можно было отключить Xorg, который прослушивает 6000 + n, где n – номер дисплея. Пожалуйста, обратитесь к man-страницам man Xserver и man xorg за подробной информацией.
– Создайте резервную копию /usr/bin/vncserver и добавьте следующие строки в /usr/bin/vncserver после строки «$cmd =« Xvnc: $displayNumber »;»
# vi /usr/bin/vncserver $cmd .= " -nolisten tcp";
- Печать
Страницы: [1] Вниз
Тема: Проблема при подключении по VNC (Прочитано 8124 раз)
0 Пользователей и 1 Гость просматривают эту тему.
chardex
Добрый день!
Арендовал у хостера Hetzner сервер с предустановленной Ubuntu Server.
Я знаю, что на сервера неправильно устанавливать GUI, но знаний пока в этой области не хватает и хотелось бы поставить GUI, желательно как в десктопной версиии.
Установил ubuntu-desctop, gdm, vnc (по инструкции: http://ubuntuforums.org/showthread.php?t=122402). Все бы хорошо: на сервере при команде
sudo netstat -tap | grep xinetdвыводится
tcp 0 0 *:5901 *:* LISTEN 10932/xinetdПри локальном подключении (работаю через Putty) с сервера
vncviewer localhost:1Ошибка «Can’t open display» (насколько я понимаю, через Putty она и должна быть).
При попытке выполнить команду startx, получаю ошибку
7: /usr/bin/X (0x400000+0x25d59) [0x425d59]Не знаю, должна ли она быть в данных условиях. Меня смущает следующее поведение, ответ на которое я найти не смог: при попытке подключиться через VNC с удаленной машины (тоже ubuntu), подключение как бы происходит, но далее процесс засыпает и ничего не происходит:
Segmentation fault at address 0x24
Caught signal 11 (Segmentation fault). Server aborting
chardex@ubuntu:~$ vncviewer my_ip:1И так до бесконечности.
VNC Viewer Free Edition 4.1.1 for X - built Apr 9 2010 15:52:37
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Mon Jun 21 23:25:03 2010
CConn: connected to host my_ip port 5901
Подскажите, пожалуйста, что я делаю не так. Какой самый простой способ получить GUI на удаленной машине под управлением Ubuntu Server?
Linux Ubuntu-1004-lucid-64-minimal 2.6.32-22-server #33-Ubuntu SMP Wed Apr 28 14:34:48 UTC 2010 x86_64 GNU/Linux
alecsartania
Дома Linux Mint 20.1 / 20.02
chardex
Error: Can't open display:
Пользователь решил продолжить мысль 23 Июня 2010, 10:47:15:
Может все же кто-то хоть наводку даст?
То у меня идеи как решить проблему — закончились 
« Последнее редактирование: 23 Июня 2010, 10:47:15 от chardex »
gorven
при подключении через ssh чтобы открывать оконные приложения (если нужны)
в файле /etc/ssh/sshd_config ставим
X11Forwarding yes
теперь можно подключившись через Путтю открывать оконные приложения.
Если юзаем vnc, то:
Во первых проброшены ли порты для vncviewer на файрволе или роутере, за которым стоит север?
Если да, то команда будет выглядеть как
vncviewer ip_сервер:порт (у меня 5900)
Эта ваша Ubuntu прикольненькая такая винда (с)
chardex
Хочется через VNC.
chardex@ubuntu:~$ vncviewer server_ip:5900
VNC Viewer Free Edition 4.1.1 for X — built Apr 9 2010 15:52:37
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Wed Jun 23 15:41:22 2010
main: unable to connect to host: Connection timed out (110)
chardex@ubuntu:~$ vncviewer server_ip:5901
VNC Viewer Free Edition 4.1.1 for X — built Apr 9 2010 15:52:37
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Wed Jun 23 15:41:33 2010
CConn: connected to host server_ip port 5901
Дальше ничего не происходит.
Что должно произойти?
gorven
Вообще то должно выскочить окошко vncviewer»а с настройками……
дурной вопрос — а vnc-сервер установлен вообще? Если да, то гуглите за правильную настройкук его конфига и по ssh правте
Эта ваша Ubuntu прикольненькая такая винда (с)
chardex
Да, установлен, все точно, как по ссылке http://ubuntuforums.org/showthread.php?t=122402
Даже порт 5901 слушает.
А если десктоп правильно не подцепился, то VNC будет работать?
Возможно может кто-то настроить, если я дам данные для доступа (все равно на сервере ничего нет)? Отблагодарю 
gorven
Помнится были у меня какие то проблемы с vnc сервером, поставленном из репов. Файлик libvnc.so (кажется, могу соврать) кривой был и ничего не работало. Знакомы гентушник подогнал правильный файл, я его заменил и заработало. Конкретнее сказать не могу, попробуй загуглить
Эта ваша Ubuntu прикольненькая такая винда (с)
- Печать
Страницы: [1] Вверх