Reset Search



Why does Windows server not respond to NBNS to different subnet?

« Go Back


TitleWhy does Windows server not respond to NBNS to different subnet?
Why is Windows AD server not responding to LDAP agent bind requests?
Why is LDAP agent not able to bind with AD server?
  • All Summit WM3000 Series Controllers
  • ExtremeWiNG Controllers
  • WirelessWiNG Controllers
  • ExtremeWiNG Access Points
  • WirelessWiNG Acess Points
  • WiNG 5 Software
With KB3161949 update Microsoft changed the way server is allowed to respond to NetBIOS queries and prevents responses to outside subnets.

User-added image

User-added image

This obviously brings problem to external devices trying to authenticate or bind with server.

User-added image

To overcome this you can either:
  • uninstall security update KB3161949 from your server (not recommended)
  • update registry parameter for NetBT with Dword AllowNBToInternet set to 1.
As we do not recommend to uninstall the patch itself, here is how to add the Dword using CMD
reg add "HKLM\System\CurrentControlSet\Services\NetBT\Parameters" /v "AllowNBToInternet" /t REG_DWORD /d 1 /f
or using PowerShell
Set-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\NetBT\Parameters -Name AllowNBToInternet -Type DWord -Value 1
After the parameter is created, you have to reload server and after that it will respond to outside NBSTAT calls

User-added image
User-added image
Additional notes
Taken from web article
Please keep in mind that SMBv1 should be used to avoid problems with LDAP based auhentication



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255