The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: VNC Client (Viewer) for Windows



There's an option  in the server set up for accepting incoming
connections

IIRC, the options are  to;

Disconnect the existing client, start new connection
Keep the existing client and connect new client (multi-connection),
Refuse the new connection (keep existing) or
Refuse all connections

Select the appropriate option and all should be OK????

HTH

Neil

Rob Iles wrote:
> If you run the server as a Service (rather than user-land), you should
be
> fine whoever you log in as. (IIRC)
>
> Rob
>
>
> 2009/12/14 Adrian Eaton <adrian@xxxxxxx>
>
>
>> Hi Pete,
>>
>> I get that if the vnc server process is running under one user and
I try
>> and
>> logon as a different user. It works fine for the user it was
installed for
>> but not others. I've not worked out how to fix it yet though.
>>
>> Adrian
>>
>>
>> From: ukha_d@xxxxxxx <ukha_d%40yahoogroups.com> [mailto:
>> ukha_d@xxxxxxx <ukha_d%40yahoogroups.com>] On Behalf Of
>> White, Peter
>> Sent: 11 December 2009 22:48
>>
>> To: ukha_d@xxxxxxx <ukha_d%40yahoogroups.com>
>> Subject: RE: [ukha_d] VNC Client (Viewer) for Windows
>>
>>
>> On a related note, I installed tightvnc on my media server (just
running
>> XP), because the crappy ATI Catalyst app will not run over a
Remote Desktop
>> Connection, and I need to get into the app as for some reason it's
not
>> putting anything out via the HDMI connection.
>>
>> Anyway, when I log in thru tightVNC (or RealVNC for that matter),
I get to
>> the XP login screen, enter the user password, which is correct,
but at that
>> point it dumps me off the connection. Any ideas why? I'm sure it's
>> something
>> very obvious, but Google didn't turn anything up, and I've not
changed any
>> of the default settings.
>>
>> It's been bugging me for a while, seeing this post just reminded
me to
>> ask...
>>
>> Thanks, Pete
>>
>> From: ukha_d@xxxxxxx <ukha_d%40yahoogroups.com> <mailto:
>> ukha_d%40yahoogroups.com <ukha_d%2540yahoogroups.com>>
>> [mailto:ukha_d@xxxxxxx
<ukha_d%40yahoogroups.com> <mailto:
>> ukha_d%40yahoogroups.com <ukha_d%2540yahoogroups.com>> ]
On Behalf
>>
>> Of Quinten Uijldert
>> Sent: Friday, December 11, 2009 4:28 PM
>> To: ukha_d@xxxxxxx <ukha_d%40yahoogroups.com> <mailto:
>> ukha_d%40yahoogroups.com <ukha_d%2540yahoogroups.com>>
>> Subject: Re: [ukha_d] VNC Client (Viewer) for Windows
>>
>> http://www.tightvnc.com/
>>
>> 2009/12/11 rb_ziggy <rb.lists@xxxxxxx
<rb.lists%40ntlworld.com><mailto:
>> rb.lists%40ntlworld.com <rb.lists%2540ntlworld.com>>
>> <mailto:rb.lists%40ntlworld.com
<rb.lists%2540ntlworld.com>>>:
>>
>>> Can anyone recommend a VNC Viewer for windows that is a) quick
in
>>>
>> rendering and b) will scale the viewing window so that the whole
server
>> screen is visible within the viewer window.
>>
>>> Free if possible.
>>>
>>> I currently use the free Real VNC viewer on pc and this is
neither of the
>>>
>> above. Chicken of the VNC on the Mac (exactly the same LAN etc) is
much
>> faster.
>>
>>> I'm playing with a mimo screen and want to see if I can get
this going
>>>
>> well as a slave for the HA screen (still using XLobby!).
>>
>>> Ta!
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>> [Non-text portions of this message have been removed]
>>
>> [Non-text portions of this message have been removed]
>>
>>
>>
>>
>
>
>
>


__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4685 (20091214) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com




------------------------------------


UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.