mapped drive

[micfly]

I have mapped a Network drive and enabled the option "Reconnect at Login." I
put a shortcut on the desktop, but every time I reboot and click the icon,
it says "Incorrect password". I can click OK and it will open the folder
(there is no password). As a convenience to my co-workers I would like to
avoid this.

We have several machines in the office, all w2k and only one is giving me
the error. It's just a temp folder on the server I have a few docs we share.
Any ideas?

 

[Phillip Windell]

I have mapped a Network drive and enabled the option "Reconnect at Login."
I
put a shortcut on the desktop, but every time I reboot and click the icon,
it says "Incorrect password". I can click OK and it will open the folder
(there is no password). As a convenience to my co-workers I would like to
avoid this.

We have several machines in the office, all w2k and only one is giving me
the error. It's just a temp folder on the server I have a few docs we
share.
Any ideas?

Yes.

Stop using Mapped Drives.

Use "Shortcuts" based on the UNC network path (\\machinename\sharename).
Copy the shortcut to the Desktop within the "All Users" profile. Verify
that the Shortcut file receives the proper permissions inherited from the
normal permissions of the All Users Desktop folder. Sometimes it takes a
little time,...sometimes it has to be forced,...sometimes it just works
without doing anything extra.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

[micfly]

Thanks for helping. Well, that's how I started out, just a shortcut to the
network folder on the desktop...But, same thing, it wanted you to login
every time after a re-boot? After I mapped it it solved that (except for
this one computer). Now that you mention it, though, I did not place the
shortcut in the All Users Desktop just the currently logged in user's
desktop. Would that make a difference?

 

[Phillip Windell]

Thanks for helping. Well, that's how I started out, just a shortcut to the
network folder on the desktop...But, same thing, it wanted you to login
every time after a re-boot? After I mapped it it solved that (except for

It will base access on what credentials the user is logged into the Source
machine with. The machine must be a domain member and your AD
Authentication must be functioning correctly. If your authentication isn't
working correctly then it is not going to matter if you use mapped drives or
shortcuts. Using the shortcuts is still the better choice,...you just may
have "other" problems happening there.

Active Directory Authentication depends heavily on DNS. If the DNS Scheme
isn't handled correctly you will have a mess. Every machine on the LAN
must use the AD/DNS for their DNS and absolutely nothing else. Even the
AD/DNS Machine will only point to itself in the TCP/IP specs. Then in the
config of the DNS services you add the IP# of the ISP's DNS to the
Forwarders list or leave the list blank and let it default to Root Hints.
Then the Firewall must allow the AD/DNS to make outbound DNS queries.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------