|
By shane - Friday, April 24, 2009
|
|
I have a folder with 343 computers in it. If I select half of them and right mouse click on the selection, click on "check VNC/RDP/SSH Staus", many report as all "x"s (no response). If I take one of the computers that reported no response, and run the check singularly, then I get information back.......
|
|
By Nelson-BBB - Tuesday, May 12, 2009
|
|
I'm getting similar results. As a group, the only positive response is from Ping - individually the status update will work correctly, however the VNC response is 90% blue rather than green. We have three admin licenses and I'm the only one using the beta and the only one getting these results.
|
|
By Bob Hartung - Tuesday, May 26, 2009
|
Same here. I have VNC Mgr configured to check status on startup and every hour. Only ping reports status correctly.
I find if I manually test it, the status reports correctly. This also works for selecting multiple PCs to check.
|
|
By shane - Tuesday, May 26, 2009
|
|
I downloaded the 5.0.2.0 and the problem still exists.
|
|
By Yury Averkiev (s-code) - Monday, June 08, 2009
|
Guys,
please do give a try to the v5.0.3.0. It fixes couple scan related bugs that could had contributed to the problem you experience with the v5.0.2.0.
|
|
By Bob Hartung - Monday, June 08, 2009
|
I installed v5.0.3.0 this morning and I now have a mixture of different results. A minority of PCs display correctly, showing VNC, RDP and Ping green. I have more PCs that only display Ping green and VNC and RDP as red even though VNC and RDP are operational. I also have some that show RDP and Ping green with VNC red even though VNC is active and functional.
My PCs primarily have UltraVNC v1.0.5.0, v1.0.5.3 or v1.0.5.6 installed. Which version doesn't seem to be a factor.
|
|
By shane - Wednesday, June 10, 2009
|
|
Just tried the 5.0.3.0 version..... problem remains....sorry
|
|
By shane - Thursday, July 02, 2009
|
Problem remains with ver 5.0.4.1
-Shane
|
|
By boss - Friday, August 28, 2009
|
related to Server status check, if I select under Manager option to have "Scan all registered computers when application starts" this is not applied. Looks like VNC Manger does not remember change in setting. After restart of the application option gets deselected.
I am using 5 0 7 0 version.
|
|
By Yury Averkiev (s-code) - Saturday, August 29, 2009
|
|
boss (8/28/2009)
related to Server status check, if I select under Manager option to have "Scan all registered computers when application starts" this is not applied. Looks like VNC Manger does not remember change in setting. After restart of the application option gets deselected.
I am using 5 0 7 0 version.Thank you for reporting this problem. It will be fixed in the 5.0.8.0 build. UPDATE: Fixed
|
|
By chewbakka - Wednesday, September 02, 2009
|
Hello,
i´ve got the problem in 5.08, that the button for the vnc server status is not working.
Every single computer is shown with the red status light for the vnc server, even when i already connected to the machine 
Doesn´t matter what version of vnc is running on the remote computer, tightvnc or uvnc....
|
|
By Nelson-BBB - Wednesday, September 02, 2009
|
Any update on the status check issue? Still not working in Version 5.0.8.0.
Thanks!
|
|
By Yury Averkiev (s-code) - Wednesday, September 02, 2009
|
Hello, i´ve got the problem in 5.08, that the button for the vnc server status is not working. Every single computer is shown with the red status light for the vnc server, even when i already connected to the machine Doesn´t matter what version of vnc is running on the remote computer, tightvnc or uvnc.... Could you double check what update timeout value your VNC Manager is using? Im wondering if the problem is caused by the timeout being set to too low value.
Tools->Options->Server Status Check->Scan timeout.
|
|
By shane - Friday, September 04, 2009
|
I have also updated to 5.08 and still have the same problem. I selected 188 workstations and only 31 of them reported correctly. I increased the timeout from 800ms up to 1000ms, then to 1500ms, then to 3000ms. At 3000ms, some would report status, some would not. I restarted the manager and just selected 5 from the ones that did not report.....all reported normally.
For S&Gs, I entered 9000ms. This seemed to work.
Something happens within the manager when you have over a certain amount to scan.
-Shane
|
|
By Yury Averkiev (s-code) - Saturday, September 05, 2009
|
|
Something happens within the manager when you have over a certain amount to scan.
This could be the case. We don't have that' many computers to test with. We have about mix of about 20 Vista/XP/2008/2003 Hyper-V virtual machines that we use for testing. In our test we haven't seen the problem described in this thread, but again we haven't tested against 100+ computers. By any chance, can we get access to your network via VPN and run VNC/RDP/SSH status updater against your computers? We don't even need to know their VNC password to run the scan and of course we will be willing to sign an NDS, etc. If it's possible please email to support@s-code.com so we could discuss it further.
|
|
By Nelson-BBB - Thursday, October 01, 2009
|
|
The status check appears to be working again in 5.0.10 - tried it on 2 different installs and it looks good. Thanks!
|