TightVNC vs regular VNC

Germain, Bob Bob.Germain "at" ferrazshawmut.com
Mon, 06 Aug 2001 20:40:53 +0000


You can connect to a share in a DOS window with the follwoing command:
net use * \\servername\sharename.  This will map the next available drive
letter on your machine to the share on the server.  You can do this on any
server (with the proper permissions) regardless of VNC.

>From there you can use Windows Explorer to copy from one directory (e.g. on
your machine) to another (i.e., the server's share/directory).

Bob Germain

-----Original Message-----
From: BugTraq Recipient [mailto:bugtraq "at" brianrea.org]
Sent: Monday, August 06, 2001 3:13 PM
To: vnc-list "at" uk.research.att.com
Subject: Re: TightVNC vs regular VNC


> 1. Run Server Manager and stop the VNC service on the remote machine.
> 2. Map a drive to the location where the VNC programs are installed on the
> remote machine.
> 3. Copy the the TightVNC files over the original VNC files on the remote
> machine.
> 4. Re-start the VNC service (using Server Manager).
> You should now be able to connect using VNC!
>
> Let me know if I'm missing something...

how is the remote admin going to perform steps two and three if he loses his
remote VNC hands after step one?
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------