We brought in a 2003 Storage Server R2 box to be our filer\print server. When I went to test the dfs replication it was failing. Upon reviewing the security log I noted we are getting a lot of security audit failures. However they are system failures with the computer accessing a share as the username. People arent having issues getting onto the network as their usernames pass and are granted access.
After reviewing loads of Microsoft material on the subject I am a bit baffled at
A. Why it is happening
B. How to fix it.
The typical error msg looks like this
Logon Failure:
Reason: The user has not been granted the requested
logon type at this machine
User Name: TTTESTER$ <--computer name
Domain: TEST.COM
Logon Type: 3
Logon Process: Kerberos
Authentication Package: Kerberos
Workstation Name: -
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: 10.0.0.126
Source Port: 0
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Did we miss something in the permissions of this member server? Obviously something got borked. I probably wouldnt worry about it too much as there isnt any issues with people accessing the shares. But I think this is the reason dfs replication is failing.
I am sure it is something easy to fix, of course the obvious is often looked over.
Any help is appreciated.
Thanks
After reviewing loads of Microsoft material on the subject I am a bit baffled at
A. Why it is happening
B. How to fix it.
The typical error msg looks like this
Logon Failure:
Reason: The user has not been granted the requested
logon type at this machine
User Name: TTTESTER$ <--computer name
Domain: TEST.COM
Logon Type: 3
Logon Process: Kerberos
Authentication Package: Kerberos
Workstation Name: -
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: 10.0.0.126
Source Port: 0
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Did we miss something in the permissions of this member server? Obviously something got borked. I probably wouldnt worry about it too much as there isnt any issues with people accessing the shares. But I think this is the reason dfs replication is failing.
I am sure it is something easy to fix, of course the obvious is often looked over.
Any help is appreciated.
Thanks
