Question Locked

Remote Desktop local drives problem

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a brand new fully updated windows server 2003 R2
and my customers use remote desktop to connect.

At one location only, 3 out of 4 of the users cannot
connect with both local drives and local printers available.
The fourth station works as expected.

If they turn on the local drives option only, the drives map fine.

As soon as they turn on the local printer option as well,
the local drives no longer map.

All users are identically defined in windows server.

Every policy that I can find for printers and drives is opened.

They all appear to be running fully updated versions of
Windows XP Pro with SP3 and the latest version of Remote
Desktop. They are all running McAffee anti-virus.

Is this an RDP problem? A printer problem?
Where can I look for errors?

Are there any tools that can help?

They tell me that their IT people have been all over this problem
and can't find anything wrong.
I'm worried about continuing to tell them that they are the only
location having this problem.

Help! Please!

2 replies

by kmh

This problem has morphed into a totally different question.
I got a suggestion from another source that one of the print drivers might be causing a problem.
That idea at least set me off in the right direction.
There were no errors in the EventLog.
I had installed print drivers for all of my customers printers.

At first I thought one of those drivers was not certified and that one of
them was causing a problem.

As I began to remove the drivers one by one to find out which one might be
causing a problem another symptom became evident.
The list of mapped printers was changing also, sometimes even without adding
or removing a printer driver.
And occasionally but not very often I would actually get the drives to map
also.
The shorter the list of printer drivers that I left installed, the more
correct was the list of printers.
And the the more likely that the drives were showing as mapped.
So I have put all of the print drivers back in and postponed the process in
my application that looks for drives and printers.

Now I can always see all of the drives and all of the printers.
So I am assuming that this is a timing issue and that my application just
wasn't waiting long enough before.
There are no scripts that I know of being run when a user logs in.

To get the drive letters, my application code is sifting through the
standard output produced by invoking net.exe.
And to get the printers, it is looping through
System.Drawing.Printing.PrinterSettings.InstalledPrinters.

Is there some event I can wait for before doing these two procedures?
Or is there something basically wrong with using these sources to obtain
drive and printer lists?

Again, thank you for your help.

This discussion is closed to new replies.