The spirit of the community
VNC.com is for practical help between working IT people and others who use remote access technology. Members include experienced administrators, project maintainers, students, and people making their first connection. Explain what you know, admit what you do not, and give others room to learn.
Condescension and gatekeeping are out of bounds. Do not dismiss a question because it is basic, demand credentials before offering help, or imply that someone does not belong here. Condescension drives away the askers whose real problems make a technical community useful.
Treat every VNC implementation even-handedly. Useful comparisons discuss requirements, behavior, maintenance, security, and tradeoffs. Brand rivalry, unsupported claims, and attacks on people who choose a different tool make technical discussion worse.
Ask specific questions
A good technical question gives other members enough information to reproduce or recognize the problem. Include:
- What server, viewer, operating system, and version you ran.
- What you expected to happen and what happened instead.
- The steps you already tried and the exact safe-to-share error text.
- Relevant network details, with addresses and identifying data removed.
Use a descriptive title. Keep one main problem per thread when possible. If an answer solves the issue, say what worked so the thread helps the next person.
Protect credentials and personal data
Never post passwords, authentication tokens, private keys, recovery codes, license keys, or other credentials. Do not share personal data about yourself or anyone else unless it is necessary, lawful, and safe. Redact screenshots and logs before uploading them. Check window titles, usernames, email addresses, IP addresses, file paths, browser tabs, and background content.
If you accidentally disclose a secret, remove it where possible, rotate or revoke it immediately, and report the post. Editing a public post does not make a copied credential safe again.
Staff transparency
Staff should separate personal experience from an official statement. See the Moderation and Reporting Policy.
Use the right channel
Public threads are a community discussion space, not a support queue. Billing, licensing, account access, and security-critical issues involving RealVNC products should go to official RealVNC support. Do not post account records or sensitive diagnostic material in the community while seeking help.
General setup, interoperability, open-source project, and VNC technology questions belong here when they can be discussed safely. A community answer does not replace vendor documentation or professional advice for a production system.
No spam or hidden promotion
Do not post repetitive advertising, irrelevant links, referral campaigns, or bulk solicitations. Relevant links to your own project or employer are welcome when they directly answer the question and you disclose the connection. Do not pose as a satisfied customer, manufacture endorsements, or turn unrelated discussions into promotion.
Report abuse
Email abuse@vnc.com to flag harassment, unsafe content, exposed credentials, spam, or another rule violation. Include the page URL and a short explanation. Do not start a public argument with the person you report or repeat harmful content to draw attention to it.
How enforcement works
Moderators consider the content, context, harm, and account history. Depending on the situation, the response may be a note explaining the rule, content removal, a temporary suspension, or a ban. Serious or repeated violations can skip earlier steps. Details about review, outcomes, and appeals appear in the Moderation and Reporting Policy. Prohibited uses are also listed in the Acceptable Use Policy.