Re: How does authentication work?

"and clicking on the drive in Explorer pulls back an error"

What error? Also check the event logs on both ends.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"The_Nite_Owl" wrote:
When a device attempts to connect to a shared drive on another server it is the remote server that requests the credentials to authenticate the connection right?
What determines how long the connection can remain before the remote server requests authentication again?

We have a Win 2003 server that maps drives to SAN sharespace through another Win 2003 server.
The drive mappings are made using a different set of credentials than the current logged on account.
Win 2003 server after SP1 no longer caches credentials for connections using a different account than the logon account.

When we boot our server the mappings are established but the drives do not connect until you click on one of them in Windows Explorer which pops up an ID/Password prompt (because it will not store the credentials). Once the credentials are entered the connection works. If the connection is unused for 15 minutes the remote server auto-disconnects the connection as it should but when the connection is accessed again it is re-established. This works as expected but in something less than 48 hours the connection dies and clicking on the drive in Explorer pulls back an error. The mappings have to be deleted and re-added which forces a new authentication prompt and then the connection works again.

I believe that when the remote server receives valid authentication credentials that it sets the connection to be allowed from that remote device for a specified time after which it requires re-authentication which our server cannot provide because it does not cache credentials for connections using a different logon id/password.

What could be governing the time the connection can remain before needing re-authentication?
Our Network Engineering team just shrug their shoulders and say it is not on their end.



.

Relevant Pages

  • RE: Remote Desktop Connection (Terminal Services Client 6.0)
    ... When a domain is not presented for the username, ... the server name entered was ... into the credentials dialog. ... Vista Remote Desktop Connection Authentication FAQ ...
    (microsoft.public.windows.terminal_services)
  • Re: How does authentication work?
    ... This I believe is because 4 drives ... the connection fails all 4 drives have to be deleted before any can be ... is the remote server that requests the credentials to authenticate the ...
    (microsoft.public.windows.server.general)
  • Re: NT "net use" Malfunctions
    ... connection open on that server as /user:newbie ... > You can't map drives using DIFFERENT credentials to the SAME server. ... If you have received this message in error please notify us immediately by return email and destroy this email. ...
    (Security-Basics)
  • RE: Dropping Shared Connections (only)
    ... source like a router or a server, or a ... with more information about the general network environment infrastructure ... while working on files on those drives. ... server with an RDC connection and it continued to act normally. ...
    (microsoft.public.windows.vista.networking_sharing)
  • Re: How does authentication work?
    ... What determines how long the connection can remain before the remote server requests authentication again? ... The drive mappings are made using a different set of credentials than the current logged on account. ... The mappings have to be deleted and re-added which forces a new authentication prompt and then the connection works again. ...
    (microsoft.public.windows.server.general)