Re: Strange Drive Mapping
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Fri, 26 Jan 2007 04:14:25 -0600
<james_crawley1981@xxxxxxxxxxx> wrote in message
news:1169805584.882991.189400@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
No, I mean when I do the "net use F: /d" it won't delete it and gives
the message saying it can't connect to network.
It won't delete it if it isn't mapped but you didn't show me the text
output of those three commands.
I cannot every recall seeing "can't connect to network" for failure to
delete a mapping
You say it's mapping for the administrator but not the ordinary user
but they are both getting exactly the same.
I was basing that on misunderstanding what you wrote about logging
on as admin -- I misread it, sorry.
Maybe I'm not explaining
this properly. When a kid logs on F:\ should be mapped to
"\\server1\jsmith$" (this is done via active directory and logon
script, which has been working fine for years). Suddenly F:\ has
started coming up as "disconnected network drive", which cannot be
disconnected or remapped. When this is clicked on it links to
"\\server2\installfiles$". When an administrator logs on, nothing
should be mapped to F:\ but they still get F:\ doing exactly the same
as when a kid logs on. After a reboot, 9 out of 10 times the kid gets
their F:\ drive mapped correctly, the "10th" time, exactly the same
problem occurs. ie. F:\ shows as disconnected network drive and links
to the wrong place.
.
- References:
- Strange Drive Mapping
- From: james_crawley1981
- Re: Strange Drive Mapping
- From: james_crawley1981
- Re: Strange Drive Mapping
- From: Herb Martin
- Re: Strange Drive Mapping
- From: james_crawley1981
- Re: Strange Drive Mapping
- From: Herb Martin
- Re: Strange Drive Mapping
- From: james_crawley1981
- Strange Drive Mapping
- Prev by Date: AT command is not working on remote machine.
- Next by Date: Re: AT command is not working on remote machine.
- Previous by thread: Re: Strange Drive Mapping
- Next by thread: RDC Logon Problem
- Index(es):
Relevant Pages
|