persistent connection

[Guest]

I have a mapped network drive that I cannot eliminate. I can disconnect it
after my system boots, (and I get a message that files are still open, which
they are not), but when I reboot, the drive is automatically remapped. I've
tried changing the registry entry on persistent connections both manually and
by using the net use command. I've tried remapping this drive to another
folder, but it always returns to the original folder. Any ideas on how to
permanently disable this mapping?

 

[Guest]

--
ab

Issue these commands from a Command Prompt, then
reboot the machine:

net use * /del /yes
net use /persistent:no
net use * /del /yes

You should also check your machine for scheduled tasks and
startup tasks. One of them might remap a share to a drive
letter at startup time.


I tried the commands. The drive does not disconnect using the net use * /del /yes command. I can disconnect it manually by right clicking on it and discconnecting that way. However from the command line, it says it is an active connection and "continuing will cancel the connection", but it doesn't. I checked the scheduled tasks and I have none. I don't know where to look for startup tasks. I checked the startup in msconfig and tweak UI and don't see a reference to network drives. Is there somewhere else I can look? BTW, this is unique to my profile; if I log on to the network using administrator credentials, the drive is not connected. I therefore think the problem is buired somewhere in the startup login sequence, but I don't know how to access this. Can you help?

 

[Pegasus \(MVP\)]

/del /yes command. I can disconnect it manually by right clicking on it and
discconnecting that way. However from the command line, it says it is an
active connection and "continuing will cancel the connection", but it
doesn't. I checked the scheduled tasks and I have none. I don't know where
to look for startup tasks. I checked the startup in msconfig and tweak UI
and don't see a reference to network drives. Is there somewhere else I can
look? BTW, this is unique to my profile; if I log on to the network using
administrator credentials, the drive is not connected. I therefore think
the problem is buired somewhere in the startup login sequence, but I don't
know how to access this. Can you help?
===============

Let's have a look at your setup. Start a Command Prompt
(Start / Run / cmd {OK}, then type this command:

net use > c:\test.txt

Now paste the contents of c:\test.txt into your reply.

 

[Guest]

Tried it, but it just returns the command prompt. i.e., U: I typed in the
command exactly as you wrote it: net use > c:\test.txt (including the space
carat space).

 

[Pegasus \(MVP\)]

You have to ***open*** c:\test.txt before you can copy & paste!
Here are the instructions more explicitely:

Click Start / Run / cmd {OK}, then type these commands:
net use > c:\test.txt
notepad c:\test.txt
copy & paste the text into your reply

 

[Guest]

OK, here is the text;

New connections will not be remembered.


Status Local Remote Network

-------------------------------------------------------------------------------
OK U: \\usistf-server\users\abrenner
Microsoft Windows Network
The command completed successfully.


It's the U: drive that remains persistent no matter if I change it in the
registry or by using the net use command. This drive is on our server in our
small office. Interestingly, when I bring up the command box, it defaults
also to U:

 

[Pegasus \(MVP\)]

That output looks fine but it does not solve your problem.

For the purpose of testing I would temporarily delete the
share \\usistf-server\users\abrenner, then see what happens
at logon time. It will take only a minute to recreate it. If the
share connection is still visible at that stage then you can
easily delete it, because there can be no open files on it now!

I am puzzled by your last remark, i.e. starting the Command
Prompt on drive U:. I suggest you explore this in more detail,
by doing this:
- Click Start / Run / cmd {OK}
- Type these commands:
set > c:\test.txt
notepad c:\test.txt
Copy & past the text into your reply.

 

[Guest]

First, thank you for staying with me on this, i very much appreciate it.
Next, I tried googling to find out how to delete the share, but other than
writing a login script, I couldn't find how to do this. Perhaps you could
tell me how to do this. if it's necessary after you read the set function.
Third, here is the set function text:

ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\abrenner\Application Data
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=ARNIE
ComSpec=C:\WINDOWS\system32\cmd.exe
FP_NO_HOST_CHECK=NO
GETMODEL=Satellite M30X
HOMEDRIVE=U:
HOMEPATH=\
HOMESHARE=\\usistf-server\users\abrenner
LOGONSERVER=\\USISTF-SERVER
NUMBER_OF_PROCESSORS=1
OS=Windows_NT
Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
Files\ATI Technologies\ATI Control Panel
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 13 Stepping 6, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0d06
ProgramFiles=C:\Program Files
PROMPT=$P$G
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\DOCUME~1\abrenner\LOCALS~1\Temp
TMP=C:\DOCUME~1\abrenner\LOCALS~1\Temp
USERDNSDOMAIN=USISTF.LOCAL
USERDOMAIN=usistf
USERNAME=abrenner
USERPROFILE=C:\Documents and Settings\abrenner
VERNUM=PSA72U-20V0278
windir=C:\WINDOWS

No wonder the share keeps appearing; it is my home drive and home share -
but I don't know how it got to be that way! I don't even know what that
means.

 

[Pegasus \(MVP\)]

Your environmental settings look fine.

Deleting a share is usually a network administrator's task.
What's happened to yours? There are several ways to create
or delete one, eg. like so:
net share users /del (to delete it)
net share users=d:SomeFolder (to create it)

The commands must, of course, be executed on \\usistf-server.

 

[Guest]

Thanks agian for your help, I will let my network administrator handle this
from here on.

 

[Guest]

arnieb;
did you ever get this issue resolved? i have the same issue and would like
to know how you got it fixed. thanks.