MS SQL server not recognized as a database server


#1

I have a MS SQL server that is not recognized as “database server”. For the default instance it is using port 1433, and dynamic ports for additional instances. What do I need to do to fix this.

Kind regards,
Wijnand


#2

It is possible to add additional TCP ports for ExtraHop Discover built-in protocol classification. By default it attempts to discover expected traffic over the RFC documented TCP ports related to a specific protocol.

Below is a link that explains how to add addtional ports for protocol classification if it is not using standard ports:

https://docs.extrahop.com/current/eh-admin-ui-guide/#protocol-classification

That being said, It is also possible that this communication is not correctly being detected. I recommend reaching out to ExtraHop Support for assistance with troubleshooting this unclassified traffic, they will be able to help you narrow down the exact cause.