J
JMMach
He is a strange problem I have never seen before; I guess there is a first
time fore everything.
We have one workstation, which is misbehaving in the area of mapping shares.
The User A has several shares mapped to drive letters, but one particular
share is mapped over and over again until all the drive letters are filled.
The drive letters are used up one at a time over the course of a day - they
are not all mapped at once.
User A disconnects the shares, and yet the next day, as the day progresses,
all available drive letters are filled with mappings to the SAME share. And
this is a share that was first mapped by User B within another profile; it
was never mapped by User A. Both Users are experiencing the same problem.
Any ideas on the source of the problem, and how to fix it? Is there a file
that stores what shares are to be mapped that I could edit, or is this
information stored in the registry?
time fore everything.
We have one workstation, which is misbehaving in the area of mapping shares.
The User A has several shares mapped to drive letters, but one particular
share is mapped over and over again until all the drive letters are filled.
The drive letters are used up one at a time over the course of a day - they
are not all mapped at once.
User A disconnects the shares, and yet the next day, as the day progresses,
all available drive letters are filled with mappings to the SAME share. And
this is a share that was first mapped by User B within another profile; it
was never mapped by User A. Both Users are experiencing the same problem.
Any ideas on the source of the problem, and how to fix it? Is there a file
that stores what shares are to be mapped that I could edit, or is this
information stored in the registry?