The problem being encountered occurs in programming, but the base issue is strictly at the server level, so that's where I'm going to start searching ![Smile :) :)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
We've got a routine that requires users to log into Remote Desktop, and then copy a file from a local drive on their PC to a folder on the remote server.
Ideally I'd like to be able to programmatically pull the data over from the user's PC, or a shared network drive that is mapped on the user's PC (drive S: for instance). However, neither the drive nor the file is not visible to any commands.
Example: using a directory command in VBA or T-SQL results in the folder not being located, when using mapped drive letter or UNC.
However, I can browse the local drives (including mapped network drives) that are exposed after logging into Remote Desktop.
Complicating factor: For security, the server on which Remote Desktop resides and the network in general are separated & cannot communicate directly. Otherwise there's way more efficient methods we already would have implemented![Smile :) :)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Is there any way to avoid doing a Windows Explorer copy/paste to get this file out to the remote server?
Thanks in advance.
Bryant Farley
EG&G Technical Services
We've got a routine that requires users to log into Remote Desktop, and then copy a file from a local drive on their PC to a folder on the remote server.
Ideally I'd like to be able to programmatically pull the data over from the user's PC, or a shared network drive that is mapped on the user's PC (drive S: for instance). However, neither the drive nor the file is not visible to any commands.
Example: using a directory command in VBA or T-SQL results in the folder not being located, when using mapped drive letter or UNC.
However, I can browse the local drives (including mapped network drives) that are exposed after logging into Remote Desktop.
Complicating factor: For security, the server on which Remote Desktop resides and the network in general are separated & cannot communicate directly. Otherwise there's way more efficient methods we already would have implemented
Is there any way to avoid doing a Windows Explorer copy/paste to get this file out to the remote server?
Thanks in advance.
Bryant Farley
EG&G Technical Services