Connection Closed Unexpectedly. Vnc Error
Contents |
Post #1 of 10 (25804 views) Permalink Connection closed unexpectedly. Hello all, vnc connection closed When I open Real VNC Viewer 4 and type in vnc connection closed immediately my No-Ip address (mikesbikes.no-ip.info) I almost immediately get the error: The connection closed unexpectedly. Do error connection closed chrome you wish to attempt to reconnect to *********.no-ip.info:6900? Yes / No It seems strange, I had another PC work on the same network absolutely https://support.realvnc.com/knowledgebase/list/Index/1/error-messages fine. I really need to get access to the PC, I'm losing patience! Any help would be great! Thanks. Kind Regards, Adam Tranter Fusion-Media.co.uk w www.fusion-media.co.uk e adam [at] fusion-media [.demime 1.01d removed an attachment of type image/gif which had a name of sig.gif] _______________________________________________ VNC-List mailing list VNC-List [at] http://www.gossamer-threads.com/lists/vnc/list/52696 realvnc To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list JAldrich at covista Oct14,2005,9:23AM Post #2 of 10 (25589 views) Permalink RE: Connection closed unexpectedly. [In reply to] Can you give us some more info, such as whether there are any firewalls between you, operating systems in question, routers, etc? Also, if this is an XP, or 2000 machine can you check the system log files to see if there is any information about *why* it is closing? It sounds like it's authenticating, but then is kicking you off. One thing you can try, I don't know if it'll help, is to add the winvnc4.exe executable to the firewall (if any) as an approved application. Also, if you're using XP and have Fast User Switching enabled, you need to disable that. Same goes for the "Remote Desktop" app that comes with XP. -----Original Message----- From: vnc-list-admin [at] realvnc [mailto:vnc-li
board cookies • All times are UTC Powered by phpBB Forum Software © phpBB Group
GSM Modem C60T Dell Support Contact Us Post navigation ← Previous Next → RealVNC and TightVNC: "Connection closed unexpectedly" Posted on 2016-June-15 by Administrator When connecting to a VNC Server (applies to both RealVNC and TightVNC), the VNC client (applies to both RealVNC and TightVNC) is unable to connect, and shows this message, "Connection closed unexpectedly". The followings issues are properly configured and they are not the culprits:- VNC server and client is allowed by firewall; and VNC port; VNC password is correct. The log file of TightVNC server shows:- [ 2132/ 4332] 2016-06-15 13:23:30 ! write() function stopped because transport has not been initialized yet. [ 2132/ 4332] 2016-06-15 13:23:32 ! AnonymousPipe::read() failed (m_hRead = 000000000000030C) [ 2132/ 4332] 2016-06-15 13:23:32 ! The Pipe's read function failed after ReadFile calling (The pipe has been ended. (109)) [ 2132/ 4332] 2016-06-15 13:23:32 ! Exception during DesktopClientImpl creaion: [ 2132/ 4332] 2016-06-15 13:23:32 ! Error during RFB initialization: [ 2132/ 4332] 2016-06-15 13:23:32 ! Connection will be closed: [ 4500/ 4420] 2016-06-15 13:23:42 ! Desktop server application failed with error: The desktop server time out expired The root caused is "RFB" on the VNC server. Solution:- uninstalll "DisplayLink" driver from server and VNC client is able to connect to VNC server; uninstall any display driver that is incompatible with VNC server. This entry was posted in Support by Administrator. Bookmark the permalink. Proudly powered by WordPress