Menu

#1437 Error in Tight VNC Viewer: Connection parameters (host, port, socket, gates) is empty.

open
nobody
None
5
2021-05-06
2018-01-16
No

Error in Tight VNC Viewer: Connection parameters (host, port, socket, gates) is empty.

The rest of my team can use this to log into our operations computers that have access to our monitoring systems. This error comes up whenever I try using the shortcuts, but I can log in if I use the IP address and password.

Discussion

  • cameron minto

    cameron minto - 2018-04-10

    Getting the same error when using a saved vnc file. Have tried rolling back versions as well as changing to 32bit version. It's an imaged system connecting to a raspberry pi, same settings and IP addresses we use at sever different sites.**

     
  • toksai

    toksai - 2018-05-15

    I just installed the 32-bit version and that fixed the problem for me.

     
  • Futaya Yamazaki

    Futaya Yamazaki - 2018-10-03

    I specified hostname::Port_num+Display_num, then it worked.

     
  • Shane Gorrell

    Shane Gorrell - 2020-03-25

    I am getting this same issue when I try to use a saved short cut. I have tried several times to recreate the shortcut but no matter what I do to it I keep getting this same error.

    32 bit version did not fix it for me.
    I opened the file in notepad and all the fields are filled out properly.

     

    Last edit: Shane Gorrell 2020-03-25
  • hycon

    hycon - 2021-04-18

    Was working fine with a previous version (don't know which version), but after updating to 2.8.59, I get the same error.
    32-bit solved it for now.

     

    Last edit: hycon 2021-04-18
  • Daniel Liuzzi

    Daniel Liuzzi - 2021-05-05

    Came across this myself today. To fix, you need edit the registry key Computer\HKEY_CLASSES_ROOT\vnc_auto_file\shell\open\command as follows:

    • Change this: "%1"
    • To this: "-optionsfile=%1"

    Leave everything else alone. See https://superuser.com/a/1511286/18964 for more details.

     
    • Anton

      Anton - 2021-05-06

      Thank you, now i understand the issue
      vnc_auto_file belongs to UltraVNC

       

Log in to post a comment.

MongoDB Logo MongoDB