Terminal Server client drive sharing not working

Hi All
I am having an issue with being able to share my client drives through a Terminal Server session. The setup is a s follows:
Domain Client Computer running the TS Client  MSTSC is Connecting to a Standalone Server all 2000 os.
I have the 2000 resource kit and have installed as per ms and this instruction from JSI http://www.jsiinc.com/SUBL/tip5900/rh5986.htm

Issue is all documents I am reading say you should be able to use a net use cmd to map the drives as usual and that the above JSI says the Drmap files should do this for you. Problem is none of it is working. Has anyone made this work if so what could I be missing?

I am a Citrix guy and all this happens without a hitch using ISA so I know I am just missing something.

Thanks
LVL 7
msiceAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

KaliKoderCommented:
Hello Msice,

- Are you using the latest TS Client ? I know you are talking about MSTSC, but have you tried using a Remote Desktop Client available at: http://www.microsoft.com/windowsxp/downloads/tools/rdclientdl.mspx ? Please download this and give this a try, when you do, click on the "Options" button, and it has a built in option which you can check or uncheck, saying "bring the computers drives to me"
- Second question, are you using the TS in remote administration or Application server mode ?

Please give the above a try and post back.

Thanks and Good Luck!
0
KaliKoderCommented:
Another thing, if you are using the Terminal Server in Application mode, in Active Directory, have you got the users Terminal Services Profile path configured ?
0
msiceAuthor Commented:
Yes using the latest client and have checked the disk drives box but no go. I am connecting to a stand-alone server no ad and in Remote Desktop mode - not worried about profiles.
Any more thoughts?
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

msiceAuthor Commented:
TS in remote administration mode that is...
0
KaliKoderCommented:
What happens when you open up a command prompt while conencted into the terminal services session and do this within the session:
Net use T: /delete
Net Use T: \\%computername%\C$ /Persistent:yes

It should map your drive ? If not, can you tell us what error message do you get ?

Where %computername% is your own computername, if %computername% does not work, replace it with your actual computername
0
msiceAuthor Commented:
Yes I have tried that already it cant find the computer on the network. The local computer is not there at all - no ping - no net view/use ext? I am puzzled.
0
KaliKoderCommented:
Is there a firewall on the client computer (laptop ?) Is port 139 traffic being allowed bidirectional ? What happens when you try and remote desktop from another machine to the server ? same result ?
0
msiceAuthor Commented:
Oh wait %computername% would be the Termial Server computername on the client that is already there. I might be off here are you saying to do this in the termial session or on the client computer? I am trying eveeything in the termial session.
Net Use T: \\%computername%\C$ /Persistent:yes
just maps the temial computers c drive to another share. T: \\clientcomputername\C$ /Persistent:yes gives error
0
msiceAuthor Commented:
Port 139 traffic is not being allowed bidirectional only port open is 3389 - over the internet this conection is. Should not matter though from what I am reading all goes over 3389.
0
KaliKoderCommented:
ah! Sorry for not being clear...

What I meant was, lets say you were on a computer called "mycomputer" on your domain, and wanted to connect to the Terminal server using the remote desktop. Now, launch the remote desktop client, connect to your terminal server, and "from within the terminal server session, open a command prompt" and type :
net use T:\\mycomputername\c$
see if it maps a drive back to your computer.!
0
KaliKoderCommented:
Everything goes over 3389 yes RDP, however, 139 allows file and print sharing, if its blocked you cant map drives etc.
0
msiceAuthor Commented:
No it does not this is what I have been trying to make work and I get an error:

System error 53 has occurred.

The network path was not found.
0
msiceAuthor Commented:
Geeezz it works using citrix and ICA no problem. I wonder why ms does not say anything about 139 in the TS drive mapping install doc.
0
msiceAuthor Commented:
Is there a way to secure this over the internet? Opening 139 seems like a nightmare waiting to happen.
0
KaliKoderCommented:
Try using the IP address instead of the computername of your computer. So do
net use T: \\192.168.0.102\c$
0
KaliKoderCommented:
Also, on your computer you are at. Can you double check if C drive is actually shared as a hidden shared with name C$ ?
0
msiceAuthor Commented:
Yes it is hidden - default admin share. Does not work with ip cant ping it either.
0
msiceAuthor Commented:
MS makes it sould like the client computer will be avalible as if it were on the same workgroup as the TS server. So Net View should show it.
0
KaliKoderCommented:
IS your Terminal Server machine and the Client computer on the same subnet ? Can you ping and map to the C$ share of the client computer from another machine ?
0
msiceAuthor Commented:
Nope it is over the internet!
0
msiceAuthor Commented:
Can you ping and map to the C$ share of the client computer from another machine ?
ANS yes the client computer is the member of a domain - behind a firewall.

The Terminal server is over the internet behind another firewall with port 3389 open.
0
KaliKoderCommented:
Ok, definitely could be a firewall issue.! You have a firewall running ? Can you test just by allowing port 139 ? I know you are worried about security, but once we resolve this, there are other methods like VPN that you can use that would make 130 secure. Also, if I am reading you correctly, you are saying, You are your home connected to the internet, and from there are trying to connect to your terminal server at work ? right ?
0
msiceAuthor Commented:
What I will do is install the Drmap files on a client in the same network as the ts server and see if that works. And get back to you.
0
msiceAuthor Commented:
Ok here’s the deal of course it will work on the local domain as all other computers do. The benefit of the TS drive mapping is that it is supposed to work over the RDP connection. If you find any MS info to the contrary if you have to have 139 open for it to work then I will give you the points - a simple hyper link to a doc will be fine. PS ( I am starting to think you are correct)

Why would there be such a big deal about mapping a simple local network drive though. As I said I use Citrix and it runs on Terminal Server – it maps local client drives thorough the terminal server using only the Citrix 1494 port I use it all the time over the Internet. Why wouldn’t MS’s own software be able to do the same thing!
0
KaliKoderCommented:
ok,

Can you please make sure that UDP 3389 is allowed birectional on both firewalls ? Did you enable RDP or UDP ? or both ?

0
KaliKoderCommented:
Also, please check if there is a group policy preventing drive redirection. Read this for more info:
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/pree_rem_uvnl.asp

Above article is about WinxP but same might apply for Win 2000. I dont have a W2K desktop in front of me sorry
0
KaliKoderCommented:
I have not been abled to find the exact article that says you should allow ports that I suggested, but I have found articles that tell you to use VPN in conjuction to get to the TS for drive redirection to work.

Article that says a VPN connection must be initiated (essentially meaning you becoming the part of the local subnet, allowing NetBios name resolution PORT 135 (TCP or UDP) for Remote Procedure Call(RPC)Service
PORT 137 (UDP) for NetBIOS Name Service
PORT 138 (UDP) for NetBIOS datagram (Browsing)
PORT 139 (TCP) for NetBIOS session (NET USE) )
http://support.microsoft.com/kb/272519/EN-US/

This articles tell you too that even with DriveShare utility drive mappings over the internet wont work, unless you VPN through, you need NetBios name resoltion etc
http://www.thinstructor.com/modules.php?op=modload&name=News&file=article&sid=333&mode=thread&order=0&thold=0

I would keep looking for a bit, but it should not hurt you to try opening the ports for a short time and testing..
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
msiceAuthor Commented:
Disappointing but thank you for your help and suggestions you earned the points.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.