RE: Drive Mapping Reverting to old mappings
From: Don Eilenberger (Eilenberger_at_discussions.microsoft.com)
Date: 08/12/04
- Next message: Dennis Davis [msft]: "Re: Errors in Network Places"
- Previous message: Bookman: "RE: Filemaker database slow to launch under XP"
- In reply to: Dave Hoppel: "Drive Mapping Reverting to old mappings"
- Next in thread: Dave: "RE: Drive Mapping Reverting to old mappings"
- Reply: Dave: "RE: Drive Mapping Reverting to old mappings"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 12 Aug 2004 12:21:04 -0700
Dave - unfortunately - it's not as simple as that :(
The computer didn't suddenly end up with a login script (plus I looked for
one.. no dice).
And it gets odder:
1. IF I login as administrator - I can add a mapped drive to Drive G (which
is what I want to do) - or any other available drive letter.
I can reboot, restart. logout, login - and the mapping stays intect.
2. IF I login as the user - I can add a mapped drive to any drive letter
EXCEPT G. If I map a drive do drive letter E - all is well. Can
restart/reboot/logout-login - and the mapping stays intact.
BUT - if I'm logged in as the user - and map the same network share point to
Drive G - it's transient - it only stays mapped as long as the user is logged
in. If I have the user logout, restart, reboot - it looses this drive mapping
- but ONLY on the letter G.
I've go through the registry - and found all the references to the old share
point on the old server - and updated them to the new share point, or removed
them. Didn't help.
I set the user to Administrator level and tried mapping the share point to
Drive G - it still didn't work. Was still transient.
I'm pulling hair on this one. My choices are:
1. Use a different drive letter for this share point ONLY on this machine,
and set all the applications to use this drive letter.
2. FDISK and reinstall.
I've done #1 - it's not a nice solution. I will probably do #2 next week
when the user it out.
I remain baffled..
Thanks!
"Dave Hoppel" wrote:
> Check to see if there is a login script that is mapping
> the drive. If there isn't try creating a login script
> that deletes all previous mappings (net use * /delete /y)
> then map what you need.
>
- Next message: Dennis Davis [msft]: "Re: Errors in Network Places"
- Previous message: Bookman: "RE: Filemaker database slow to launch under XP"
- In reply to: Dave Hoppel: "Drive Mapping Reverting to old mappings"
- Next in thread: Dave: "RE: Drive Mapping Reverting to old mappings"
- Reply: Dave: "RE: Drive Mapping Reverting to old mappings"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|