Re: How does authentication work?
- From: "The_Nite_Owl" <the_nite_owl@xxxxxxxxxxx>
- Date: Fri, 16 Nov 2007 12:46:48 -0500
Well, silly enough I did not save the error message. When trying to re-map
one of the drives it would tell us it was not able to as the drive was
already mapped under a different ID. This I believe is because 4 drives
were mapped with the domain account and the credentials not cached so when
the connection fails all 4 drives have to be deleted before any can be
re-mapped.
We have seen nothing in the event logs related to connectivity, mapping or
authentication errors.
"Dave Patrick" <DSPatrick@xxxxxxxxxxxxxxxx> wrote in message
news:6E7494F1-7751-405F-B5E3-2BE00E12C2DA@xxxxxxxxxxxxxxxx
"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.
.
- References:
- How does authentication work?
- From: The_Nite_Owl
- Re: How does authentication work?
- From: Dave Patrick
- How does authentication work?
- Prev by Date: ESENT TCPSVCS (1216) error every so often.. server is CM 2007/DPM agent/DC/DHCP server..
- Next by Date: kerbtray.exe shows workstations listed on a DC server.. is this normal?
- Previous by thread: Re: How does authentication work?
- Next by thread: Re: How does authentication work?
- Index(es):
Relevant Pages
|
|
