NTLM based auth fails for LOCAL SYSTEM when accessing shared folde

June 26th, 2009 - 11:25 am ET by Dave | Report spam
Hi,

This is a cross post from Microsoft.Public.Windows.Server.Clustering...just
wondering if any can offer thoughts?

Info:

- Windows 2003 SP2 active/passive cluster
- Physical nodes are called "Node1" and "Node2"
- These nodes are members of Windows 2003 AD domain called "ADDomain.Local"
- Cluster Name resource is called "VirtualServer"
- Cluster Name resource does NOT have Kerberos auth enabled
- "Node1" is currently active
- Shares are created as clustered resources with the following permissions:

SHARE ACL specifies EVERYONE:Full Control
NTFS ACL specifies EVERYONE:Full Control

- All shares are currently active on "Node1"
- Test share is "\\VirtualServer.ADDomain.Local\TestShare"
- Test computer is "ADDomain\TestPC"
- Test user is "ADDomain\TestUser"
- Both DNS and WINS are configured and confirmed working properly in the
environment

OBJECTIVE is to read the TestShare folder with following four CMDs:

dir \\VirtualServer.ADDomain.Local\TestShare
dir \\Node1.ADDomain.Local\TestShare
dir \\IPAddr_for_VirtualServer\TestShare
dir \\IPAddr_for_Node1\TestShare

Results

ADDomain\TestUser logs on to ADDomain\TestPC and is successful with the
OBJECTIVE in all four cases. Each one has to fall back to NTLM.

Next is a test with credentials of LOCAL SYSTEM ( ADDomain\TestPC ):

- Test #1 FAILS
- Test #2 success
- Test #3 FAILS
- Test #4 FAILS

I'm assuming that test #2 succeeded because we used the hostname of the
physical node which was able to use Kerberos and had a valid SPN in AD.

I'm trying to understand why NTLM fails in the other three cases under
context of a domain computer even while it succeeds in all cases under the
credentials of a domain user.

Thank you!
-Dave
email Follow the discussionReplies 1 replyReplies Make a reply

Replies

#1 DaveMo
June 29th, 2009 - 02:13 pm ET | Report spam
On Jun 26, 8:25 am, Dave wrote:
Hi,

This is a cross post from Microsoft.Public.Windows.Server.Clustering...just
wondering if any can offer thoughts?

Info:

- Windows 2003 SP2 active/passive cluster
- Physical nodes are called "Node1" and "Node2"
- These nodes are members of Windows 2003 AD domain called "ADDomain.Local"
- Cluster Name resource is called "VirtualServer"
- Cluster Name resource does NOT have Kerberos auth enabled
- "Node1" is currently active
- Shares are created as clustered resources with the following permissions:

SHARE ACL specifies EVERYONE:Full Control
NTFS ACL specifies EVERYONE:Full Control

- All shares are currently active on "Node1"
- Test share is "\\VirtualServer.ADDomain.Local\TestShare"
- Test computer is "ADDomain\TestPC"
- Test user is "ADDomain\TestUser"
- Both DNS and WINS are configured and confirmed working properly in the
environment

OBJECTIVE is to read the TestShare folder with following four CMDs:

dir \\VirtualServer.ADDomain.Local\TestShare
dir \\Node1.ADDomain.Local\TestShare
dir \\IPAddr_for_VirtualServer\TestShare
dir \\IPAddr_for_Node1\TestShare

Results

ADDomain\TestUser logs on to ADDomain\TestPC and is successful with the
OBJECTIVE in all four cases.  Each one has to fall back to NTLM.

Next is a test with credentials of LOCAL SYSTEM ( ADDomain\TestPC ):

- Test #1 FAILS
- Test #2 success
- Test #3 FAILS
- Test #4 FAILS

I'm assuming that test #2 succeeded because we used the hostname of the
physical node which was able to use Kerberos and had a valid SPN in AD.

I'm trying to understand why NTLM fails in the other three cases under
context of a domain computer even while it succeeds in all cases under the
credentials of a domain user.

Thank you!
-Dave



Hello Dave,

Sounds like you have a fairly odd problem. There is some fairly old
behavior for the localsystem account where sometimes it will not
authenticate as the computer account but instead default to a null
session. null session is supposed to be part of Everyone so I'm still
not sure why that would fail. But it's the only difference I'm aware
of between auth of user and computer accounts.

My first thought would be to figure out how exactly how the
authentication is happening. Specifically, what identity is
authenticating to the server in the success and failure cases. The
first thing I would do is try to look on the server side and see if
there is a session listed for the remote computer. You would do this
under Computer Management if you were managing a normal file share,
not sure what you look under for your scenario but hopefully there is
something. If this doesn't work or you can't find a session/identity,
then look in the server security logs to see who authenticated to the
server when you try to connect from the localsystem process. Finally
I would try netmon and see if you can see the Kerb/NTLM traffic and
see if there is any good info there.

Finally, why are you trying to make everything use NTLM?

HTH,
dave

Similar topics