Well,
I know about the net stop/start stuff. My problem is how to get the registry
settings into the remote machine. It seems like it simply will not allow that
to happen...
I needed a command line trick that does not throw up a GUI dialogue. I can get
to the command line prompt on that machine bu no further because of the
registry thing.
Here is a solution that works!
Avi Solomon [[EMAIL PROTECTED]] posted (using the very off-topic subject
"RE: vnc-list-digest V1 #1139" a solution that actually worked:
"The other thing you can do is export the registry key(s) from the working
machine and create a .REG file containing the correct information to be
pushed to the Win2000 machine. Then, in a login script or batch file, put
the command REGEDIT /S <FILENAME>.REG. When executed on the Win2000 machine,
the registry entries will silently install into the proper location."
So I used Regedit and saved the ORL tree to a reg file, then made a batch file
according to the tip above. Then I copied it via VPN on to the remote
machine's har disk.
Finally I connected using RConsole and executed the bat file.
Then I did net start "VNC Server" (it was stopped before) and lo-and-behold!
Now it is finally possible to connect with VNC over the VPN tunnel via
Internet!
I am finally there....
And note that the binary data imported just fine, the password is exactly as I
set it on my local machine.
/Bo
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jim Millard
Sent: Sunday, May 20, 2001 10:53 PM
To: [EMAIL PROTECTED]
Subject: Re: VNC server remote install on W2000 Pro, help with registry
wanted!
Bo,
>I am about done with the remote install of the VNC server on my remote W2000
>Pro machine, there is "only" the small part about setting the password
>left...
[snip]
Recall that the registry is only read when the server starts up and
initializes. If you didn't have the password, then the server is displaying
the properties dialog, waiting to have the password set. With no
interaction, the password won't get set even if you later put it into the
registry.
My suggestion:
1) do a "net stop" to kill the server that you started before setting the
password
2) verify that a password hash is in the expected registry location, and
that it's the right type (BINARY, which can't be imported using a .REG file)
3) do a "net start" to re-load using the registry settings
--
Jim Millard
+--------------------------------------------------------------+
Kansas City, MO http://www.millard.org/
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
