4.0.3.0b installed WONDERFUL! has resolved the major issue of not being able apply default vnc settings to 'Dynamic Search Folders', big help...thanks!

There is however what I believe to be new bugs;

1.) When you multi -select (CTRL+CLICK) several computers from the list in a group in 'Dynamic Search Folder', when you right click (for example roll out VNC) it unselects all computers except for the one you click on.  This doesn't happen all the time, but probably 70% of the time, this DEFINATELY wasn't the case in 4.0.2.0b and earlier.

2.) You cannot set the option to 'Enable automatic scan every xx minutes' in Options > Network Scan > Edit Default Settings, when you check the option and click OK, it doesn't save the changes, when you go back into it, it's unchecked again!

3.) The 'Clear server list before scan option in Options > Network Scan > Edit Default Settings doesn't do anything, unlike point 2 it does keep the option but doesn't actually work!

4.) Not sure if it's a bug, but if you change the name of a PC, the network scan still picks up the old name (even if you delete the computer from VNCM) (This is problematic as I'm finding it picking up the original name from the SOE image. not the current name)

Some Wish List Items!

1.) The ability for a network scan to identify when a computer has changed IP address and update the record rather than create a new computer (DHCP Networks)

2.) The ability to create custom toolbars, with custom commands (ie a rollout VNC button/send message to console button) on a toolbar.

Regards,
Graeme Lucas

Some Wish List Items!

You are correct, this is a issues with WINS lookup, deleting the record in WINS resolves the issue!

Thanks!

Regards,
Graeme Lucas

VERY strange, I've since tried this again and it's okay now, but it happened on three different occasions (I always try and rectify the problem and testing it on multiple PC's before reporting it!)

Correct but VNC Manager only seems to resolve the mac address on the local subnet, I'm presuming but scanning packets? nbtstat lookups does resolve the MAC address, so I'm presuming VNCM doesn't use that method!

Regards,
Graeme Lucas

Would this likely be changed in the future considering it's a known limitation it can only obtain mac address from computers on the same subnet?

Regards,
Graeme Lucas

Excellent, it's an on and off problem, since my last post it certainly has happened again!

Thanks for your continued support, it's very much appreciated

Regards,
Graeme Lucas