Home > Error While > Error While Waiting For Server Message Tightvnc

Error While Waiting For Server Message Tightvnc


If it's a problem initially connecting, slow DNS might be at fault. The source column would be "Jamcast". Have you looked at your router logs? Thanks for the additional information.OK, so it sounds like the Jamcast server is not starting up upon restart. http://smartphpstatistics.com/error-while/error-while-waiting-for-server-message-tightvnc-mac.html

The service manager times out if the Jamcast (or any other) service fails to start in a reasonable amount of time. Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: vnc-list-admin "at" realvnc.com > [mailto:vnc-list-admin "at" realvnc.com] On Behalf Of Angelo Sarto > Sent: 06 April 2005 17:31 > To: Dr. H.CallahanMarch 31st, 2009, 08:28 PMedthefox, I posted this a couple of pages ago: The wiring of the network is basically: INTERNET /\ || \/ Modem <-> Router <-------> Switch <------> Windows Is the Jamcast service running? https://archive.realvnc.com/pipermail/vnc-list/2005-April/050215.html

Error While Waiting For Server Message

H.CallahanFebruary 12th, 2009, 11:34 PMIf this is a desktop machine without a wireless connection then try removing network manager using synaptic (you do not need it). Turned out my Nintendo Wii was configured with the same IP address as my server >_<. Also, note that there is another, older machine running Hardy (the initial install was Gutsy, and then upgraded with the upgrade utility) that is essentially hooked up the same way (different

I know esvnc has a lot less latency for me than tightvnc, even without the fuzzy option (which btw I cannot use - it hurts my eyes), and that's over a Closed your duplicate thread. Come back anytime if I can help with anything else.Thanks!Scott Jamcast Developer Support Page: http://getjamcast.com/Support.aspx WWW BLOG Facebook Twitter Google+ User ProfileView All Posts by User Seattlite #11 Posted : The wiring from the affected box and the switch is a brand new CAT-6 patch cable.

Reply With Quote 05-Feb-2009,13:57 #30 swerdna View Profile View Forum Posts View Blog Entries Visit Homepage View Articles Administrator Join Date Mar 2008 Location Oz Posts 11,469 Re: VNC Broken in Vnc Error While Waiting For Server Message It has been disabled for the time being. Some services stop automatically if they are not in use by other services or programs."Please help,Thanks :-)Hi,Sure, could you send your JAMCAST.LOG's along so I can have a look? http://marc.info/?l=vnc-list&m=101133053426132&w=2 The reason for this is that the line between the Router and the Switch is a single Cat 6 cable that has a difficult routing.

All, I get the error message "Error while waiting for server message" 5-10 times daily. I have previously tried the ServerAliveInterval, with no change. Comment: http://www.arin.net/reference/rfc/rfc1918.txt RegDate: 1994-03-15 Updated: 2007-11-27 OrgAbuseHandle: IANA-IP-ARIN OrgAbuseName: Internet Corporation for Assigned Names and Number OrgAbusePhone: +1-310-301-5820 OrgAbuseEmail: [email protected] OrgTechHandle: IANA-IP-ARIN OrgTechName: Internet Corporation for Assigned Names and Number OrgTechPhone: Yesterday, just for giggles, I fired up an SCP from the affected box to a Windows box sitting in close physical proximity (using WinSCP).

Vnc Error While Waiting For Server Message

I never lose cable signal. Terms Privacy Opt Out Choices Advertise Get latest updates about Open Source Projects, Conferences and News. Error While Waiting For Server Message If that isn't the answer, ionice might be useful. As soon as I hooked in the Internet (the path being a patch cable from the switch where the two machines are connected to the router and then a patch cable

Email us! check over here From the new machine itself, it does not appear to be generically loosing the network as I have been able to browse on it and download both through the browser and On the left, navigate Windows Logs->Application. There might be vnc settings you could twiddle too.

But I guess the service hasn't started since 6/15.Have you tried uninstalling/reinstalling Jamcast? Next time, I'll replace the case first! Contact Us Need technical support? his comment is here http://thinkgeek.com/sf ___________________________________________________________ TightVNC mailing list, [email protected] https://lists.sourceforge.net/lists/listinfo/vnc-tight-list Previous Message by Thread: Re: VNC: "Error while waiting for server message" I had the same problem and frustration until I started using VNC

However, there don't seem to have any other ill effects, and I can reconnect with my remote client again as many times as I want with no problems. Today I tried to look more closely into this issue, but have discovered that this line is not commented out in all TightVNC 1.2.x versions. All the configuration I have done is through the supplied web interface.

I feel that the problem is, at this point, more likely to be either the software or the configuration that is causing the problem.

The machine is wired. I was too stubborn to actually consider it but it turned out that I had forgotten something in a game console, which I configured a long time ago, manually. If needed I can get data from my router through the commandline, but someone will have to tell me what to type. H.CallahanApril 2nd, 2009, 04:05 PMWhat I can't wrap my head around is that if it is a piece of network equipment that is causing the problem, then why isn't it causing

Not true. I kind of fell stupid because I spent a lot of time on this I am connecting to my openSuse 11.1 box from my Windows XP box I am using tight Both ends have the same wiring though, so that should be good. http://smartphpstatistics.com/error-while/mac-error-while-printing-message.html under options I clicked the little box for "let remote server deal with mouse cursor" now everything is working with no crashes This solution worked for me.

I still have the problem today. http://p.sf.net/sfu/bobj-july___________________________________________________________ TightVNC mailing list, [hidden email] To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list « Return to VNC Tight List | 1 view|%1 views Loading... I'll attempt this delayed start function.Regards,Steve User ProfileView All Posts by User Scott #12 Posted : Sunday, August 24, 2014 8:19:35 AM(UTC) Rank: AdministrationJoined: 1/25/2009(UTC)Posts: 2,579Location: Orlando, FL, USA Originally gnome-system-log HermanABFebruary 13th, 2009, 10:02 AMAn old El'Cheapo router with little RAM somewhere in the link can cause SSH to drop out when it flushes its tables every five to 20

If so, you could try bumping your MTU to something larger than 1500. Sorry for taking long time, but...Because of your help I actually found two faults under Windows - logs --> System, which basically said no.1 "A timeout (30000ms) occured while waiting for I can always continue to ping the server and even samba will still work but VNC will no longer respond. Originally Posted by swerdna I filed a bug report that covers only TightVNC but it's probably relevant to a lot of the vnc issues discussed in this thread.

You will have to register before you can post in the forums. (Be aware the forums do not accept user names with a dash "-") Also, logging in lets you avoid H.CallahanFebruary 19th, 2009, 07:05 PMI am certain that the IP address is unique. When SSH has been thrown into the mix (either using SSH directly, trying to SCP something or tunneling with VNC), the message has been "Network error: Software caused connection abort". Other than that, try running programs like tshark and/or tcpdump, see what that uncovers.

use this init script in /home/yourname/.vnc/xstartup Code: #!/bin/sh /usr/bin/startkde In my comment #6 of the bug report I am able to report that: The KDE4 virtual desktop will start from within com> Date: 2002-01-18 5:02:32 [Download message RAW] Hello group! under options I clicked the little box for "let remote server deal with mouse cursor" now everything is working with no crashes Thanks! Your setting change works fro me also, at least using KDE4 with the TightVNC client on my Windows PC. (I don't have Gnome installed.) The only errant behavior that I get

D*mn thing still didn't work. After another 20 seconds or so VNC Viewer closes. (TightVNC viewer generates a dialog box with this message "Error while waiting for server message".) After a certain timeout the remote PC