Mapped drive doesn't reconnect in Windows 2000.

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

Guest

In a Pc with Windows 2000 Professional I mapped a remote shared directory on
drive z:
I chose the Reconnect at logon option and filled user name and password for
'Connect using a different user name'. I used the following username: remote
hostname \ remote user1
with password -> remote user1 password. It works very well, but everytime
you logon locally you are prompted
for a password for the mapped drive because Windows says that it couldn't
reconnect the drive with the username

and password he knows.
Where is the trick?
Do I have to change something in the registry to make windows remember the
password ?
In fact on another Pc I mapped another drive using an username with blank
password and it reconnects

automatically.

Thank you
Filippo
 
setecastronomy said:
In a Pc with Windows 2000 Professional I mapped a remote shared directory on
drive z:
I chose the Reconnect at logon option and filled user name and password for
'Connect using a different user name'. I used the following username: remote
hostname \ remote user1
with password -> remote user1 password. It works very well, but everytime
you logon locally you are prompted
for a password for the mapped drive because Windows says that it couldn't
reconnect the drive with the username

and password he knows.
Where is the trick?
Do I have to change something in the registry to make windows remember the
password ?
In fact on another Pc I mapped another drive using an username with blank
password and it reconnects

automatically.

Thank you
Filippo
Click to expand...

If you log on as "Filipo" with a password of "xxxyyy", make sure
that the account Filipo / xxxyyy also exists on the PC that hosts
the share. If it does not exist then you will be treated as a
stranger and you will be challenged each and every time. This
is what Windows security is about!
 
I don't agree.
What is the 'Connect using a different user name' option for ?
According to me it is available to avoid the necessity to have the local
account you log with on the PC that hosts the share too.
It is quite confusing because this option doens't work in conjunction with
'reconnect at logon'.
As I stated in my first message the following scenario has no problem:
create a mapped drive using:
- reconnect at logon
- in the 'Connect using a different user name' insert the name of the
remote host + '\' + a remote username.
If the password for that username is blank you can log on locally with ever
account, the mapped drive will work fine.
Instead if the password is not blank you will be prompted to insert it. Why ?

Thanks
Filippo

"Pegasus (MVP)" ha scritto:
 
"Reconnect at logon" has nothing whatsoever to do with
validation. It only means that Windows will ***attempt***
to restore the shared connection at logon time. Whether
it succeeds or not is an entirely different matter.

Please feel free to disagree with me. The fact remains that
you will face the password challenge for as long as your
logon account / password is not recongised by the host
computer. To have it recognised, it must exist on the host
computer.
 
Please feel free to disagree with me. The fact remains that
you will face the password challenge for as long as your
logon account / password is not recongised by the host
computer. To have it recognised, it must exist on the host
computer.
Click to expand...

Sure a valid logon and password must exist on the host computer but there is
no need they are the same as those of the locally logged account. When I map
the remote share I say to use username Pluto (which is a valid account on
remote host but NOT on local one) and I insert Pluto 's password. Locally my
account is different from Pluto and everything works fine !
When I log on again windows tries to reconnect the network share and it
tries using Pluto's account, not mine, but it fails. It says that the last
connection was done using username Pluto and it asks for a password.
Inserting Pluto's password, which has nothing to do with local accounts it
works.
What I'm asking is why windows forget Pluto's password.
Is it clear now ?
I would expect a behaviour similar to that of Stored username and Password
of windows XP.
 
The local machine does not have "Pluto's password" to connect with
because it does not exist on the machine.
 
There is a way to open up machines to the whole world by
enabling the Guest account. I never use this method because
of its obvious security implications. The following thread
deals with your subject and it might help you if you wish to
follow this path:

Newsgroup: microsoft.public.windowsxp.general
Subject: computer asking for password when accessed on the network
 
Unlike Pegasus, I understand what your talking about because I have same
problem.

Just wondering if you have had any luck figuring it out in the couple of
months since you started this thread?
 
Back
Top