Problem with shared folder access. Windows Server 2003

Михаил Андросов 336 Reputation points
2022-09-21T19:13:35.563+00:00

There are two Windows Server 2003 servers with IP addresses: 10.77.160.17 and 10.77.160.18. The servers are members of the Active Directory domain.
Folders are shared on the servers and the appropriate permissions are configured.
There is a problem when a user accesses from the first server to a shared resource on the second server and vice versa.
Access is carried out in the form:
\10.77.160.18
With such an attempt, a name and password request window is displayed after a few seconds. If you enter the name and password of the current user, an error message will be displayed:
Username you typed is the same as the username you logged in with. That username has already been tried. A domain controller cannot be found verify that username
At the same time, a warning is recorded in the event log:
Source: LSASRV
Category: SPNEGO (Negotiator)
ID: 40960
The Security System detected an authentication error for the server cifs/10.77.160.18. The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request.
(0xc000005e)".
I checked access to shared resources from a domain controller. Such access was without any problems.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,266 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Dave Patrick 426.2K Reputation points MVP
    2022-09-21T19:24:16.397+00:00

    Has it ever worked? Have you tried using the name rather than ip address for access?

    0 comments No comments

  2. Михаил Андросов 336 Reputation points
    2022-09-22T06:12:55.967+00:00

    Yes, I tried. When addressing by name, the same thing happens.
    It looks like the problem is in Windows Server 2003. From these servers, I cannot access shared folders on all other servers. I tried to contact domain controllers.

    0 comments No comments

  3. Dave Patrick 426.2K Reputation points MVP
    2022-09-22T12:46:48.613+00:00

    Please run;

    Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
    repadmin /showrepl >C:\repl.txt
    ipconfig /all > C:\dc1.txt
    ipconfig /all > C:\dc2.txt
    ipconfig /all > C:\memberserver.txt
    ipconfig /all > C:\problemworkstation.txt

    then put unzipped text files up on OneDrive and share a link.

    0 comments No comments

  4. Михаил Андросов 336 Reputation points
    2022-09-22T18:42:20.597+00:00

    Unfortunately, I cannot provide the results of the dcdiag utility execution. The report provides a lot of information about the network structure. The provision of such information is prohibited by our security service.
    The link below contains the rest of the requested reports.
    If you can draw any conclusions from them, it would be great.
    https://1drv.ms/u/s!Alw1m4Yt-nFSh5p-VETZO7zpJJNRCw?e=aUMOMf

    On the Internet I found several links similar to our problem. Unfortunately, links to Microsoft sites are no longer valid.
    https://forums.tomshardware.com/threads/lsasrv-event-id-40960-and-40961.1080384/

    https://winitpro.ru/index.php/2013/08/19/oshibka-0xs0000005-i-drugie-problemy-s-poslednimi-obnovleniyami-microsoft/?ysclid=l8c0rfsuuq849798982