We are very interested in VNC Manager, but just cannot get it to work at all.

We need to be able to scan for active VNC and RDP servers. Scanning on either potr does not find any servers at all, which effectively means we cannot use the software. We want to use to manage all internal servers, and all of our clients servers which are connected using VPN tunnels. Why does it never find anything? Yes I am running on XPSP2, but VNC admin console finds all the servers fine. I prefer this software, but if we cannot get it to scan we cannot use it.

Please help!

Thanks

First of all, VNC Manager v2.5 cannot scan for RDP servers. He is only capable to find VNC ones. RDP scan has been implemented just a few days ago and will be included in v3.0.
As for VNC servers scan, I think you should try to increase a timeout value. Can you please try to change it and let us know if it helped?

I tried at 1000 miliseconds, and it just doesn't get anything. Even on the local LAN, which has a 100MBps switch.

Any other ideas?

Thanks

Ok I will try the live support, thanks.

Looking forward to the version that will scan for RDP clients as well, as not all of our Pcs have VNC on.

I fixed the problem by simply reinstalling the program.

Also removed VNc Manager at the same time, so maybe that helped.

Working great now, I love this program!

Glad to hear that it's fixed. 

Yury,

Maybe you need to make a Category in the forums called FAQ's and add this in there.  If their are people migrating from vnc Console to VNC Manager it might help them to reference this and also help us to remember what the fix to the problem actually was.  Also could be useful for other things.

Adam

Actually I still have the problem...I thought it had gone, but it seems that sometimes it works and sometimes it doesn't.

If I restart the program, often it will scan a couple of PCs correctly. If I then add a whole subnet, or range of subnets, it just scans through and finds nothing.

Once that has happened, if I scan a PC that I know is there, it doesn't find it. It is not a timeout problem-  increasing or scanning PCs on the LAN makes no difference.

Any other ideas?

If it's not timeout than I see only two possible reasons:

1. VNC server has built-in antihacking mechanism, which is supposed to prevent bruteforce attacks. What it does is that if you try to connect to same server several times within very short period of time, it simply starts rejecting your connections. During testing we saw such behavior several times. After that nor scanner neither VNC viewer weren't able to establish connection. In this case you either have to wait.. I think after 5 or 10 minutes server stops rejecting connection or you just have to restart the VNC server.
2. The problem could be that on XP SP2, tcpip.sys still blocks scanner connections. We have improved this situation and now it happens in very rare case, but still it happens sometimes. If it's tcpip.sys problem, the you will see 4226 event id's in Event Viewer under System folder.