Re: Is it possible to map a drive over 3389 using 2003 TS + remote desktop ?
From: Robin Walker (rdhw_at_cam.ac.uk)
Date: 11/01/04
- Next message: h_at_@STER: "RE: The client could not connect to the remote computer"
- Previous message: Hugh: "RE: The client could not connect to the remote computer"
- In reply to: scott: "Is it possible to map a drive over 3389 using 2003 TS + remote desktop ?"
- Next in thread: scott: "Re: Is it possible to map a drive over 3389 using 2003 TS + remote desktop ?"
- Reply: scott: "Re: Is it possible to map a drive over 3389 using 2003 TS + remote desktop ?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 1 Nov 2004 10:59:54 -0000
"scott" <nospamscott@yahoo.com> wrote in message
news:ur3aqw$vEHA.2568@TK2MSFTNGP10.phx.gbl
>
> Im trying to figure out if its possible to map a drive from a XP
> workstation running Remote Desktop connecting to a 2003 terminal
> server over the net to port 3389 ?
>
> I understand you can share the workstation "DRIVES" within Remote
> Desktop which makes them available under My Computer on the Terminal
> Server Desktop - but I need to actually MAP these drive i.e
> NET USE L: \\clinet\cdrive so I can run a scheduled batch file.
On which computer is the batch file to run: the server or the client?
> The batch file will not run unless the drive is mapped as it cant
> find the host when the clinet c drive is shared using the Remote
> Desktop option. When using Remote Desktop share option the C drive is
> available on the TS desktop as an "OTHER" drive.
You are confusing Remote Desktop with File Sharing. No, you cannot map
server resources onto a client drive with Remote Desktop. The client
computer is quite unaware of the Remote Desktop session, which is contained
totally within the RDP client application.
[Apart from anything else, this is one of the strengths of Remote Desktop:
no matter what malware is running in the client, that malware cannot access
server resources in the RDP session: it needs to be a server-based
application that performs any data transfer between the two file systems].
If you want to do file-sharing or copying between remote PCs, then you need
to set up a VPN between them. The VPN arrangements will be quite indepedent
of Remote Desktop arrangements. You can set up a scheduled job which will
connect the VPN, run a copy command, and then disconnect the VPN again.
Alternatively, you might arrange for a start-up process in the RDP sessions
on the server to run a timed transfer of data between the local server
disks, and the client file-system mounted as remote drives, so that while
users are logged on via RDP, the transfers take place as timed activities
within their server sessions.
By the way, although your example of a NET USE command above is only an
example, it is bad practice in terms of security to share the root of the C
drive over a network: it exposes very many vulnerabilities, especially if
the share is writable. You should share only the directory you need to
share, and that directory should not be part of the C:\WINDOWS hierarchy, or
include it.
-- Robin Walker rdhw@cam.ac.uk
- Next message: h_at_@STER: "RE: The client could not connect to the remote computer"
- Previous message: Hugh: "RE: The client could not connect to the remote computer"
- In reply to: scott: "Is it possible to map a drive over 3389 using 2003 TS + remote desktop ?"
- Next in thread: scott: "Re: Is it possible to map a drive over 3389 using 2003 TS + remote desktop ?"
- Reply: scott: "Re: Is it possible to map a drive over 3389 using 2003 TS + remote desktop ?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
