I don't have access to network share by ip - windows server 2008r2/2012r2

drClays 146 Reputation points
2022-05-19T14:06:21.31+00:00

Hey,

2 days ago I had a problem with energy in my data center and my servers were restarted.

After they UP I saw a problem with access to a network share by IP, for example:

Not working: \10.0.0.20\c$
Working: \server\c$

Access by IP doesn't work to file server(Windows Server 2008r2), database, and rdp(Windows Server 2012r2), but works to two domain controllers and hyper-v host.

I think it's a problem with NTLM but how to find a bug and fix it?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,126 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,852 questions
0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Philippe Levesque 5,681 Reputation points MVP
    2022-05-19T14:15:05.543+00:00

    Hi

    First, does the server changed IP in the restart ? can you do a "ping server" to validate it's still 10.0.0.20

    Second point; It can happen with StrictNameChecking registry settings, please set it to 1 to disable it, to test it;

    Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
    DWORD name: DisableStrictNameChecking
    DWORD value: 1

  2. rr-4098 1,176 Reputation points
    2022-05-19T16:49:41.907+00:00

    Are the servers that are failing, and the DC's that are working, on the same subnet or vlan? Are the network properties and advanced properties the same?

  3. rr-4098 1,176 Reputation points
    2022-05-20T14:00:05.967+00:00

    Are there error's in the SMBClient and SMBServer event logs?

  4. drClays 146 Reputation points
    2022-05-27T07:01:52.23+00:00

    Does anyone have some ideas?

    0 comments
  5. MotoX80 31,571 Reputation points
    2022-05-27T11:52:53.167+00:00

    Does anyone have some ideas?

    As I recall, this is a Kerberos problem. Do you have NTLM enabled?

    https://www.bing.com/search?q=windows%20share%20kerberos%20logon%20failure%20ip

    By default Windows will not attempt Kerberos authentication for a host if the hostname is an IP address. It will fall back to other enabled authentication protocols like NTLM. However, applications are sometimes hardcoded to use IP addresses which means the application will fall back to NTLM and not use Kerberos.

    The simplest solution is to just use the server name and not the IP address.

    0 comments