Re: Is it possible to map a drive over 3389 using 2003 TS + remote desktop ?

From: scott (nospamscott_at_yahoo.com)
Date: 11/01/04 

Date: Mon, 1 Nov 2004 11:18:57 -0000

Thanks for reply.

- On which computer is the batch file to run: the server or the client?

Was initially thinking of the batch file running on the server - looking for
file on client to copy. I guess the client could run batch file and copy to
a server share. But same problem exists over RDP that you cant really use
batch file to copy to a share as shares (map drives) dont work over RDP.

- 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.

Was thinking of doing it the other way around i.e the TERMINAL SERVER
SESSION finds a path to the clinet share and creates a map drive.

- 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.

I have setup many VPNs but this customer already has 2003 + Remote desktop
in place so was trying to think of a way around it.

- 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.

This sounds interesting. How would i set this up for a file to be trasfered
from the clinet to the server ?

- 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.

Aware of the risks, was just an example as the default file ends up on the c
drive.

Thank for advice.
Scott

Relevant Pages

  • Re: Client behind a firewall!
    ... Microsoft MVP - Terminal Server ... Internet with Remote Desktop enabled when I'm at work, ... Remote Desktop client is blocked, and I just can't use it. ...
    (microsoft.public.windows.terminal_services)
  • Re: 4912: Cannot update the already existing object. Need some he
    ... Also, as far as the client pointing to the wrong server, you should use SMS ... SP3 client through a logon batch file. ...
    (microsoft.public.sms.admin)
  • RE: VBScript: Remote Desktop Disconnected
    ... VBScript: Remote Desktop Disconnected ... The client could not connect to the remote computer. ... I suggest we try to rerun the CEICW to confirm the RWW is properly ... On the SBS 2003 Server open the Server Management console. ...
    (microsoft.public.windows.server.sbs)
  • Re: Can not Remote access to Server
    ... >>Remote Desktop, or PcAnywhere? ... >>> I have never able to run Remote Desktop Connection to ... >>> Server, so, I install PCANYWHERE on server. ... Remote Desktop Client? ...
    (microsoft.public.windows.server.setup)
  • Re: Client behind a firewall!
    ... Internet with Remote Desktop enabled when I'm at work, ... ISA Server proxy, which will only let HTTP traffic through; ... Remote Desktop client is blocked, and I just can't use it. ...
    (microsoft.public.windows.terminal_services)