Windows Server 2012 R2 sharing is not working with its IP but working as \\server.

Question

Hi Team,

Windows Server 2012 R2 sharing is not working with its IP but working as \server with name. Need assistance thank you.

Answer 1

Hi @Shakeel Baharpet ,

Please refer to the following steps:

1.Click on see details to check the exact error message:

2.Then check SMB client log and SMB server log to see if there are something related for us to troubleshooting:

e.g.: A access B' shared file, then A is SMB client and B is SMB server.

3.Check if you can ping server's IP address.

Nslookup servername and see if returned IP address is right.

Best Regards,

Candy

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi Candy,

Thanks for the reply. Followed share troubleshooting steps.

1. IP is pinging and server name is also pinging.
2. Firewall is off and anti virus is disabled.
3. But SMB client logs showing port 445 5445 as disabled.
4. Can telnet port 445 via server name but not through IP.
   Firewall is off and antivirus also disabled. But still port 445 is blocking for IP don't know where its blocking all possible checks please helps if missing something.

Answer 3

Hi Candy,

Full error message.

Answer 4

Hi ,

Check the following registry path:**HKLM\System\CurrentControlSet\Control\Lsa\MSV1_0**

See if the a registry key named RestrictReceivingNTLMTraffic here and the value is 2. As picture below:

To allow NTLM traffic, or re-enabling NTLM authentication again: change Registry keys on both systems SMB client and SMB File server.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0

**RestrictReceivingNTLMtraffic    REG_DWORD    0x0**  
**RestrictSendingNTLMtraffic      REG_DWORD    0x0**  

Important: The information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs.

Best Regards,

Candy

--------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 5

Hi @Shakeel Baharpet ,

What I mean is if I have a registry key RestrictReceivingNTLMTraffic with value 2, then I will have the same issue. Try to set the value RestrictReceivingNTLMTraffic and RestrictSendingNTLMtraffic to 0:

RestrictReceivingNTLMtraffic    REG_DWORD    0x0  
RestrictSendingNTLMtraffic      REG_DWORD    0x0  

Then see if the issue still happens.

Best Regards,

Candy