# VNC remote access not displaying "@", "\<", "\>" characters

**URL:** <https://forums.suse.com/t/vnc-remote-access-not-displaying-characters/23477>\
**Category:** SLES Configure-Administer\
**Created:** [January 7, 2013, 3:51pm UTC](https://forums.suse.com/t/vnc-remote-access-not-displaying-characters/23477 "2013-01-07T15:51:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ashbrook](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@ashbrook](https://forums.suse.com/u/ashbrook)\
**Post date:** [January 7, 2013, 3:51pm UTC](https://forums.suse.com/t/vnc-remote-access-not-displaying-characters/23477/1 "2013-01-07T15:51:40Z")

</div>

Hello,  
I’ve searched and searched for a solution to this problem, but am getting nowhere. Perhaps someone here can help?  
I have a few SLES 11 SP2 servers running in VMware VMs. Access to them works fine from VMware vSphere console access, as does SSH terminal access, but my problem occurs when trying to use VNC access. For this I’ve tried to use TightVNC and UltraVNC clients on a Windows 7 desktop.

The problem is that certain characters are not being interpreted by either of the VNC clients, or the VNC server configuration. The characters that I have found don’t work are “@”, “\<” and “\>”, but I suspect that there may be more.

I have tried a few suggestions that I found, around adding “-xkb” to the VNC server config file in /etc/xinetd.d or changing keyboard-related settings but these do not seem to work for me.

Anyone else come across this problem? Any help with a solution much appreciated, thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\
**Post date:** [January 17, 2013, 3:30pm UTC](https://forums.suse.com/t/vnc-remote-access-not-displaying-characters/23477/2 "2013-01-17T15:30:20Z")

</div>

ashbrook,

It appears that in the past few days you have not received a response to your  
posting. That concerns us, and has triggered this automated reply.

Has your issue been resolved? If not, you might try one of the following options:

- Visit [http://www.suse.com/support](http://www.suse.com/support) and search the knowledgebase and/or check all  
the other support options available.
- You could also try posting your message again. Make sure it is posted in the  
correct newsgroup. ([http://forums.suse.com](http://forums.suse.com))

Be sure to read the forum FAQ about what to expect in the way of responses:  
[http://forums.suse.com/faq.php](http://forums.suse.com/faq.php)

If this is a reply to a duplicate posting, please ignore and accept our apologies  
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your SUSE Forums Team  
[http://forums.suse.com](http://forums.suse.com)

---

<div class="post-metadata">

**Author:** ![mollusc\_limited](https://avatars.discourse-cdn.com/v4/letter/m/46a35a/32.png) [@mollusc\_limited](https://forums.suse.com/u/mollusc_limited)\
**Post date:** [July 23, 2013, 9:20pm UTC](https://forums.suse.com/t/vnc-remote-access-not-displaying-characters/23477/3 "2013-07-23T21:20:11Z")

</div>

Hi ashbrook.  
I had the same problem and on my kit it was an issue with the keyboard mapping ( SLES installed with United Kingdom keyboard ).

Using TightVNC viewer ( client ) connect to your SLES Box and change the keyboard layout to USA. The keyboard layout option is at the bottom of the window ( TightVNC 2.7.7 ).

The keys you mentioned then started working for me.

Hope this helps,

Shane