UltraVNC

I'll second that. NTLM pass-through authentication would be very useful. But it might not be a trivial exercise to implement it.

Could you provide more detail to how you set this up ? I actually been fighting to make fast push work for me..... Not at the moment, but it was fairly trivial. When I have some time I'll hack fastpush 7.2 beta and feed back my changes to the fastpush author. No point in a howto for an unsupported ...

Kevin wrote:How can this be pushed out in a domain environment with the MSLOGON groups intact ?

I use a modified version of VNC Fastpush 6.5, using Sysinternals' psexec to remotely run mslogonacl.exe on the target PC.

That's it! "domain\user" or "machine\user" is working for me with authSSP_NT4.dll. It would be nice to assume first "machine" if only username is specified, and as a second try if there is no local account "user" to assume "domain". Maybe it's possible to use the registry-value "CachePrimaryDomain ...

Phew, glad it's not just me.

Phil

Well, almost there, but...

No more secur32.dll warnings but it still will not authenticate.

If file transfer is disabled on the server, then the file transfer button (and menu item) in VNCViewer should be grayed out. Does not the server report its capabilities when the viewer connects? The confusing message when you try is a pain in the neck, because you don't know without looking ...

Excellent!

Martin,

It still complains that it wants secur32.dll and doesn't authenticate, even with the latest AuthSSP.dll.

Sorry I wasn't clear about that,

Phil

Martin,

This still doesn't work with Rudi's latest pre-RC197 winvnc.exe builds. Should it?

Phil

Marscha wrote: aclui.dll is called with /delayload option to allow operation on NT4 and Win9x.

Does this mean that the security configuration manager is no longer needed on NT 4 boxes?

Thanks for the feedback. Currently this new ms-logon feature is not really integrated with the rest of ultravnc because - it is indeed very new - it is supposed to change further - there's very limited feedback until now Once it's more stable it will be integrated into the 'normal' releases :wink ...

You could peek at Mozilla's Bug 231529 which seeks to do the same thing

Optionally would be better. Some people may think that those registry changes are somewhat intrusive. The solution, if possible, is to do the following on a VNC-sent reboot request: 1: Save current values of those keys 2: Put something into the RunOnce on startup to restore those values (you could ...