stillsyra
asked on
You might not have permission to use this network resource & System Error 1396
Starting yesterday, some computers have problem with shared resources on a file server. The server is Windows 2008 R2 standard, a DC and file server.
When trying to connect to the server with server name, the error message shows:
\\fileserver is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
Logon Failure: The target account name is incorrect.
When trying to connect to the server with IP address, it works fine to access the resources.
When use net use in Command Prompt to map a network drive to the server with server name, the error message shows:
System error 1396 has occurred.
Logon Failure: The target account name is incorrect.
I restarted the server yesterday and it worked for a short time, but the problem started again today.
Can anyone help please?
When trying to connect to the server with server name, the error message shows:
\\fileserver is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
Logon Failure: The target account name is incorrect.
When trying to connect to the server with IP address, it works fine to access the resources.
When use net use in Command Prompt to map a network drive to the server with server name, the error message shows:
System error 1396 has occurred.
Logon Failure: The target account name is incorrect.
I restarted the server yesterday and it worked for a short time, but the problem started again today.
Can anyone help please?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm not sure if this is a DNS issue. I can't access the shared resources with the server name, but I can ping the server name and it shows correct ip address.
I mentioned two other common causes...
Confirm the results of checking these.
Confirm the results of checking these.
ASKER
There was a AD replication issue on one of the domain controllers (not the shared resource server). After fixing the replication issue, everything's working now: shared resourced and printers.
I'm glad you got your issue resolved. You didn't have to award me any points though, since it appears that the solution for your problem was not among any of my suggestions. Best would have been to accept your own post with relevant details as the answer.
Cheers!
Cheers!
ASKER
It was a Kerberos authentication issue, which was caused by AD replication failure.
Refer to this article:
https://blogs.technet.microsoft.com/danstolts/2011/06/resolving-network-issues-you-might-not-have-permission-to-use-this-network-resource/
Also check this thread.
Hope this helps!