If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
Remote Desktop - How to access the remote drive locally ?
Hello All,
I would like to copy some files to and from the Remote Desktop connected computer to the local one. Point is that I want to share the remote drive with the local computer, not the other way around (local drive sharing with remote computer). How do I do this ? Google only seems to have info about the latter method. If that is not possible, is there any way to limit the remote computer in what it can access on the local one (like only giving it access to a single folder) ? Regards, Rudy Wieser |
#2
|
|||
|
|||
Remote Desktop - How to access the remote drive locally ?
R.Wieser wrote:
Hello All, I would like to copy some files to and from the Remote Desktop connected computer to the local one. Point is that I want to share the remote drive with the local computer, not the other way around (local drive sharing with remote computer). How do I do this ? Google only seems to have info about the latter method. If that is not possible, is there any way to limit the remote computer in what it can access on the local one (like only giving it access to a single folder) ? Regards, Rudy Wieser File sharing, if you're on the same LAN. In My Computer, click a folder, then click Share This Folder. Ignore the wizard, Just Share Anyway. You can allow remote write or not. -- On the internet, nobody knows you're a jerk. |
#4
|
|||
|
|||
Remote Desktop - How to access the remote drive locally ?
From: "R.Wieser"
Hello All, I would like to copy some files to and from the Remote Desktop connected computer to the local one. Point is that I want to share the remote drive with the local computer, not the other way around (local drive sharing with remote computer). How do I do this ? Google only seems to have info about the latter method. If that is not possible, is there any way to limit the remote computer in what it can access on the local one (like only giving it access to a single folder) ? Regards, Rudy Wieser Just Copy and Paste. That's it. Treat the RDP as a Window and load whatever Folder on whatever PC you want to copy to or copy from. Choose the files and/or folders and choose "Copy" then go to the destination and choose "Paste". You can't use Drag 'n Drop over RDP. You can't move, only copy. The source file(s) will not be deleted. I use this scenario... Server 2008 Domain behind a NAT Router. RDP, TCP Port 3389, is Port-Forwarded to Server 2008. Server 2008 has Firewall Rules to block ingress from networks not allowed RDP access. Domain Participant computers can be accessed from the Server 2008 via RDP. Thus I can open a RDP Session with the server then open a RDP session ( from the POV of the server ) with a Domain Participant computer and I can copy a file(s) to any of the Domain Participant computers. NOTE: RDP security has been improved with Vista and above and its another reasonm to drop XP if you want to use RDP nad take advantage of the increased data security models. -- Dave Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk http://www.pctipp.ch/downloads/dl/35905.asp |
#5
|
|||
|
|||
Remote Desktop - How to access the remote drive locally ?
David,
Just Copy and Paste. That's it. I already go the feeling that that might be the only way to do it. Oh well, if it doesn't go like I want, it has to go as it allows I guess. :-) I have to say that I find it a bit remarkable, from a security perspective, that the target, server computer must have access to the local, client computer to be able to transfer files. If that target computer has any kind of infection it could (I think) easily (and silently?) infect the client too. Regards, Rudy Wieser -- Origional message: David H. Lipman schreef in berichtnieuws ... Just Copy and Paste. That's it. Treat the RDP as a Window and load whatever Folder on whatever PC you want to copy to or copy from. Choose the files and/or folders and choose "Copy" then go to the destination and choose "Paste". You can't use Drag 'n Drop over RDP. You can't move, only copy. The source file(s) will not be deleted. I use this scenario... Server 2008 Domain behind a NAT Router. RDP, TCP Port 3389, is Port-Forwarded to Server 2008. Server 2008 has Firewall Rules to block ingress from networks not allowed RDP access. Domain Participant computers can be accessed from the Server 2008 via RDP. Thus I can open a RDP Session with the server then open a RDP session from the POV of the server ) with a Domain Participant computer and I can copy a file(s) to any of the Domain Participant computers. NOTE: RDP security has been improved with Vista and above and its another reasonm to drop XP if you want to use RDP nad take advantage of the increased data security models. -- Dave Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk http://www.pctipp.ch/downloads/dl/35905.asp |
#6
|
|||
|
|||
Remote Desktop - How to access the remote drive locally ?
From: "R.Wieser"
David, Just Copy and Paste. That's it. I already go the feeling that that might be the only way to do it. Oh well, if it doesn't go like I want, it has to go as it allows I guess. :-) I have to say that I find it a bit remarkable, from a security perspective, that the target, server computer must have access to the local, client computer to be able to transfer files. If that target computer has any kind of infection it could (I think) easily (and silently?) infect the client too. Huh ? No. First you can change the XDaemon port from TCP port 3389 to another, unepected, port. Secondly you should the TCP connection as a tunnel where the screen, keystrokes, mouse movements, sound, etc., and files travel through. This tunnel uses encryption and authentication. Malware is not sophiticated enough to "worm" through RDP. However onnce the tunnel has been created based upon authentication, it is possible that malware can be passed through the tunnel. This is a case of what is called the "Insider Threat" and would exist if you had physical access or RDP access. But, that is why there are layers and protocols to limit the use of RDP to help eliminate the threat. In the client-server model this is always present. RDP is just an extension of the client-server model. -- Dave Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk http://www.pctipp.ch/downloads/dl/35905.asp |
#7
|
|||
|
|||
Remote Desktop - How to access the remote drive locally ?
David,
Huh ? Well, this is what it looks to me: The Remote computer is allowed, because of the necessity of copying, access to a drive on the client machine. As I've not seen any restrictions to that this means that the remote machine can read, write and alter anything on that drive. Now if the remote machine is infected with anything, isn't that (the attached drive) the perfect place to see if any files/executables can be found to store some viri-offspring in ? However onnce the tunnel has been created based upon authentication, it is possible that malware can be passed through the tunnel. Yes, thats always a possibility. But do we really need to open the barn doors for any viri that are in search for files to infect by giving the remote machine full access to our/a local drive ? In other words, its not about which port the data is coming thru, or how many bits the encryption key is. Its way simpler to exploit than that. If you know anything that proves me wrong than please do so, as I do now not at all feel at ease using Remote Desktop. Regards, Rudy Wieser -- Origional message: David H. Lipman schreef in berichtnieuws ... Huh ? No. First you can change the XDaemon port from TCP port 3389 to another, unepected, port. Secondly you should the TCP connection as a tunnel where the screen, keystrokes, mouse movements, sound, etc., and files travel through. This tunnel uses encryption and authentication. Malware is not sophiticated enough to "worm" through RDP. However onnce the tunnel has been created based upon authentication, it is possible that malware can be passed through the tunnel. This is a case of what is called the "Insider Threat" and would exist if you had physical access or RDP access. But, that is why there are layers and protocols to limit the use of RDP to help eliminate the threat. In the client-server model this is always present. RDP is just an extension of the client-server model. -- Dave Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk http://www.pctipp.ch/downloads/dl/35905.asp |
#8
|
|||
|
|||
Remote Desktop - How to access the remote drive locally ?
From: "R.Wieser"
David, Huh ? Well, this is what it looks to me: The Remote computer is allowed, because of the necessity of copying, access to a drive on the client machine. As I've not seen any restrictions to that this means that the remote machine can read, write and alter anything on that drive. Now if the remote machine is infected with anything, isn't that (the attached drive) the perfect place to see if any files/executables can be found to store some viri-offspring in ? However onnce the tunnel has been created based upon authentication, it is possible that malware can be passed through the tunnel. Yes, thats always a possibility. But do we really need to open the barn doors for any viri that are in search for files to infect by giving the remote machine full access to our/a local drive ? In other words, its not about which port the data is coming thru, or how many bits the encryption key is. Its way simpler to exploit than that. If you know anything that proves me wrong than please do so, as I do now not at all feel at ease using Remote Desktop. Regards, Rudy Wieser Don't use it then. -- Dave Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk http://www.pctipp.ch/downloads/dl/35905.asp |
Thread Tools | |
Display Modes | |
|
|