Reverse Drive Mapping?

G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

Hi, is it possible to map the servers drive to the client through
Remote Desktop? The scenario is a NATed work machine (the client),
attaching to a public IP facing Windows 2003 Server. Now, remote
desktop outbound from the client to the server works fine, but all
other Netbios style traffic is blocked. In a nutshell, the client can
connect and share it’s resources with the terminal server, but
conenctions on other ports cannot be established. Is it somehow
possible to map a server drive back so the client can access it - in
the Remote Desktop session? So Server can see clients C:\ drive, and
the client can see servers C:\ drive ?

Thanks

Yum.

--
http://www.WindowsForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.WindowsForumz.com/Client-Reverse-Drive-Mapping-ftopict200875.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.WindowsForumz.com/eform.php?p=591527
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

RDP Clients can only access the terminal server's hard drive from within a
session, i.e. when you logon to a session and go to "My Computer", the C
Drive you see is that of the server's not the client (unless you remap drives
with Citrix' Drive Re-Map tool before installing any apps)

It is not possible to map a drive from the client's explorer shell to the
terminal server via RDP. You'd need a VPN or direct RPC connection for this.

That being said, I'm not sure what your actual problem is, as with 2003
Terminal Server you can copy & paste files between the client and server via
the RDP Protocol. This is done via "Copy a file on the server, browse my
computer to the C Drive on the client computer, go the destination directory,
paste, or minimize your session and paste in the client's explorer shell".
This works in the opposite direction, except that you can't access the
server's hard drive via the client's explorer shell. This does not stop you
from copy/paste files between the two computers in both directions.

This is NOT possible in 2000 w/o using the legacy Terminal Server Client +
rdpclip resource kit utility or Remote Desktop Client + TSDropCopy or 3rd
party utility.

http://www.workthin.com/tshta.htm#RemoteDesktopClientConfiguration

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com

"plates" wrote:

> Hi, is it possible to map the servers drive to the client through
> Remote Desktop? The scenario is a NATed work machine (the client),
> attaching to a public IP facing Windows 2003 Server. Now, remote
> desktop outbound from the client to the server works fine, but all
> other Netbios style traffic is blocked. In a nutshell, the client can
> connect and share it’s resources with the terminal server, but
> conenctions on other ports cannot be established. Is it somehow
> possible to map a server drive back so the client can access it - in
> the Remote Desktop session? So Server can see clients C:\ drive, and
> the client can see servers C:\ drive ?
>
> Thanks
>
> Yum.
>
> --
> http://www.WindowsForumz.com/ This article was posted by author's request
> Articles individually checked for conformance to usenet standards
> Topic URL: http://www.WindowsForumz.com/Client-Reverse-Drive-Mapping-ftopict200875.html
> Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.WindowsForumz.com/eform.php?p=591527
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

"Patrick Rouse MVP" wrote:
> RDP Clients can only access the terminal server's hard drive
> from within a
> session, i.e. when you logon to a session and go to "My
> Computer", the C
> Drive you see is that of the server's not the client (unless
> you remap drives
> with Citrix' Drive Re-Map tool before installing any apps)
>
> It is not possible to map a drive from the client's explorer
> shell to the
> terminal server via RDP. You'd need a VPN or direct RPC
> connection for this.
>
> That being said, I'm not sure what your actual problem is, as
> with 2003
> Terminal Server you can copy & paste files between the client
> and server via
> the RDP Protocol. This is done via "Copy a file on the
> server, browse my
> computer to the C Drive on the client computer, go the
> destination directory,
> paste, or minimize your session and paste in the client's
> explorer shell".
> This works in the opposite direction, except that you can't
> access the
> server's hard drive via the client's explorer shell. This
> does not stop you
> from copy/paste files between the two computers in both
> directions.
>
> This is NOT possible in 2000 w/o using the legacy Terminal
> Server Client +
> rdpclip resource kit utility or Remote Desktop Client +
> TSDropCopy or 3rd
> party utility.
>
> http://www.workthin.com/tshta.htm#RemoteDesktopClientConfiguration
>
> Patrick Rouse
> Microsoft MVP - Terminal Server
> http://www.workthin.com
>
> "plates" wrote:
>
> > Hi, is it possible to map the servers drive to the client
> through
> > Remote Desktop? The scenario is a NATed work machine (the
> client),
> > attaching to a public IP facing Windows 2003 Server. Now,
> remote
> > desktop outbound from the client to the server works fine,
> but all
> > other Netbios style traffic is blocked. In a nutshell, the
> client can
> > connect and share it’s resources with the terminal server,
> but
> > conenctions on other ports cannot be established. Is it
> somehow
> > possible to map a server drive back so the client can access
> it - in
> > the Remote Desktop session? So Server can see clients C:
> drive, and
> > the client can see servers C: drive ?
> >
> > Thanks
> >
> > Yum.
> >
> > --
> > http://www.WindowsForumz.com/ This article was posted by author's request
> > Articles individually checked for conformance to usenet
> standards
> > Topic URL: http://www.WindowsForumz.com/Client-Reverse-Drive-Mapping-ftopict200875.html
> > Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.WindowsForumz.com/eform.php?p=591527
> >

Basically, we have a DVD Drive on the Win 2003 Server. Now, the client
is on the other end of a (very slow) link. The firewall prevents the
client initiating a standard windows file sharing session, to map the
drive. Now, on the DVD is a large application composed of many
components. Given the fact the installation is in compacted CAB
format, it would be significantly easier if the CLIENT could see the
SERVERS DVD drive through the RDP connection. Copy and paste is no
good as it would involve copying the entire DVD (Which would day
several days). However, if the drive on the SERVER could be mapped to
the client over the RDC, then the client could map, and install the
application, getting only those pertinent components and preventing
pointless wasteage by copying the entire DVD. Thats my problem

--
http://www.WindowsForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.WindowsForumz.com/Client-Reverse-Drive-Mapping-ftopict200875.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.WindowsForumz.com/eform.php?p=596454
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

Is there a reason why you don't install the program on the Terminal Server
and have the user execute the program inside of a RDP session, instead of
installing it on their home computer?

If user's are on a dial-up speed connection, any installation over a couple
of hundred kilobytes will be like watching grass grow, and the install may
transfer the entire cab files to the user's PC, which would make it even
slower.

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com


"plates" wrote:

> "Patrick Rouse MVP" wrote:
> > RDP Clients can only access the terminal server's hard drive
> > from within a
> > session, i.e. when you logon to a session and go to "My
> > Computer", the C
> > Drive you see is that of the server's not the client (unless
> > you remap drives
> > with Citrix' Drive Re-Map tool before installing any apps)
> >
> > It is not possible to map a drive from the client's explorer
> > shell to the
> > terminal server via RDP. You'd need a VPN or direct RPC
> > connection for this.
> >
> > That being said, I'm not sure what your actual problem is, as
> > with 2003
> > Terminal Server you can copy & paste files between the client
> > and server via
> > the RDP Protocol. This is done via "Copy a file on the
> > server, browse my
> > computer to the C Drive on the client computer, go the
> > destination directory,
> > paste, or minimize your session and paste in the client's
> > explorer shell".
> > This works in the opposite direction, except that you can't
> > access the
> > server's hard drive via the client's explorer shell. This
> > does not stop you
> > from copy/paste files between the two computers in both
> > directions.
> >
> > This is NOT possible in 2000 w/o using the legacy Terminal
> > Server Client +
> > rdpclip resource kit utility or Remote Desktop Client +
> > TSDropCopy or 3rd
> > party utility.
> >
> > http://www.workthin.com/tshta.htm#RemoteDesktopClientConfiguration
> >
> > Patrick Rouse
> > Microsoft MVP - Terminal Server
> > http://www.workthin.com
> >
> > "plates" wrote:
> >
> > > Hi, is it possible to map the servers drive to the client
> > through
> > > Remote Desktop? The scenario is a NATed work machine (the
> > client),
> > > attaching to a public IP facing Windows 2003 Server. Now,
> > remote
> > > desktop outbound from the client to the server works fine,
> > but all
> > > other Netbios style traffic is blocked. In a nutshell, the
> > client can
> > > connect and share it’s resources with the terminal server,
> > but
> > > conenctions on other ports cannot be established. Is it
> > somehow
> > > possible to map a server drive back so the client can access
> > it - in
> > > the Remote Desktop session? So Server can see clients C:
> > drive, and
> > > the client can see servers C: drive ?
> > >
> > > Thanks
> > >
> > > Yum.
> > >
> > > --
> > > http://www.WindowsForumz.com/ This article was posted by author's request
> > > Articles individually checked for conformance to usenet
> > standards
> > > Topic URL: http://www.WindowsForumz.com/Client-Reverse-Drive-Mapping-ftopict200875.html
> > > Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.WindowsForumz.com/eform.php?p=591527
> > >
>
> Basically, we have a DVD Drive on the Win 2003 Server. Now, the client
> is on the other end of a (very slow) link. The firewall prevents the
> client initiating a standard windows file sharing session, to map the
> drive. Now, on the DVD is a large application composed of many
> components. Given the fact the installation is in compacted CAB
> format, it would be significantly easier if the CLIENT could see the
> SERVERS DVD drive through the RDP connection. Copy and paste is no
> good as it would involve copying the entire DVD (Which would day
> several days). However, if the drive on the SERVER could be mapped to
> the client over the RDC, then the client could map, and install the
> application, getting only those pertinent components and preventing
> pointless wasteage by copying the entire DVD. Thats my problem
>
> --
> http://www.WindowsForumz.com/ This article was posted by author's request
> Articles individually checked for conformance to usenet standards
> Topic URL: http://www.WindowsForumz.com/Client-Reverse-Drive-Mapping-ftopict200875.html
> Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.WindowsForumz.com/eform.php?p=596454
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

"Patrick Rouse MVP" wrote:
> Is there a reason why you don't install the program on the
> Terminal Server
> and have the user execute the program inside of a RDP session,
> instead of
> installing it on their home computer?
>
> If user's are on a dial-up speed connection, any installation
> over a couple
> of hundred kilobytes will be like watching grass grow, and the
> install may
> transfer the entire cab files to the user's PC, which would
> make it even
> slower.
>
> Patrick Rouse
> Microsoft MVP - Terminal Server
> http://www.workthin.com
>
>
> "plates" wrote:
>
> > "Patrick Rouse MVP" wrote:
>  > > RDP Clients can only access the terminal server's
> hard drive
>  > > from within a
>  > > session, i.e. when you logon to a session and go to
> "My
>  > > Computer", the C
>  > > Drive you see is that of the server's not the
> client (unless
>  > > you remap drives
>  > > with Citrix' Drive Re-Map tool before installing
> any apps)
>  > >
>  > > It is not possible to map a drive from the client's
> explorer
>  > > shell to the
>  > > terminal server via RDP. You'd need a VPN or
> direct RPC
>  > > connection for this.
>  > >
>  > > That being said, I'm not sure what your actual
> problem is, as
>  > > with 2003
>  > > Terminal Server you can copy & paste files between
> the client
>  > > and server via
>  > > the RDP Protocol. This is done via "Copy a file on
> the
>  > > server, browse my
>  > > computer to the C Drive on the client computer, go
> the
>  > > destination directory,
>  > > paste, or minimize your session and paste in the
> client's
>  > > explorer shell".
>  > > This works in the opposite direction, except that
> you can't
>  > > access the
>  > > server's hard drive via the client's explorer
> shell. This
>  > > does not stop you
>  > > from copy/paste files between the two computers in
> both
>  > > directions.
>  > >
>  > > This is NOT possible in 2000 w/o using the legacy
> Terminal
>  > > Server Client +
>  > > rdpclip resource kit utility or Remote Desktop
> Client +
>  > > TSDropCopy or 3rd
>  > > party utility.
>  > >
>  > >
> http://www.workthin.com/tshta.htm#RemoteDesktopClientConfiguration
>  > >
>  > > Patrick Rouse
>  > > Microsoft MVP - Terminal Server
>  > > http://www.workthin.com
>  > >
>  > > "plates" wrote:
>  > >
>   > > > Hi, is it possible to map the servers drive
> to the client
>  > > through
>   > > > Remote Desktop? The scenario is a NATed
> work machine (the
>  > > client),
>   > > > attaching to a public IP facing Windows
> 2003 Server. Now,
>  > > remote
>   > > > desktop outbound from the client to the
> server works fine,
>  > > but all
>   > > > other Netbios style traffic is blocked. In
> a nutshell, the
>  > > client can
>   > > > connect and share it’s resources
> with the terminal server,
>  > > but
>   > > > conenctions on other ports cannot be
> established. Is it
>  > > somehow
>   > > > possible to map a server drive back so the
> client can access
>  > > it - in
>   > > > the Remote Desktop session? So Server can
> see clients C:
>  > > drive, and
>   > > > the client can see servers C: drive ?
>   > > >
>   > > > Thanks
>   > > >
>   > > > Yum.
>   > > >
>   > > > --
>   > > > http://www.WindowsForumz.com/ This article
> was posted by author's request
>   > > > Articles individually checked for
> conformance to usenet
>  > > standards
>   > > > Topic URL:
> http://www.WindowsForumz.com/Client-Reverse-Drive-Mapping-ftopict200875.html
>   > > > Visit Topic URL to contact author (reg.
> req'd). Report abuse:
> http://www.WindowsForumz.com/eform.php?p=591527
>   > > >
> >
> > Basically, we have a DVD Drive on the Win 2003 Server. Now,
> the client
> > is on the other end of a (very slow) link. The firewall
> prevents the
> > client initiating a standard windows file sharing session,
> to map the
> > drive. Now, on the DVD is a large application composed of
> many
> > components. Given the fact the installation is in compacted
> CAB
> > format, it would be significantly easier if the CLIENT could
> see the
> > SERVERS DVD drive through the RDP connection. Copy and paste
> is no
> > good as it would involve copying the entire DVD (Which would
> day
> > several days). However, if the drive on the SERVER could be
> mapped to
> > the client over the RDC, then the client could map, and
> install the
> > application, getting only those pertinent components and
> preventing
> > pointless wasteage by copying the entire DVD. Thats my
> problem
> >
> > --
> > http://www.WindowsForumz.com/ This article was posted by author's request
> > Articles individually checked for conformance to usenet
> standards
> > Topic URL: http://www.WindowsForumz.com/Client-Reverse-Drive-Mapping-ftopict200875.html
> > Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.WindowsForumz.com/eform.php?p=596454
> >

Thanks for your reply - I appericate the suggestions, but they don’t
answer my original question - is it possible to reverse map server
drives to the client over RDP - for whatever reason?

--
http://www.WindowsForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.WindowsForumz.com/Client-Reverse-Drive-Mapping-ftopict200875.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.WindowsForumz.com/eform.php?p=598648
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)

Per my first reply, this is not possible.

Quote
"It is not possible to map a drive from the client's explorer shell to the
terminal server via RDP. "

"plates" wrote:

> "Patrick Rouse MVP" wrote:
> > Is there a reason why you don't install the program on the
> > Terminal Server
> > and have the user execute the program inside of a RDP session,
> > instead of
> > installing it on their home computer?
> >
> > If user's are on a dial-up speed connection, any installation
> > over a couple
> > of hundred kilobytes will be like watching grass grow, and the
> > install may
> > transfer the entire cab files to the user's PC, which would
> > make it even
> > slower.
> >
> > Patrick Rouse
> > Microsoft MVP - Terminal Server
> > http://www.workthin.com
> >
> >
> > "plates" wrote:
> >
> > > "Patrick Rouse MVP" wrote:
> > > > RDP Clients can only access the terminal server's
> > hard drive
> > > > from within a
> > > > session, i.e. when you logon to a session and go to
> > "My
> > > > Computer", the C
> > > > Drive you see is that of the server's not the
> > client (unless
> > > > you remap drives
> > > > with Citrix' Drive Re-Map tool before installing
> > any apps)
> > > >
> > > > It is not possible to map a drive from the client's
> > explorer
> > > > shell to the
> > > > terminal server via RDP. You'd need a VPN or
> > direct RPC
> > > > connection for this.
> > > >
> > > > That being said, I'm not sure what your actual
> > problem is, as
> > > > with 2003
> > > > Terminal Server you can copy & paste files between
> > the client
> > > > and server via
> > > > the RDP Protocol. This is done via "Copy a file on
> > the
> > > > server, browse my
> > > > computer to the C Drive on the client computer, go
> > the
> > > > destination directory,
> > > > paste, or minimize your session and paste in the
> > client's
> > > > explorer shell".
> > > > This works in the opposite direction, except that
> > you can't
> > > > access the
> > > > server's hard drive via the client's explorer
> > shell. This
> > > > does not stop you
> > > > from copy/paste files between the two computers in
> > both
> > > > directions.
> > > >
> > > > This is NOT possible in 2000 w/o using the legacy
> > Terminal
> > > > Server Client +
> > > > rdpclip resource kit utility or Remote Desktop
> > Client +
> > > > TSDropCopy or 3rd
> > > > party utility.
> > > >
> > > >
> > http://www.workthin.com/tshta.htm#RemoteDesktopClientConfiguration
> > > >
> > > > Patrick Rouse
> > > > Microsoft MVP - Terminal Server
> > > > http://www.workthin.com
> > > >
> > > > "plates" wrote:
> > > >
> > > > > Hi, is it possible to map the servers drive
> > to the client
> > > > through
> > > > > Remote Desktop? The scenario is a NATed
> > work machine (the
> > > > client),
> > > > > attaching to a public IP facing Windows
> > 2003 Server. Now,
> > > > remote
> > > > > desktop outbound from the client to the
> > server works fine,
> > > > but all
> > > > > other Netbios style traffic is blocked. In
> > a nutshell, the
> > > > client can
> > > > > connect and share it’s resources
> > with the terminal server,
> > > > but
> > > > > conenctions on other ports cannot be
> > established. Is it
> > > > somehow
> > > > > possible to map a server drive back so the
> > client can access
> > > > it - in
> > > > > the Remote Desktop session? So Server can
> > see clients C:
> > > > drive, and
> > > > > the client can see servers C: drive ?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Yum.
> > > > >
> > > > > --
> > > > > http://www.WindowsForumz.com/ This article
> > was posted by author's request
> > > > > Articles individually checked for
> > conformance to usenet
> > > > standards
> > > > > Topic URL:
> > http://www.WindowsForumz.com/Client-Reverse-Drive-Mapping-ftopict200875.html
> > > > > Visit Topic URL to contact author (reg.
> > req'd). Report abuse:
> > http://www.WindowsForumz.com/eform.php?p=591527
> > > > >
> > >
> > > Basically, we have a DVD Drive on the Win 2003 Server. Now,
> > the client
> > > is on the other end of a (very slow) link. The firewall
> > prevents the
> > > client initiating a standard windows file sharing session,
> > to map the
> > > drive. Now, on the DVD is a large application composed of
> > many
> > > components. Given the fact the installation is in compacted
> > CAB
> > > format, it would be significantly easier if the CLIENT could
> > see the
> > > SERVERS DVD drive through the RDP connection. Copy and paste
> > is no
> > > good as it would involve copying the entire DVD (Which would
> > day
> > > several days). However, if the drive on the SERVER could be
> > mapped to
> > > the client over the RDC, then the client could map, and
> > install the
> > > application, getting only those pertinent components and
> > preventing
> > > pointless wasteage by copying the entire DVD. Thats my
> > problem
> > >
> > > --
> > > http://www.WindowsForumz.com/ This article was posted by author's request
> > > Articles individually checked for conformance to usenet
> > standards
> > > Topic URL: http://www.WindowsForumz.com/Client-Reverse-Drive-Mapping-ftopict200875.html
> > > Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.WindowsForumz.com/eform.php?p=596454
> > >
>
> Thanks for your reply - I appericate the suggestions, but they don’t
> answer my original question - is it possible to reverse map server
> drives to the client over RDP - for whatever reason?
>
> --
> http://www.WindowsForumz.com/ This article was posted by author's request
> Articles individually checked for conformance to usenet standards
> Topic URL: http://www.WindowsForumz.com/Client-Reverse-Drive-Mapping-ftopict200875.html
> Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.WindowsForumz.com/eform.php?p=598648
>