Cannot connect client drive on Win 2000 TS

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have never been able to get the client drive connected on my W2K TS. In
the past it was not a big problem, but I am seeing that future use will
require the need to connect to the client's local disk. I have user A setup
on the TS with the connect local drive box checked. I have a RDP connection
with local drive box checked. Yet I do not get my local drive. Is there
something known about this issue?
 
Yes. But it's not an issue, it's by design.
W2K TS does not support client drive redirection. You will need to
upgrade to 2003 for this.
In the meantime, you can use TSDropCopy from AnalogX for file
transfer between client and TS session.

http://www.analogx.com/contents/download/system/tsdc.htm

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
 
This works great, but may not do exactly what I need. I am not sure so I
will ask you.
I have users that connect to Quick Books. They generate a report then open
it in Excel. There does not appear to be a way to save it on their machine
from this point. They don't acually get a desktop, just the app. I am
missing something?
 
OK, I understand.
Do the users have a network-based home directory, on a file server?
If so, they should have access to their home drive also from within
a TS session. You can configure this either in their account
properties in AD, or in a logon script.

net use H: \\server\Users\%username% or something similar

Then users will be able to save their files to H: from within
QuickBooks.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
 
They are making a Remote Desktop Connection. They then have access to their
home directory on the server, but when they disconnect the file is sitting
there and they cannot access it.

I little background. For some time now we have been using TS at a couple of
satellite offices to enter sales/shipping information into QB. There was no
one who needed to save anything, so no need to provide additional support.
A couple of additional satellite offices have come on-line this year that had
their own local QB and had setup a number of procedures, by which, they would
send info to customers straight from their PC. Since everything was on their
PC, there was not an issue. Now ... there is one. I really cannot see
upgrading to 2003 server as a solution in the next few months. I am,
therefore, left with the dilemma of "giving them what they want" without the
benefit of being able to upgrade.

I have appreciated your quick responses to my questions. I may have to go
the ftp route, although I am not exactly sure how to approach that.

Any additional help is beyond kindness and would be greatly appreciated!
 
One way or the other, you have to make sure that users have access
to the same home directory from their workstations and from within
their RDP sessions.

One way to do that (the preferred one) is to give them a centrally
stored home directory on a file server, which they use to store all
their files in. They should have a connection to this home
directory when they logon to their workstation, as well as when
they start QB in a Remote Desktop session.

If you don't have a central file server, the second best option is
to share the local workstation drive, or at least their home folder
on the local drive, and map a connection to it from within their
RDP session.

on the client: net share C:\MyHome
within the session: net use H: \\MyPC\MyHome

The above is just an example to clarify, you can use the variable
%CLIENTNAME% to avoid having to hardcode the name of the
workstation.
Something like: net use H: \\%CLIENTNAME%\%USERNAME%

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
 
I will try the last option. It will probably bet the best one. In this, I
can then disconnect the drive on exit. Thanks!
 
It was a while before I could check out your suggestions. I cannot get a
connection from the RDP side. I get a system error 53. Network path not
found. I can see the client name in the RDP connection, but I cannot seem to
see the client when I try to ping/connect to it. Is there something that I
have missed?
 
Are you connecting over the Internet? Then "net use" will not work.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
 
No, this is an RDP connection to TS. Can you connect to a TS application
from the internet? This might have some interesting possibilities. That is
to say, if it does not require some additional software other then IIS.
 
Sure you can connect to a Terminal Server over the Internet. Either
with the normal rdp client, or with the wec client = Internet
Explorer + an ActiveX component on the client, IIS on the server.

But if you current client is on the same LAN as the Terminal
Server, you should be able to see ir from within your TS session.
Maybe the client has a firewall running?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
 
The client is not on the same LAN as the server. You may have a point on the
firewall, but I don't know where I should be looking. Since the RDP
connection is successful (the client is running Quick Books remotely), and
since the client's printers are functioning properly, and since the client
does have shared folders in use on its LAN, I am at a loss as to what I need
to do to open the firewall on the client to allow access to a shared drive
from the server. Is there a possible user name and password issue here?

I know how to create a WScript mapped drive, which involves a user name and
password, but this is different.
 
Back
Top