• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 38 subscribers
  • Views 461 views
  • Users 0 members are here
Options
Related
This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

port 137

AJ2

We are running Orion NPM and our security tools found that the server is constantly trying to talk to outside addresses via port 137.  Does anyone know why NPM would need to talk using port 137 to the outside?

  • 0

    This is more than likely attributed to NetBIOS

    This is due to the behavior of Windows servers that use NetBIOS (as well as DNS) to resolve IP addresses to names using the "gethostbyaddr()" function.

    This shouldn't be too big of a concern for you.

  • 0

    Hi AJ2,

    You might want to disable the NetBios Over TCP/IP protocol on the interface and use the LMHOSTS file for the servers that needs to be resolved using NB names. That might be the case e.g. of the SQL Server.

    You should no more have any NetBios Lookup Query trying to go through your firewall if you do so.

    Some posts about the same issue:

    HTH,

    Yann

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.

SolarWinds Customer Success Center Certification Media Vault Link Accounts
About THWACK Blogs For Government Edit Settings Free Tools & Trials
Legal Documents Terms of Use Privacy California Privacy Rights Security Information
©2024 SolarWinds Worldwide, LLC. All Rights Reserved.