• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Are you having HotKey issues? Click here for tips and tricks.
Locked

‎06-13-2024 03:36 PM

HP Recommended

We recently updated our Hp Device Manager host to 5.0.12 from 5.0.11. All processes/tasks work except VNC. When we attempt remote access direct or shadow, we connect but immediately get a popup from TightVNC viewer "Connection has been gracefully closed" "OK". 

On version 5.0.11 this did not happen. 

Any suggestions/assistance appreciated.

 

Category:
1 person had the same question
1 ACCEPTED SOLUTION

Accepted Solutions

‎06-13-2024 06:18 PM

HP Recommended

Hello, I would just like to clarify a few things. What device are you connecting to your HP device with? Have you tried updating TightVNC or tried using a different VNC app, such as RealVNC? Also, don't forget to check your firewall/antivirus if applicable! The Device Manager update may have reset your firewall or removed an exisiting exception.

 

Please let me know if this has helped! Feel free to ask more questions!

View solution in original post

Was this reply helpful? Yes No
2 REPLIES 2

‎06-13-2024 06:18 PM

HP Recommended

Hello, I would just like to clarify a few things. What device are you connecting to your HP device with? Have you tried updating TightVNC or tried using a different VNC app, such as RealVNC? Also, don't forget to check your firewall/antivirus if applicable! The Device Manager update may have reset your firewall or removed an exisiting exception.

 

Please let me know if this has helped! Feel free to ask more questions!

Was this reply helpful? Yes No

‎06-14-2024 01:40 PM

HP Recommended

Thank you for your response.

The firewall on the console machine was missing inbound tcp and udp rules for vnc. Once I added those, I was able to remote  to thin clients on different subnets in our enterprise.

Was this reply helpful? Yes No
Warning
Be alert for scammers posting fake support phone numbers and/or email addresses on the community.
If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.
Didn't find what you were looking for? Ask the community
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.