UltraVNC

osm, I recommend the use of InstallWatchPro (freeware), which takes a snapshot of the file system and Registry before and after an installation, to show you every change that it makes.

Those graphics are great, Exillion. Don't get discouraged because they're not quite right for UltraVNC...the actual designs are very well done, and we should be glad to have someone with such talent taking an interest. A little tweaking based on what redge said and you may have some winners.

As for the file transfer, enable View Only before you connect and then initiate the file transfer. The people on the other end shouldn't notice anything.

Does the INI file you create automatically match one that works when you create it manually?

There are a couple other settings that directly affect whether UltraVNC uses MS Logon:
I've found that NewMSLogon doesn't work very well, so I use the old one.

That's pretty much what I did...install UVNC the way you want it and pull those preconfigured files into an installer.

You'll have to install the service at the end of the file copy on the new machine, of course.

You're trying to misrepresent what you're doing on the computer when someone connects in to the server to watch you, much like in the movies when they put a picture in front of a security camera's lens? Can't be done. What you see is what they see. Although, I suppose if you had a second computer ...

If you use the MSLogon authentication scheme (http://www.uvnc.com/features/authentica ... l#mslogon1) you can set up multiple accounts for logon.

BarqMulch, if the windows firewall on .109 is turned off and the service is disabled i should be good right? Just turning off the firewall should eliminate it as the problem, if it still doesn't work. You should also make sure there's no other firewall programs on there, like ZoneAlarm or Norton ...

from workstation: destination IP x.x.x.x port 5901, result: port is filtered from server0: (dont know if this is a valid test or not but did it anyway) destination IP x.x.x.x port 5901, result: port is listening my router port forwarding page looks like this: VNC1 5900 to 5900 TCP 192.168.1.2 ...

port forwards are as follows vnc0 5900 to 5900 TCP 192.168.1.2 enabled (this is the server of the domain) vnc1 5901 to 5901 TCP 192.168.1.109 enabled (this is an xp pro work station). Is it as simple as not having set .109's VNC server to run on port 5901? If you didn't specify, then it's still ...

I am experiencing this problem in v1.02 and 1.04RC16, so it seems like a long-time issue. If we use an UltraVNC Viewer without encryption to connect to an UltraVNC Server with encryption we get a message that encryption needs to be enabled, but if we use a Viewer with encryption connecting to a ...

Hi dwilson, I had the same problem. I made a script that performs the following commands, which uninstalls the old VNC server and installs the new one: Make a UVNCSetup.bat file from the commands below and copy it, the UltraVNC-101-Setup.exe and UltraVncDriverSetupSilent.exe to the desktop on the ...