I'm new to this forum and hope to get some help here. Thanx in advance I have one WIN XP 32bit and one WIN 7 Home 64bit pc. For security reasons I want to use DSM plugin to make connection from WIN7 to WIN XP over the Internet. Without DSM plugin I can connect with no problem. When I want to use DSM plugin it seems to me that the 32bit version is not compatible with the 64bit version, is that right?Can anyone please give me a hint on how to connect the two mentioned PCs with using DSM plugin, please?A second question would be if it is necessary to use DSM plugin for security reasons if I would use a VPN connection instead?

There is a 32bit(SecureVNCPlugin.dsm) plugin and a 64bit (SecureVNCPlugin64.dsm) plugin.

Using a 32bit dsmplugin with a 64bit winvnc.exe/vncviewer.exe -> failUsing a 64bit dsmplugin with a 32bit winvnc.exe/vncviewer.exe ->failUsing a 32bit dsmplugin with a 32bit winvnc.ex/vncviewer.exee ->OKUsing a 64bit dsmplugin with a 64bit winvnc.exe/vncviewer.exe ->OK

I can connect to a remote 32-bit test/dev (Win2003) server from 64-bit Thinkpad (Windows 7 KVM) at first using UltraVNC but then the next day cannot connect again. It hangs on Negotiating Protocol Version or get and error about a DSMPlugin missing. The workaround is to use RDC and do a physical reboot of the 32-bit test/dev server, then I can connect with UltraVNC again from the Thinkpad. So something expires on the 32-bit server for UltraVNC after about 24 hours. Where do I get the right DSMPlugin for the 32-bit server?

There are no expires in ultravnc.You are using the correct plugins, else it would not work at all.Looks like the server ( running as service) get blocked...possible caused by some port scanners or other software scanningthe default vnc ports.

*try to activate the winvnc.log logging, possible there is some clue in the debug*update the the pre-release 1.2.0.8 possible it's something that's fixed*using another port then the default one