Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > Fastbit server didn't respond. waiting for 30s. Unable to connect to [Netflow DB Server]

Fastbit server didn't respond. waiting for 30s. Unable to connect to [Netflow DB Server]

Created by Leif Amland, last modified by Melanie Boyd on Jun 21, 2018

Views: 1,008 Votes: 0 Revisions: 4


This article describes the issue about the connection between NTA FlowStorage DB and the Orion Server that prompts this message:

Error: < fastbit server didn't respond. waiting for 30s >


This article applies NTA 4.2 and earlier. NTA 4.4 and later versions use a SQL Server database to store flow data. For more information, see Databases used by SolarWinds modules.


NTA 4.2 and earlier


This issue occurs because the firewall is blocking the connection.


Turn off the firewall and it should automatically connect back to the database. You can verify this in the Web Console under the NetFlow tab. A message appears that the connection has resumed.


Last modified