SmartCode Solutions Web Forum




Connection issues using UltraVNC and VNC Manager

Expand / Collapse
Author Message
 Posted Saturday, February 25, 2006
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: Monday, February 27, 2006
Posts: 1, Visits: 3
I have been working with the evaluation version of VNC Manager and have run into and issue where my VNC servers do not respond.  Prior to trying VNC Manager we had been using UltraVNC v1.0.0 RC18 without any problems.  After installing and evaluating VNC Manager we are now experiencing problems by which our UltraVNC servers will not respond to connection requests.  When this problem occurs we are unable to stop the VNC server service on the affected computer (error that the service did not repond).  The only resolution to this it seems is to reboot the workstation.  Our VNC servers are spread across multiple locations connected via T1's.  Additionally when when updating VNC server status in the folders the response varies and is very inconsistant.  Somtimes it will show alive and a few minutes later it may say invalid response. 

Do I need to replace the UltraVNC installs we currently have with the UltraVNC version included with VNC Manager? 

Additionally I have had to adjust the timeout for the scans to 3000ms to get the scans to find my servers in the remote offices.  I find this strange as a round trip ing only takes 16ms.  Scans were inconsistant on my local network as well.  Some servers were detected when other were not.  This was not only limited to VNC servers but to RDP servers as well.

I really like the design and feel of the product but so far my experience has been very inconsistant.  If anyone has any thoughts or suggestions on what may be causing these issues they would greatly be appriciated.

Post #739
Add to Twitter Add to Facebook
 Posted Sunday, February 26, 2006
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Administrators
Last Login: 2 days ago @ 4:49 PM
Posts: 1,248, Visits: 2,125
I have been working with the evaluation version of VNC Manager and have run into and issue where my VNC servers do not respond.  Prior to trying VNC Manager we had been using UltraVNC v1.0.0 RC18 without any problems.  After installing and evaluating VNC Manager we are now experiencing problems by which our UltraVNC servers will not respond to connection requests.  When this problem occurs we are unable to stop the VNC server service on the affected computer (error that the service did not repond).  The only resolution to this it seems is to reboot the workstation.  Our VNC servers are spread across multiple locations connected via T1's.  Additionally when when updating VNC server status in the folders the response varies and is very inconsistant.  Somtimes it will show alive and a few minutes later it may say invalid response.

Hm.. I really don't know what to suggest. I would say about 30-40% of our customers run UltraVNC servers and we had never heard about something like that. Perhaps upgrading to the latest version 1.0.1 of UltraVNC server might fix the problem?

Do I need to replace the UltraVNC installs we currently have with the UltraVNC version included with VNC Manager?

UltraVNC install included with the VNC Manager installs the same files as the native UltraVNC v1.0.1 installer. But you better upgrade your 1.0.0 RC18 installation with the latest one. UltraVNC had fixed quite a few bugs since the 1.0 release.

Additionally I have had to adjust the timeout for the scans to 3000ms to get the scans to find my servers in the remote offices.  I find this strange as a round trip ing only takes 16ms.  Scans were inconsistant on my local network as well.  Some servers were detected when other were not.  This was not only limited to VNC servers but to RDP servers as well.

VNC/RDP scan takes longer than a simple ping because during the scan VNC Manager:
1) establishes connection to a server
2) reads few first bytes sent by the server (this is to ensure that you really connected to a VNC/RDP server and to an email server listening on port 5900, for example).
In addition if you run the VNC Manager on a Windows XP SP2 based computer you might want to look at the following thread:
http://www.s-code.com/forum/Topic108-5-1.aspx

I really like the design and feel of the product but so far my experience has been very inconsistant.  If anyone has any thoughts or suggestions on what may be causing these issues they would greatly be appriciated.



Kindest Regards,
SmartCode Solutions Support

Post #740
Add to Twitter Add to Facebook
 Posted Monday, February 27, 2006
Junior Member

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member

Group: Forum Members
Last Login: Tuesday, July 11, 2006
Posts: 20, Visits: 155
Additionally I have had to adjust the timeout for the scans to 3000ms to get the scans to find my servers in the remote offices.  I find this strange as a round trip ing only takes 16ms.  Scans were inconsistant on my local network as well.  Some servers were detected when other were not.  This was not only limited to VNC servers but to RDP servers as well.

We ran into this too. However we found that it was more consistant when we did scans for RDP or VNC and not both.  Also we ran into some issues with the firewalls and IPS.  In some cases the IPS would pick up the service query as a port scan and drop the packets.  Some minor tweaking to the IPS and Firewall rules ironed out most of the issues.

Aaron

Post #741
Add to Twitter Add to Facebook


Similar Topics

Expand / Collapse

Reading This Topic

Expand / Collapse