SmartCode Solutions Web Forum

I've found another bug in VNC manager 4.0.3.0b, it may very well been in previous versions as well.

I have been setting up a customised version of UltraVNC SingleClick (SC) to connect to machines not on our domain, but connected using our VPN connection, where rolling out VNC through VNCM is impossible because of the lack of authority on the remote PC.

I was doing some testing, and clicked on the 'Run Listening VNC Viewer' service, and initiated the SC on the remote PC, it worked a treat fantastic!

The problem is as soon as it's disconnected, VNCM no longer has the ability to run a network search, instead no matter which Search Folder you run a scan, it ONLY finds the PC I connected to with SC! Even if it's IP address doesn't lie within the 'scope' of the search!

Strange! So I wanted to find out if the problem is caused by SC or by VNCM, so i did a restore of VNCM that i did earlier in the day, before testing SC and Hey presto, problem solved.

I then compared the config.xml file to the 'broken' config.xml file and found there was a difference.

In the 'broken' config.xml file theres the following string.

</vmrc></group_computer></dynamic_search_folder><server name="" storage="2"><ip>10.3.32.72</ip><default_action val="0" />

Comparing that with the 'working' config.xml, this is the same string.

</vmrc></group_computer></dynamic_search_folder><server name="" storage="2"><ip></ip><default_action val="0" />

10.3.32.72 being the IP address of the PC I used SC on. So I edited the config.xml and removed the IP address, hey presto problem solved!

I've concluded that once you've connect to a computer in listening mode, it must get stuck to that PC and cannot see anywhere else!

I've attached some screenshots;

working.jpg is of a Default Search Folder network scan (F8), you'll notice several computers respond and i get the healthy green ticks!

notworking.jpg is straight after I've connected to a computer using listening mode, you'll notice it only finds one PC, it appears to 'spoof' the name of a computer already in the list (the actual computer on that IP address is not called that), and it doesn't find any others! Also the computer it does find has an IP address outside the scope of the search (10.3.32.72 NOT 10.4.16.100-10.4.16.139) It also finds this computer almost instantly!

Any suggestions?

 This only happens once a connection is initiated.  Clicking on listening mode then closing it doesn't cause VNCM to malfunction.

Thanks in advance,

Graeme Lucas

Regards,
Graeme Lucas

notworking.JPG (108 views, 35.08 KB)
working.jpg (104 views, 33.04 KB)

1.) go to http://freehost04.websamba.com/duckware/testsc/testsc.htm and download  the 'client pc' file on the left onto any machine on your network.

2.) On a machine with VNCM installed first do a quick search on any 'dynamic search folder' group, I'm assuming this will work.

3.) Set VNCM to go into listening mode CTRL+L.

4.) Run the client.exe file on another machine, and enter the ip address of the machine that's in listening mode .

The PC should now connect and you should be able to control as per normal!

5.) Disconnect the connection from either end.

6.) Do another quick search, and it should now be broken (only find a computer with a spoofed name with the same IP address of the computer you ran client.exe on)

7.) Close VNCM, find the config.xml file and do a text search on the file for the offending IP address.

8.) Remove the ip address, save + exit

9.) Open VNCM and search again, it should now be fixed!

 

Regards,
Graeme Lucas

once you've broken vncm, you need to shut it, open it then shut it again before it updates the config.xml file!

Regards,
Graeme Lucas

So could you please email us at support@s-code.com content of the configuration folder (please include all the files) and we will try to reproduce the bug using your configuration files.


We are looking for investors and business partners. Please contact us for more details

Kindest Regards,
SmartCode Solutions Support

It's a strange one, but I've certainly managed to replicate the problem on several machines in the office, so perhaps it's something to do with our config??

Maybe I could somehow record the steps taken and post that if you can't find anything in the config files?

Thanks for this info

Will await your reply

Regards,
Graeme Lucas