Re: How does authentication work?
- From: "The_Nite_Owl" <the_nite_owl@xxxxxxxxxxx>
- Date: Tue, 20 Nov 2007 07:24:29 -0500
The server is one the domain but we log into it with a local account.
It is an appliance box and the application is supported by the vendor.
Security required us to use a local account login for the box so that the
vendor can connect to support it without being able to browse the entire
network.
Since the shared drives are out on the domain we have to use the domain
account to map those drives with alternate credentials.
This was not a problem until we upgraded the server to 2003 SP2 and it
precluding caching of alternate credentials.
But it seems to me that the length of time the connection can remain valid
before requiring re-authentication is set by the remote server and that
there may be a solution on that end for us. I just have not found anyone
that can confirm or explain what needs to be done.
"Dave Patrick" <DSPatrick@xxxxxxxxxxxxxxxx> wrote in message
news:DDC9155D-B29C-47BE-B91E-6799D1E375FA@xxxxxxxxxxxxxxxx
You would get that effect if you connected with the domain (or any other)
account and the local account simultaneously. Why not join it to the
domain?
--
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:
We do not use more than one set to connect to those resources, just the
domain account.
The problem is that when the remote server times out the connection and
wants credentials sent again our server cannot send them because they are
not cached.
The problem is in the connection ever timing out in the first place. If
Microsoft had not disabled caching of passwords for the non-logon account
we would not have the issue but if the remote server did not set some
sort of expiration on an authenticated connection we would not have it
either. It's just that nobody seems to know how that connection seems to
go from being authenticated to no longer authenticated.
The multiple credentials for the resource is really not accurate, the
credentials would have been exactly the same except that Windows no
longer remembers what the old ones were so cannot actually compare them
and states them to be different requiring all mappings to that resource
to be dropped before any of them can be re-mapped.
It's frustrating but it's an application server that has to have those
mapped drives and they just disconnect at times we have not been able to
predict.
.
- Follow-Ups:
- Re: How does authentication work?
- From: Dave Patrick
- Re: How does authentication work?
- References:
- How does authentication work?
- From: The_Nite_Owl
- Re: How does authentication work?
- From: Dave Patrick
- Re: How does authentication work?
- From: The_Nite_Owl
- Re: How does authentication work?
- From: The_Nite_Owl
- Re: How does authentication work?
- From: Dave Patrick
- How does authentication work?
- Prev by Date: Re: Adding a new (additional) domain controller
- Next by Date: Re: Server 2003 Cannot shutdown - after Cloning HD
- Previous by thread: Re: How does authentication work?
- Next by thread: Re: How does authentication work?
- Index(es):
Relevant Pages
|