[EMAIL PROTECTED] wrote:

Wez,

I registered then started the service through my TS session, then closed TS
and ran VNC, but when I try to connect I get "server closed connection
unexpectedly". I can understand why this would happen, if as you said, it
was running in application mode, however in service mode it should connect,
unless TS is stopping the service as well?


I think this is standard behavour on M$Windows implementations of vnc: It copies the contents of an existing session. Most times the session on the console. If you logout from the console, the console stays there and vnc can still handle the display, keyboard and mouse. Here the tiny difference is between services and user-started vncservers: if you logout, all your processes are killed, hence the user-started vncserver is killed. Services keep running hence vncservers runnig as service keep running.

Correct me if I'm wrong but I think that if you use a terminal-session, then the vncserver in ther copies that session. After you close the terminal-session, there is nothing left to handle so vnc stops too. In a little more detail: if you logout, the entire ts is removed. If you only disconnect and reconnect later, then the session is saved somewhere and it is only activated after you reconnect.



CBee



Ben

==========================================================
Triumph International Ltd
Arkwright Road, Groundwell, Swindon, SN25 5BE

Ben Blackmore
I.T. Department

Phone:      +44 (0) 1793 720126
Fax:           +44 (0) 1793 720179
Mail:           [EMAIL PROTECTED]
Visit us at: http://www.triumph-international.co.uk

==========================================================
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is prohibited.
==========================================================


"James Weatherall" To: <[EMAIL PROTECTED]> <[EMAIL PROTECTED] cc: <[EMAIL PROTECTED]> > Subject: RE: VNC 4 16/06/2004 09:47





Ben,

As mentioned in the FAQ, all bets are off if certain Terminal Services
based
features, particularly Remote Desktop or Fast User Switching are used.

In your case, I assume that you are running an application mode VNC Server
in your Terminal Services session - when you Disconnect the session,
Windows
actually shuts down the graphics for it, making it impossible for VNC
Server
to remote it.

Wez @ RealVNC Ltd.


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: 16 June 2004 09:44
To: James Weatherall
Cc: [EMAIL PROTECTED]
Subject: RE: VNC 4



Wez,

I think I've just sorted it! I checked the VNC4 known bugs
(http://www.realvnc.com/v4/known-bugs.html), and found...

The IP addresses displayed by the tray icon are not refreshed
when the host
IP addresses change.

After I stopped and restarted the service I was able to connect.

Its strange though, cause I'm connected via TS and when I run
VNC I get the
TS screen, if I close TS I can't connect. I think I'll have
to pay a visit
to the server, and check VNC is running on the normal desktop

Ben

==========================================================
Triumph International Ltd
Arkwright Road, Groundwell, Swindon, SN25 5BE

Ben Blackmore
I.T. Department

Phone:      +44 (0) 1793 720126
Fax:           +44 (0) 1793 720179
Mail:           [EMAIL PROTECTED]
Visit us at: http://www.triumph-international.co.uk

==========================================================
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is prohibited.
==========================================================





                     "James


Weatherall" To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> <[EMAIL PROTECTED] cc:


> Subject: RE: VNC 4




16/06/2004 09:38












Ben,

Have you checked that there is nothing else listening on the
VNC server
port?

Wez @ RealVNC Ltd.

_______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to