How to prevent question mark cursor issue cause be Insert key when doing VNC to a mac?











up vote
5
down vote

favorite
3












I found out that when I press the Insert key on the client I will block the OS X VNC server by putting it in a "help mode" where you get the question mark mouse cursor.



The mouse works but I cannot use the keyboard anymore.



Details:




  • Reconnecting using VNC does not help

  • Normal keyboard is working fine on the mac


The only solution in addition to relogin was to stop the VNC server on mac using:



  killall OSXvnc-server


After few seconds it will restart by itself and it will work.



I don't like current workaround and looking for something better.



Tested with these versions of the VNC client and all put the VNC server in the question mark mode, requiring service restart:




  • Ultr@VNC 1.0.8.2

  • RealVNC 4.1.3


I know that the problem is caused by the different/bad implementation of the VNC protocol in the server but do you need an workaround?










share|improve this question
























  • Apple forum is so nice - people complained about this issue and apple marked the thread as Solved! and archived it (readonly) discussions.apple.com/thread.jspa?threadID=2222053&tstart=0
    – sorin
    Jan 13 '10 at 14:59















up vote
5
down vote

favorite
3












I found out that when I press the Insert key on the client I will block the OS X VNC server by putting it in a "help mode" where you get the question mark mouse cursor.



The mouse works but I cannot use the keyboard anymore.



Details:




  • Reconnecting using VNC does not help

  • Normal keyboard is working fine on the mac


The only solution in addition to relogin was to stop the VNC server on mac using:



  killall OSXvnc-server


After few seconds it will restart by itself and it will work.



I don't like current workaround and looking for something better.



Tested with these versions of the VNC client and all put the VNC server in the question mark mode, requiring service restart:




  • Ultr@VNC 1.0.8.2

  • RealVNC 4.1.3


I know that the problem is caused by the different/bad implementation of the VNC protocol in the server but do you need an workaround?










share|improve this question
























  • Apple forum is so nice - people complained about this issue and apple marked the thread as Solved! and archived it (readonly) discussions.apple.com/thread.jspa?threadID=2222053&tstart=0
    – sorin
    Jan 13 '10 at 14:59













up vote
5
down vote

favorite
3









up vote
5
down vote

favorite
3






3





I found out that when I press the Insert key on the client I will block the OS X VNC server by putting it in a "help mode" where you get the question mark mouse cursor.



The mouse works but I cannot use the keyboard anymore.



Details:




  • Reconnecting using VNC does not help

  • Normal keyboard is working fine on the mac


The only solution in addition to relogin was to stop the VNC server on mac using:



  killall OSXvnc-server


After few seconds it will restart by itself and it will work.



I don't like current workaround and looking for something better.



Tested with these versions of the VNC client and all put the VNC server in the question mark mode, requiring service restart:




  • Ultr@VNC 1.0.8.2

  • RealVNC 4.1.3


I know that the problem is caused by the different/bad implementation of the VNC protocol in the server but do you need an workaround?










share|improve this question















I found out that when I press the Insert key on the client I will block the OS X VNC server by putting it in a "help mode" where you get the question mark mouse cursor.



The mouse works but I cannot use the keyboard anymore.



Details:




  • Reconnecting using VNC does not help

  • Normal keyboard is working fine on the mac


The only solution in addition to relogin was to stop the VNC server on mac using:



  killall OSXvnc-server


After few seconds it will restart by itself and it will work.



I don't like current workaround and looking for something better.



Tested with these versions of the VNC client and all put the VNC server in the question mark mode, requiring service restart:




  • Ultr@VNC 1.0.8.2

  • RealVNC 4.1.3


I know that the problem is caused by the different/bad implementation of the VNC protocol in the server but do you need an workaround?







keyboard vnc remote-control






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 13 '10 at 14:26

























asked Jan 11 '10 at 12:35









sorin

4,412174762




4,412174762












  • Apple forum is so nice - people complained about this issue and apple marked the thread as Solved! and archived it (readonly) discussions.apple.com/thread.jspa?threadID=2222053&tstart=0
    – sorin
    Jan 13 '10 at 14:59


















  • Apple forum is so nice - people complained about this issue and apple marked the thread as Solved! and archived it (readonly) discussions.apple.com/thread.jspa?threadID=2222053&tstart=0
    – sorin
    Jan 13 '10 at 14:59
















Apple forum is so nice - people complained about this issue and apple marked the thread as Solved! and archived it (readonly) discussions.apple.com/thread.jspa?threadID=2222053&tstart=0
– sorin
Jan 13 '10 at 14:59




Apple forum is so nice - people complained about this issue and apple marked the thread as Solved! and archived it (readonly) discussions.apple.com/thread.jspa?threadID=2222053&tstart=0
– sorin
Jan 13 '10 at 14:59










3 Answers
3






active

oldest

votes

















up vote
2
down vote













From Mac OS X - VNC curson becomes QUESTION mark - unable to type (with experts-exchange.com you might need to google for it, then scroll to the end to see the answers):




Answer 1:
This problem occurs when
you use UltraVNC version 1.0.5.2
(possibly anything 1.0.5.+?) and hit
the INSERT key on a Windows machine.
At that point your only option appears
to be to logout and log back in. This
problem does not occur with UltraVNC
1.0.2 or the latest version of TightVNC or RealVNC. Also, FYI, Mac
OSX has a built in VNC cilent, you do
not need to install Vine VNC unless
you want per-user VNC sessions. Only
TightVNC or UltraVNC 1.0.2 appear to
be able to connect to the default OSX
VNC server, the others fail.



Answer 2:
I don't to this in my
environment, but in the Mac world the
key should be Command-C to copy and
Command-V to paste. Not sure if VNC
client changes that or
not...apparently it might given the
answer above...but you might give it a
shot.



Answer 3:
This may sound silly...
but I don't use CTRL-C to copy... it
does not work for me using TightVNC...
I use ALT-C... that copies for me.







share|improve this answer





















  • Thanks for clarifying! I voted for it but I cannot accept it as an answer because it does not provide a solution.
    – sorin
    Jan 13 '10 at 14:31










  • The solution is apparently using the latest version of TightVNC or RealVNC.
    – harrymc
    Jan 13 '10 at 15:09










  • I tested latest TightVNC and RealVNC and they still have the "Ins" key bug that blocks the Mac.
    – sorin
    Jan 27 '10 at 21:08


















up vote
1
down vote













This is fixed for me using Vine Server 4.01 on mac side and UltraVNC viewer 1.1.9.1 on windows side.



Default settings on server side produce the bug (very annoying).



To fix, open Vine Server preferences, Advanced tab, change Keyboard Events to User Session Events.



Happily using Ctrl+Ins/Shift+Ins for copy/paste in xcode now.



Note: this will likely break any keyboard remapper you have that relies on hardware events.






share|improve this answer




























    up vote
    1
    down vote













    As of 2018 (Mojave, High Sierra, etc) the VNC server is named /System/Library/CoreServices/RemoteManagement/screensharingd.bundle/Contents/MacOS/screensharingd



    If you can remotely log in, you can restart it with

    sudo killall screensharingd



    The server restarts and resumes the previous connections.






    share|improve this answer





















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f94326%2fhow-to-prevent-question-mark-cursor-issue-cause-be-insert-key-when-doing-vnc-to%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      2
      down vote













      From Mac OS X - VNC curson becomes QUESTION mark - unable to type (with experts-exchange.com you might need to google for it, then scroll to the end to see the answers):




      Answer 1:
      This problem occurs when
      you use UltraVNC version 1.0.5.2
      (possibly anything 1.0.5.+?) and hit
      the INSERT key on a Windows machine.
      At that point your only option appears
      to be to logout and log back in. This
      problem does not occur with UltraVNC
      1.0.2 or the latest version of TightVNC or RealVNC. Also, FYI, Mac
      OSX has a built in VNC cilent, you do
      not need to install Vine VNC unless
      you want per-user VNC sessions. Only
      TightVNC or UltraVNC 1.0.2 appear to
      be able to connect to the default OSX
      VNC server, the others fail.



      Answer 2:
      I don't to this in my
      environment, but in the Mac world the
      key should be Command-C to copy and
      Command-V to paste. Not sure if VNC
      client changes that or
      not...apparently it might given the
      answer above...but you might give it a
      shot.



      Answer 3:
      This may sound silly...
      but I don't use CTRL-C to copy... it
      does not work for me using TightVNC...
      I use ALT-C... that copies for me.







      share|improve this answer





















      • Thanks for clarifying! I voted for it but I cannot accept it as an answer because it does not provide a solution.
        – sorin
        Jan 13 '10 at 14:31










      • The solution is apparently using the latest version of TightVNC or RealVNC.
        – harrymc
        Jan 13 '10 at 15:09










      • I tested latest TightVNC and RealVNC and they still have the "Ins" key bug that blocks the Mac.
        – sorin
        Jan 27 '10 at 21:08















      up vote
      2
      down vote













      From Mac OS X - VNC curson becomes QUESTION mark - unable to type (with experts-exchange.com you might need to google for it, then scroll to the end to see the answers):




      Answer 1:
      This problem occurs when
      you use UltraVNC version 1.0.5.2
      (possibly anything 1.0.5.+?) and hit
      the INSERT key on a Windows machine.
      At that point your only option appears
      to be to logout and log back in. This
      problem does not occur with UltraVNC
      1.0.2 or the latest version of TightVNC or RealVNC. Also, FYI, Mac
      OSX has a built in VNC cilent, you do
      not need to install Vine VNC unless
      you want per-user VNC sessions. Only
      TightVNC or UltraVNC 1.0.2 appear to
      be able to connect to the default OSX
      VNC server, the others fail.



      Answer 2:
      I don't to this in my
      environment, but in the Mac world the
      key should be Command-C to copy and
      Command-V to paste. Not sure if VNC
      client changes that or
      not...apparently it might given the
      answer above...but you might give it a
      shot.



      Answer 3:
      This may sound silly...
      but I don't use CTRL-C to copy... it
      does not work for me using TightVNC...
      I use ALT-C... that copies for me.







      share|improve this answer





















      • Thanks for clarifying! I voted for it but I cannot accept it as an answer because it does not provide a solution.
        – sorin
        Jan 13 '10 at 14:31










      • The solution is apparently using the latest version of TightVNC or RealVNC.
        – harrymc
        Jan 13 '10 at 15:09










      • I tested latest TightVNC and RealVNC and they still have the "Ins" key bug that blocks the Mac.
        – sorin
        Jan 27 '10 at 21:08













      up vote
      2
      down vote










      up vote
      2
      down vote









      From Mac OS X - VNC curson becomes QUESTION mark - unable to type (with experts-exchange.com you might need to google for it, then scroll to the end to see the answers):




      Answer 1:
      This problem occurs when
      you use UltraVNC version 1.0.5.2
      (possibly anything 1.0.5.+?) and hit
      the INSERT key on a Windows machine.
      At that point your only option appears
      to be to logout and log back in. This
      problem does not occur with UltraVNC
      1.0.2 or the latest version of TightVNC or RealVNC. Also, FYI, Mac
      OSX has a built in VNC cilent, you do
      not need to install Vine VNC unless
      you want per-user VNC sessions. Only
      TightVNC or UltraVNC 1.0.2 appear to
      be able to connect to the default OSX
      VNC server, the others fail.



      Answer 2:
      I don't to this in my
      environment, but in the Mac world the
      key should be Command-C to copy and
      Command-V to paste. Not sure if VNC
      client changes that or
      not...apparently it might given the
      answer above...but you might give it a
      shot.



      Answer 3:
      This may sound silly...
      but I don't use CTRL-C to copy... it
      does not work for me using TightVNC...
      I use ALT-C... that copies for me.







      share|improve this answer












      From Mac OS X - VNC curson becomes QUESTION mark - unable to type (with experts-exchange.com you might need to google for it, then scroll to the end to see the answers):




      Answer 1:
      This problem occurs when
      you use UltraVNC version 1.0.5.2
      (possibly anything 1.0.5.+?) and hit
      the INSERT key on a Windows machine.
      At that point your only option appears
      to be to logout and log back in. This
      problem does not occur with UltraVNC
      1.0.2 or the latest version of TightVNC or RealVNC. Also, FYI, Mac
      OSX has a built in VNC cilent, you do
      not need to install Vine VNC unless
      you want per-user VNC sessions. Only
      TightVNC or UltraVNC 1.0.2 appear to
      be able to connect to the default OSX
      VNC server, the others fail.



      Answer 2:
      I don't to this in my
      environment, but in the Mac world the
      key should be Command-C to copy and
      Command-V to paste. Not sure if VNC
      client changes that or
      not...apparently it might given the
      answer above...but you might give it a
      shot.



      Answer 3:
      This may sound silly...
      but I don't use CTRL-C to copy... it
      does not work for me using TightVNC...
      I use ALT-C... that copies for me.








      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Jan 11 '10 at 14:19









      harrymc

      250k11258555




      250k11258555












      • Thanks for clarifying! I voted for it but I cannot accept it as an answer because it does not provide a solution.
        – sorin
        Jan 13 '10 at 14:31










      • The solution is apparently using the latest version of TightVNC or RealVNC.
        – harrymc
        Jan 13 '10 at 15:09










      • I tested latest TightVNC and RealVNC and they still have the "Ins" key bug that blocks the Mac.
        – sorin
        Jan 27 '10 at 21:08


















      • Thanks for clarifying! I voted for it but I cannot accept it as an answer because it does not provide a solution.
        – sorin
        Jan 13 '10 at 14:31










      • The solution is apparently using the latest version of TightVNC or RealVNC.
        – harrymc
        Jan 13 '10 at 15:09










      • I tested latest TightVNC and RealVNC and they still have the "Ins" key bug that blocks the Mac.
        – sorin
        Jan 27 '10 at 21:08
















      Thanks for clarifying! I voted for it but I cannot accept it as an answer because it does not provide a solution.
      – sorin
      Jan 13 '10 at 14:31




      Thanks for clarifying! I voted for it but I cannot accept it as an answer because it does not provide a solution.
      – sorin
      Jan 13 '10 at 14:31












      The solution is apparently using the latest version of TightVNC or RealVNC.
      – harrymc
      Jan 13 '10 at 15:09




      The solution is apparently using the latest version of TightVNC or RealVNC.
      – harrymc
      Jan 13 '10 at 15:09












      I tested latest TightVNC and RealVNC and they still have the "Ins" key bug that blocks the Mac.
      – sorin
      Jan 27 '10 at 21:08




      I tested latest TightVNC and RealVNC and they still have the "Ins" key bug that blocks the Mac.
      – sorin
      Jan 27 '10 at 21:08












      up vote
      1
      down vote













      This is fixed for me using Vine Server 4.01 on mac side and UltraVNC viewer 1.1.9.1 on windows side.



      Default settings on server side produce the bug (very annoying).



      To fix, open Vine Server preferences, Advanced tab, change Keyboard Events to User Session Events.



      Happily using Ctrl+Ins/Shift+Ins for copy/paste in xcode now.



      Note: this will likely break any keyboard remapper you have that relies on hardware events.






      share|improve this answer

























        up vote
        1
        down vote













        This is fixed for me using Vine Server 4.01 on mac side and UltraVNC viewer 1.1.9.1 on windows side.



        Default settings on server side produce the bug (very annoying).



        To fix, open Vine Server preferences, Advanced tab, change Keyboard Events to User Session Events.



        Happily using Ctrl+Ins/Shift+Ins for copy/paste in xcode now.



        Note: this will likely break any keyboard remapper you have that relies on hardware events.






        share|improve this answer























          up vote
          1
          down vote










          up vote
          1
          down vote









          This is fixed for me using Vine Server 4.01 on mac side and UltraVNC viewer 1.1.9.1 on windows side.



          Default settings on server side produce the bug (very annoying).



          To fix, open Vine Server preferences, Advanced tab, change Keyboard Events to User Session Events.



          Happily using Ctrl+Ins/Shift+Ins for copy/paste in xcode now.



          Note: this will likely break any keyboard remapper you have that relies on hardware events.






          share|improve this answer












          This is fixed for me using Vine Server 4.01 on mac side and UltraVNC viewer 1.1.9.1 on windows side.



          Default settings on server side produce the bug (very annoying).



          To fix, open Vine Server preferences, Advanced tab, change Keyboard Events to User Session Events.



          Happily using Ctrl+Ins/Shift+Ins for copy/paste in xcode now.



          Note: this will likely break any keyboard remapper you have that relies on hardware events.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Apr 2 '14 at 16:20









          Eugene

          1312




          1312






















              up vote
              1
              down vote













              As of 2018 (Mojave, High Sierra, etc) the VNC server is named /System/Library/CoreServices/RemoteManagement/screensharingd.bundle/Contents/MacOS/screensharingd



              If you can remotely log in, you can restart it with

              sudo killall screensharingd



              The server restarts and resumes the previous connections.






              share|improve this answer

























                up vote
                1
                down vote













                As of 2018 (Mojave, High Sierra, etc) the VNC server is named /System/Library/CoreServices/RemoteManagement/screensharingd.bundle/Contents/MacOS/screensharingd



                If you can remotely log in, you can restart it with

                sudo killall screensharingd



                The server restarts and resumes the previous connections.






                share|improve this answer























                  up vote
                  1
                  down vote










                  up vote
                  1
                  down vote









                  As of 2018 (Mojave, High Sierra, etc) the VNC server is named /System/Library/CoreServices/RemoteManagement/screensharingd.bundle/Contents/MacOS/screensharingd



                  If you can remotely log in, you can restart it with

                  sudo killall screensharingd



                  The server restarts and resumes the previous connections.






                  share|improve this answer












                  As of 2018 (Mojave, High Sierra, etc) the VNC server is named /System/Library/CoreServices/RemoteManagement/screensharingd.bundle/Contents/MacOS/screensharingd



                  If you can remotely log in, you can restart it with

                  sudo killall screensharingd



                  The server restarts and resumes the previous connections.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Dec 1 at 18:07









                  DMPalmer

                  1111




                  1111






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f94326%2fhow-to-prevent-question-mark-cursor-issue-cause-be-insert-key-when-doing-vnc-to%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      How do I know what Microsoft account the skydrive app is syncing to?

                      When does type information flow backwards in C++?

                      Grease: Live!