UltraVNC

http://www.uvnc.com/pchelpware/sc/creator.html

there are three creators on this page... if you use the bottom creator it supports uac:

"Update 27/08/2009, the user is only asked once to give UAC permission ( add [DIS_AUC] )
helpdesk.txt
[DIS_UAC]"

i'm not sure what to make of that comment, and i ...

i would rather see the password field filled with the letter "l" (the lowercase letter "L") - but also using the wingdings font. this would result in a black dot for each character - just like the password fields in windows xp.

sweet, i've been waiting for this. i haven't had much time to test it thoroughly, but it seemed to work fine for me on the two basic tests that i ran.

i also wanted to mention that the about screen shows "sc 20.3" instead of "sc rel 1.0.0".

i know that when using ms login and ms login ii we are going for better security.

and i wouldn't want to store my user/pass combination in any resulting .vnc file.

but i'm wondering about something...

in windows xp when i attempt to access a network resource, my windows login credentials are ...

i'm not sure of anything at this point.

i'm pretty sure i asked about firewalls already.

yeah, i did...

additionally, are there any firewalls running that might block the connection?
I have configured my firewall for the incoming connection.
no specific information though... like... are ports ...

ok i am going to be out for a few hours but when i get home i will go over the entire post again. we will get it.

i can't remember, but if you aren't using 20.5, install it on both computers and then try again.

also, when building the sc on the sc page, use the top one, 20+.

try some stuff, i'll ...

np.

ok, it's time to test it per rudi's instructions.

in helpdesk, remove the -plugin info

then rebuild sc

start your viewer/listener without the -dsmplugin options

try the connection again

ok, in one of my earlier posts here i mentioned that the "start in" field had to contain the full path to your ultravnc folder. it has to be in quotes.

ex: "C:\Program Files\UltraVNC\"

what is the "start in" field for your vncviewer listen shortcut?

the target looks ok, but what is the "start in"?

SC (custom zip/exe) ships with a file named MSRC4Plugin.dsm. do not attempt to use any other file - you have to use this one only inside your SC package. do not attempt to rename it either.

all i mentioned was to change your vnc viewer shortcut to something like this:

"C:\Program Files\UltraVNC ...

ok, you are almost all done (believe it or not)...

your vnc listener shortcut MUST use the NOREG dsmplugin. with SC you cannot use the normal dsmplugin in your vncviewer/listener command line.

so, change your target to this:

"C:\Program Files\UltraVNC\vncviewer.exe" -listen 5500 -dsmplugin ...

also... are you opposed to trying 20.5?

i can't help but think that we are wasting our time trying to debug an old version.

try 20.5 and let me know.

it is definitely working in both directions for me:

winxp sc request -> win98se listener
win98se sc request -> winxp listener

i am also using the msrc4 plugin with matching rc4.key files at each end (one rc4.key is built into the sc).

my listener shortcut:

target: "C:\Program Files\UltraVNC ...

ok, let me try to duplicate this scenario.

give me 10 minutes...

and what about the host settings in helpdesk.txt?

is it calling for a plugin?

if so, does your sc package include the dsmplugin + rc4.key?

additionally, are there any firewalls running that might block the connection?

search the forum (links at top) for dual monitor.

i have seen several posts about it, so i'm sure there are issues with it... but since i don't have dual monitors (yet), i haven't studied any of the threads or any possible work arounds.

heh sorry :/

hmm my fingers are still numb from this morning ...

I have set my win98se to user-level access control. Is that really necessary? I would like it not to be.
yes, user-level access control is currently required.

before i start, for debugging this issue, please test everything with the msrc4 dsm plugin disabled on the server (winvnc) and viewer ...

how exactly are you running the listen server?

that's important.

and what version of the sc creator did you use? the newer 20+? or the older 20?

the new crypto fixed the problem.

thanks for your help!

hopefully this post will be a little more worthy than my last one here ahem.

this is a feature request more than anything.

there are three things that i would like to see changed in sc if at all possible.

1) this has been posted, so i will keep it short: a "connect" button. almost everyone agrees ...

i'm holding out.

someday we will have the power!

it's almost good that i can't delete it. cuz sure enough, someone will drop by and see this post and think "damn, that's my problem exactly lol good thing i didn't post it and look stupid like that jerk did haha!"

lol...

well, that was the quickest solution ever.

my shortcut's "target":

"C:\Program Files\UltraVNC\vncviewer.exe" -listen 5500 -dsmplugin msrc4plugin_noreg.dsm

however, the shorcut's "start in" folder was blank - when using the noreg dsm plugin you must include the correct path for "start in":

"C ...

i am running ultravnc 1.0.0 rc 20.5 and i've tried the 20.5 and 20.6 versions of vncviewer.

all attempts to run sc's that were built against the rc 20+ custom.zip are all now failing to connect with the following error:

the plugin cannot be loaded.
please check it's name integrity.

i'm going to ...

ok, done

i think i am having the same problem. ugh.

i posted a new topic here:

[post=9846][/post]

from the dsmplugin readme:

"Supports 128bit on Windows 95 osr2 -> Windows 2003 (Win 95/98 require High Encryption Pack)"

really? cuz i'm having no luck at all under windows 98.

i built an rc4.key file with vncviewer on a windows xp system, then i copied it to other systems. all of the xp boxes ...

i was talking to my brother on the phone last night and i found another scenario where an ini file containing admins/users would be prefered as opposed to using ms login ii.

ms login ii requires that "forceguest" is disabled. changing this setting turns on advanced file sharing mode. my brother ...

on the win9x box i moved authadmin.dll out of the ultravnc folder and restarted the service - i then logged in with the test account again - but i still had full access. the test user account is only in the vncusers group, and vncusers is only in group 3 of ms login.

i am running two global groups on my nt4 domain controller, vncadmins and vncusers.

for that machine and for win9x clients in that domain i am using ms login (not ms login ii).

in ms login, the 1st group is set to vncadmins (all caps), the 2nd group is intentionally left blank and the 3rd group is ...

as we all know, ms login ii will not work unless the forceguest setting is turned off in windows xp. many topics in this forum mention editing the registry and changing the forceguest setting from 1 (default) to 0. while this method is 100% effective, it forces end users to modify settings in the ...