mysterious f drive

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a network where all XP Pro clients have an F drive.
It is not a mapped drive.
I can right click and say disconnect, however the drive stays and I can
still access it via a double click on the drive.
I need to setup login scripts, but when the login script tries to map the f
drive, I get an error to the effect that the drive letter already exists.
I have scanned the registry, but can not find any hints on how this drive
letter is 'connected' to the server.
It is not coming from the server, because all the new machines we put in do
not have this strange F drive.
Any hints?

Frank
 
Frank Neuner said:
I have a network where all XP Pro clients have an F drive.
It is not a mapped drive.
I can right click and say disconnect, however the drive stays and I can
still access it via a double click on the drive.
I need to setup login scripts, but when the login script tries to map the f
drive, I get an error to the effect that the drive letter already exists.
I have scanned the registry, but can not find any hints on how this drive
letter is 'connected' to the server.
It is not coming from the server, because all the new machines we put in do
not have this strange F drive.
Any hints?

Frank
Click to expand...

A couple of questions:
- What's the contents of this mysterious drive?
- Is it the same as one of the existing drives?
- What's the contents of c:\drive.txt after you have
run through the following steps:
* Click Start / Run
* Type cmd {OK}
* Type mountvol > c:\drive.txt {Enter}
* Type net use >> c:\drive.txt {Enter}
* Type net use F: >> c:\drive.txt {Enter}
* Type subst >> c:\drive.txt {Enter}
* Type notepad c:\drive.txt {Enter}
 
The F drive on the workstations is the same as the F drive on the Windows
2000 server, which in turn is shared as the F drive on this server
No, all my local drives are different and so is the F drive

reates, deletes, or lists a volume mount point.

MOUNTVOL [drive:]path VolumeName
MOUNTVOL [drive:]path /D
MOUNTVOL [drive:]path /L

path Specifies the existing NTFS directory where the mount
point will reside.
VolumeName Specifies the volume name that is the target of the mount
point.
/D Removes the volume mount point from the specified directory.
/L Lists the mounted volume name for the specified directory.

Possible values for VolumeName along with current mount points are:

\\?\Volume{8bce4e70-b211-11d6-9b4b-806d6172696f}\
C:\

\\?\Volume{8bce4e71-b211-11d6-9b4b-806d6172696f}\
D:\

\\?\Volume{8bce4e72-b211-11d6-9b4b-806d6172696f}\
A:\

New connections will be remembered.


Status Local Remote Network

-------------------------------------------------------------------------------
OK F: \\mail\f Microsoft Windows Network
The command completed successfully.

Local name F:
Remote name \\mail\f
Resource type Disk
Status OK
# Opens 0
# Connections 1
The command completed successfully.

NOTE: the subst command produced no output

Regards

Frank
 
Your F: drive is an ordinary mapped network drive. It is mapped
to a share called "F" on server "mail".

In your first post you said that you were unable to unmap it.
I assume that you did this from within Explorer. Do it from a
command prompt this time, running these commands and
reporting their output:

net use
net use F: /del
net use


Frank Neuner said:
The F drive on the workstations is the same as the F drive on the Windows
2000 server, which in turn is shared as the F drive on this server
No, all my local drives are different and so is the F drive

reates, deletes, or lists a volume mount point.

MOUNTVOL [drive:]path VolumeName
MOUNTVOL [drive:]path /D
MOUNTVOL [drive:]path /L

path Specifies the existing NTFS directory where the mount
point will reside.
VolumeName Specifies the volume name that is the target of the mount
point.
/D Removes the volume mount point from the specified directory.
/L Lists the mounted volume name for the specified directory.

Possible values for VolumeName along with current mount points are:

\\?\Volume{8bce4e70-b211-11d6-9b4b-806d6172696f}\
C:\

\\?\Volume{8bce4e71-b211-11d6-9b4b-806d6172696f}\
D:\

\\?\Volume{8bce4e72-b211-11d6-9b4b-806d6172696f}\
A:\

New connections will be remembered.


Status Local Remote Network

-------------------------------------------------------------------------- -----
OK F: \\mail\f Microsoft Windows Network
The command completed successfully.

Local name F:
Remote name \\mail\f
Resource type Disk
Status OK
# Opens 0
# Connections 1
The command completed successfully.

NOTE: the subst command produced no output

Regards

Frank

Frank Neuner said:
I have a network where all XP Pro clients have an F drive.
It is not a mapped drive.
I can right click and say disconnect, however the drive stays and I can
still access it via a double click on the drive.
I need to setup login scripts, but when the login script tries to map the f
drive, I get an error to the effect that the drive letter already exists.
I have scanned the registry, but can not find any hints on how this drive
letter is 'connected' to the server.
It is not coming from the server, because all the new machines we put in do
not have this strange F drive.
Any hints?

Frank
Click to expand...
Click to expand...
 
Back
Top