Local drive through Terminal Server oddity

I have 5 servers running Windows 2003 SP2 doing load balancing of
users' RDP sessions. This is the main application server running
about 400-500 concurrent RDP connections at a time. A very small
number of users are intermittently having a problem with their local
drives from the terminal session. For some reason, the local drives
that they see aren't even their local drives. In every instance, the
name on the local drive was a member of the IT department. I've seen
4 instances myself, and twice it was the same tech, a different tech,
and then it was the IT manager who's name appeared on the drive. When
the users try to access the drive, they get a not accessible error
message.

Any help is appreciated..



Matt

Matt <(E-Mail Removed)> wrote:
> I have 5 servers running Windows 2003 SP2 doing load balancing of
> users' RDP sessions. This is the main application server running
> about 400-500 concurrent RDP connections at a time. A very small
> number of users are intermittently having a problem with their local
> drives from the terminal session. For some reason, the local drives
> that they see aren't even their local drives. In every instance, the
> name on the local drive was a member of the IT department. I've seen
> 4 instances myself, and twice it was the same tech, a different tech,
> and then it was the IT manager who's name appeared on the drive. When
> the users try to access the drive, they get a not accessible error
> message.
>
> Any help is appreciated..

Hi - I suggest you post in microsoft.public.windows.terminal_services for
the most expert help with your question.