How to ENABLE notification that your computer Window 7 PC is being monitored via TightVNC?












1















I'm using TightVNC in a classroom situation, and I want the little pop up notification to appear on the students PC's letting them know when the teacher has remoted into their machine or is monitoring them.



However, that pop-up message indicating the teacher's PC name and that they are connected, does not consistently appear on all the machines when a connection is made.



I can't find any controls in TightVNC Viewer, Server or in Windows 7 that appears to control this. Any assistance finding and enabling such a control, or even finding a third-party plug-in that will serve the purpose, would be appreciated.










share|improve this question





























    1















    I'm using TightVNC in a classroom situation, and I want the little pop up notification to appear on the students PC's letting them know when the teacher has remoted into their machine or is monitoring them.



    However, that pop-up message indicating the teacher's PC name and that they are connected, does not consistently appear on all the machines when a connection is made.



    I can't find any controls in TightVNC Viewer, Server or in Windows 7 that appears to control this. Any assistance finding and enabling such a control, or even finding a third-party plug-in that will serve the purpose, would be appreciated.










    share|improve this question



























      1












      1








      1








      I'm using TightVNC in a classroom situation, and I want the little pop up notification to appear on the students PC's letting them know when the teacher has remoted into their machine or is monitoring them.



      However, that pop-up message indicating the teacher's PC name and that they are connected, does not consistently appear on all the machines when a connection is made.



      I can't find any controls in TightVNC Viewer, Server or in Windows 7 that appears to control this. Any assistance finding and enabling such a control, or even finding a third-party plug-in that will serve the purpose, would be appreciated.










      share|improve this question
















      I'm using TightVNC in a classroom situation, and I want the little pop up notification to appear on the students PC's letting them know when the teacher has remoted into their machine or is monitoring them.



      However, that pop-up message indicating the teacher's PC name and that they are connected, does not consistently appear on all the machines when a connection is made.



      I can't find any controls in TightVNC Viewer, Server or in Windows 7 that appears to control this. Any assistance finding and enabling such a control, or even finding a third-party plug-in that will serve the purpose, would be appreciated.







      tightvnc






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 7 '12 at 21:43









      Der Hochstapler

      68k49230285




      68k49230285










      asked Mar 17 '12 at 12:18









      BJRBJR

      612




      612






















          1 Answer
          1






          active

          oldest

          votes


















          0














          This is governed by the registry keys at



          HKLMSOFTWAREORLWinVNC3Default
          QuerySetting (REG_DWORD) ` should be set to 2
          QueryTimeout (REG_DWORD) ` timeout in seconds before applying the default action
          QueryAccept (REG_DWORD) ` Accept connection by default if no response to query window


          If you're finding that it doesn't work for some users, it may be because they have conflicting values configured in their profile (HKCUSOFTWAREORLWinVNC3Default).



          I had similar issues with UltraVNC a few years ago. You might want to check and see if some of the troublesome users/machines have another VNC server installed which might be setting those same registry values.






          share|improve this answer


























          • Thank you or your response. I see the picture that you added, but I'm not sure where or how to look on the computer to see it. I know that the IT department in our company uses "Dameware" to remote in occassionally,...I'm not sure if that might be the issue or if so, how to resolve it. Also, I've occassionally accidentally had TightVNC Server running more than one instance simultaneously. Again, if that's the case, I'm not sure where to look or how to resolve it. Also...can you tell me...if the pop up message generated by "tightvnc server", or is it generated by "Windows 7"?

            – BJR
            Mar 17 '12 at 15:21













          • I didn't put a picture in my answer - just a list of registry keys listed in a code block. I have never used Dameware, so I don't know if that could have an effect on VNC. I wouldn't have thought so. If you have more than one instance of tightVNC server running, only one of them will be able to bind to the default VNC port, so only one of them will be reachable at a time. You can see how many instances are running by looking at the running processes via tasklist.exe or in task manager. The pop-up message is generated by VNC, not Windows itself.

            – Adam Thompson
            Mar 18 '12 at 1:48











          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',
          autoActivateHeartbeat: false,
          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%2f401797%2fhow-to-enable-notification-that-your-computer-window-7-pc-is-being-monitored-via%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          This is governed by the registry keys at



          HKLMSOFTWAREORLWinVNC3Default
          QuerySetting (REG_DWORD) ` should be set to 2
          QueryTimeout (REG_DWORD) ` timeout in seconds before applying the default action
          QueryAccept (REG_DWORD) ` Accept connection by default if no response to query window


          If you're finding that it doesn't work for some users, it may be because they have conflicting values configured in their profile (HKCUSOFTWAREORLWinVNC3Default).



          I had similar issues with UltraVNC a few years ago. You might want to check and see if some of the troublesome users/machines have another VNC server installed which might be setting those same registry values.






          share|improve this answer


























          • Thank you or your response. I see the picture that you added, but I'm not sure where or how to look on the computer to see it. I know that the IT department in our company uses "Dameware" to remote in occassionally,...I'm not sure if that might be the issue or if so, how to resolve it. Also, I've occassionally accidentally had TightVNC Server running more than one instance simultaneously. Again, if that's the case, I'm not sure where to look or how to resolve it. Also...can you tell me...if the pop up message generated by "tightvnc server", or is it generated by "Windows 7"?

            – BJR
            Mar 17 '12 at 15:21













          • I didn't put a picture in my answer - just a list of registry keys listed in a code block. I have never used Dameware, so I don't know if that could have an effect on VNC. I wouldn't have thought so. If you have more than one instance of tightVNC server running, only one of them will be able to bind to the default VNC port, so only one of them will be reachable at a time. You can see how many instances are running by looking at the running processes via tasklist.exe or in task manager. The pop-up message is generated by VNC, not Windows itself.

            – Adam Thompson
            Mar 18 '12 at 1:48
















          0














          This is governed by the registry keys at



          HKLMSOFTWAREORLWinVNC3Default
          QuerySetting (REG_DWORD) ` should be set to 2
          QueryTimeout (REG_DWORD) ` timeout in seconds before applying the default action
          QueryAccept (REG_DWORD) ` Accept connection by default if no response to query window


          If you're finding that it doesn't work for some users, it may be because they have conflicting values configured in their profile (HKCUSOFTWAREORLWinVNC3Default).



          I had similar issues with UltraVNC a few years ago. You might want to check and see if some of the troublesome users/machines have another VNC server installed which might be setting those same registry values.






          share|improve this answer


























          • Thank you or your response. I see the picture that you added, but I'm not sure where or how to look on the computer to see it. I know that the IT department in our company uses "Dameware" to remote in occassionally,...I'm not sure if that might be the issue or if so, how to resolve it. Also, I've occassionally accidentally had TightVNC Server running more than one instance simultaneously. Again, if that's the case, I'm not sure where to look or how to resolve it. Also...can you tell me...if the pop up message generated by "tightvnc server", or is it generated by "Windows 7"?

            – BJR
            Mar 17 '12 at 15:21













          • I didn't put a picture in my answer - just a list of registry keys listed in a code block. I have never used Dameware, so I don't know if that could have an effect on VNC. I wouldn't have thought so. If you have more than one instance of tightVNC server running, only one of them will be able to bind to the default VNC port, so only one of them will be reachable at a time. You can see how many instances are running by looking at the running processes via tasklist.exe or in task manager. The pop-up message is generated by VNC, not Windows itself.

            – Adam Thompson
            Mar 18 '12 at 1:48














          0












          0








          0







          This is governed by the registry keys at



          HKLMSOFTWAREORLWinVNC3Default
          QuerySetting (REG_DWORD) ` should be set to 2
          QueryTimeout (REG_DWORD) ` timeout in seconds before applying the default action
          QueryAccept (REG_DWORD) ` Accept connection by default if no response to query window


          If you're finding that it doesn't work for some users, it may be because they have conflicting values configured in their profile (HKCUSOFTWAREORLWinVNC3Default).



          I had similar issues with UltraVNC a few years ago. You might want to check and see if some of the troublesome users/machines have another VNC server installed which might be setting those same registry values.






          share|improve this answer















          This is governed by the registry keys at



          HKLMSOFTWAREORLWinVNC3Default
          QuerySetting (REG_DWORD) ` should be set to 2
          QueryTimeout (REG_DWORD) ` timeout in seconds before applying the default action
          QueryAccept (REG_DWORD) ` Accept connection by default if no response to query window


          If you're finding that it doesn't work for some users, it may be because they have conflicting values configured in their profile (HKCUSOFTWAREORLWinVNC3Default).



          I had similar issues with UltraVNC a few years ago. You might want to check and see if some of the troublesome users/machines have another VNC server installed which might be setting those same registry values.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Mar 18 '12 at 1:49

























          answered Mar 17 '12 at 12:48









          Adam ThompsonAdam Thompson

          1,949915




          1,949915













          • Thank you or your response. I see the picture that you added, but I'm not sure where or how to look on the computer to see it. I know that the IT department in our company uses "Dameware" to remote in occassionally,...I'm not sure if that might be the issue or if so, how to resolve it. Also, I've occassionally accidentally had TightVNC Server running more than one instance simultaneously. Again, if that's the case, I'm not sure where to look or how to resolve it. Also...can you tell me...if the pop up message generated by "tightvnc server", or is it generated by "Windows 7"?

            – BJR
            Mar 17 '12 at 15:21













          • I didn't put a picture in my answer - just a list of registry keys listed in a code block. I have never used Dameware, so I don't know if that could have an effect on VNC. I wouldn't have thought so. If you have more than one instance of tightVNC server running, only one of them will be able to bind to the default VNC port, so only one of them will be reachable at a time. You can see how many instances are running by looking at the running processes via tasklist.exe or in task manager. The pop-up message is generated by VNC, not Windows itself.

            – Adam Thompson
            Mar 18 '12 at 1:48



















          • Thank you or your response. I see the picture that you added, but I'm not sure where or how to look on the computer to see it. I know that the IT department in our company uses "Dameware" to remote in occassionally,...I'm not sure if that might be the issue or if so, how to resolve it. Also, I've occassionally accidentally had TightVNC Server running more than one instance simultaneously. Again, if that's the case, I'm not sure where to look or how to resolve it. Also...can you tell me...if the pop up message generated by "tightvnc server", or is it generated by "Windows 7"?

            – BJR
            Mar 17 '12 at 15:21













          • I didn't put a picture in my answer - just a list of registry keys listed in a code block. I have never used Dameware, so I don't know if that could have an effect on VNC. I wouldn't have thought so. If you have more than one instance of tightVNC server running, only one of them will be able to bind to the default VNC port, so only one of them will be reachable at a time. You can see how many instances are running by looking at the running processes via tasklist.exe or in task manager. The pop-up message is generated by VNC, not Windows itself.

            – Adam Thompson
            Mar 18 '12 at 1:48

















          Thank you or your response. I see the picture that you added, but I'm not sure where or how to look on the computer to see it. I know that the IT department in our company uses "Dameware" to remote in occassionally,...I'm not sure if that might be the issue or if so, how to resolve it. Also, I've occassionally accidentally had TightVNC Server running more than one instance simultaneously. Again, if that's the case, I'm not sure where to look or how to resolve it. Also...can you tell me...if the pop up message generated by "tightvnc server", or is it generated by "Windows 7"?

          – BJR
          Mar 17 '12 at 15:21







          Thank you or your response. I see the picture that you added, but I'm not sure where or how to look on the computer to see it. I know that the IT department in our company uses "Dameware" to remote in occassionally,...I'm not sure if that might be the issue or if so, how to resolve it. Also, I've occassionally accidentally had TightVNC Server running more than one instance simultaneously. Again, if that's the case, I'm not sure where to look or how to resolve it. Also...can you tell me...if the pop up message generated by "tightvnc server", or is it generated by "Windows 7"?

          – BJR
          Mar 17 '12 at 15:21















          I didn't put a picture in my answer - just a list of registry keys listed in a code block. I have never used Dameware, so I don't know if that could have an effect on VNC. I wouldn't have thought so. If you have more than one instance of tightVNC server running, only one of them will be able to bind to the default VNC port, so only one of them will be reachable at a time. You can see how many instances are running by looking at the running processes via tasklist.exe or in task manager. The pop-up message is generated by VNC, not Windows itself.

          – Adam Thompson
          Mar 18 '12 at 1:48





          I didn't put a picture in my answer - just a list of registry keys listed in a code block. I have never used Dameware, so I don't know if that could have an effect on VNC. I wouldn't have thought so. If you have more than one instance of tightVNC server running, only one of them will be able to bind to the default VNC port, so only one of them will be reachable at a time. You can see how many instances are running by looking at the running processes via tasklist.exe or in task manager. The pop-up message is generated by VNC, not Windows itself.

          – Adam Thompson
          Mar 18 '12 at 1:48


















          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f401797%2fhow-to-enable-notification-that-your-computer-window-7-pc-is-being-monitored-via%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

          Plaza Victoria

          Puebla de Zaragoza

          Musa