|
|
|
Junior Member
 
Group: Forum Members
Last Login: 5/23/2008 9:42:51 AM
Posts: 13,
Visits: 25
|
|
I've been using VNC Manager for a couple of years and up until recently was using Real VNC fre version exclusively. However, I've started using UltraVNC v1.0.1 and now v1.0.2 and I've experienced some inconsistent behavior.
With RealVNC, the status in VNC Manager was correctly reported...
Green Ball = Ready for Connection
Blue Ball = Not Ready for Connection
With UltraVNC, I often get a Blue Ball status but more than half the time I can still connect to the system. When I can't connect to a "Blue Ball" system, I've checked them and found UltraVNC running on them. I also find that a Blue Ball system that I couldn't connect to but verified was running UltraVNC sometimes after 15 or 20 minutes will let me connect to it.
I do know that if I can't connect to a Blue Ball system through VNC Manager, I also cannot connect to it through UltraVNC Viewer either. I have VNC Manager configured to check the status of VNC servers every 60 minutes. This problem manifests on Win95 systems through WinXP Pro.
Anybody experiencing this or have a suggestion?
Thanks.
|
|
|
|
|
Supreme Being
Group: Administrators
Last Login: Today @ 7:37:56 AM
Posts: 820,
Visits: 1,328
|
|
Blue status would be shown in case if the VNC Manager was able to establish TCP connection to remote computer, but instead of standard VNC handshake starting with "RFB" text, something else was received. So say if you have a Microsoft Virtual Server installed on a remote computer, which by default listens on 5900 port, you would get the Blue status for such computer.
I looked at the source code and it seems that there is one more possibility for the Blue status. It may be caused by timeout, if not enough data was received from remote computer within the timeout period.Since you are saying that standard VNC viewer cannot connect to such server either it would be safe to assume that there is something wrong going on with the server...or may be with the network connection?
Kindest Regards,
SmartCode Solutions Support
|
|
|
|
|
Junior Member
Group: Forum Members
Last Login: 4/1/2008 7:22:38 PM
Posts: 20,
Visits: 63
|
|
| Hey Guys, Based on your description of the problem, I'd now guess its a UltraVNC problem. We use UltraVNC exclusively for a while now and just accepted those blue circles and failed connects as a fact of life. The only resolution was to use the remote Task Manager to end the crashed winvnc.exe task, and restart the VNC service. Even then, it didn't always work, I'd have to reboot the PC. On top of the random crashing UltraVNC service, I found that that the Video Driver can actually BSOD Windows after about 10 log off's and on's of users in a few minutes in the same VNC session. So.. I think that since you said RealVNC works.. we might switch to that, or give TightVNC a try. Ultra VNC has those extra features, but its really buggy (blue circles and the crashing service), and makes those features not worth the trouble. /me is off to install RealVNC onto the clients. Thanks guys, Bryan
|
|
|
|
|
Junior Member
Group: Forum Members
Last Login: 4/1/2008 7:22:38 PM
Posts: 20,
Visits: 63
|
|
| Sorry for double post. Just wanted to add that I also used to have VNC Manager set to check the status of the computers every so many minutes. I had to disable it for the exact same reason: After a while it would crash UltraVNC on the computers, resulting in blue circles, and failed connections. Bryan
|
|
|
|