Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote Desktop Connection and local drive/printers

Status
Not open for further replies.

mtanner01

Technical User
Nov 20, 2001
34
CA
We have just installed and Windows 2000 Terminal Server, and are currently testing user connectivity.

One thing we would like to do is allow users to see their local PC drive and printers in the Remote Session. In the Options settings for the Remote Desktop Connection we have selected these options, but it does not work. We can not see the local PC drives and have no means of copying files from the Remote Session to the Local PC drive.

Any suggestions or advice would be greatly appreciated. If at all possible I would like to avoid adding a 3rd party software for this process, as we will not have a lot of users requiring this.

Thanks!
Marlene (o:
 
Okay.. The rules are different with Windows 2000 Terminal Server. When MS licensed the TermServ technology from Citrix, one of the restrictions that was put on the license was no automapping of drives--like citrix does.

Assuming these pcs are part of the domain, you could map a drive from the server to the client pc and do it that way. Infact, that's what MS says to do--somehwere on their site.

The Printers should typically map w/o any problem. The server has to have the driver available first. If not, it will not map to any of the client printers.

There is also a patch on MS's site (don't have the link, but it comes up in a search) that will allow you to C&P files between Termserv sessions.

-Iota
 
I have read a lot about this and see the issue with the automatic mapping of local drives.

The only information I can find on patching C&P Files is relating to the first/original version of Terminal Services Client, which I have found.

We are using the latest version of Remote Desktop Connection, and do not believe the same patch applies. I did a piece of information about updating the RDP connection to allow Virtual Channels which has helped fix this problem on my W2K and NT4 boxes, but still issues with Win98 clients.

Any additional help would be greatly appreciated.

-Marlene
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top