Document Management Software Help : Docsvault

Firewalls & Remote Connections

Firewalls & Remote Connections

Previous topic Next topic No directory for this topic  

Firewalls & Remote Connections

Previous topic Next topic Topic directory requires JavaScript  


Having trouble in Client Connections?


There are primarily three reasons for the client failing to connect to the Docsvault server.


The Docsvault server name specified in client login form is not valid.


The Docsvault server name is the hostname or the IP address of the machine on which the Docsvault server is running. The Host name of the machine running the Docsvault server side can be found from under the ‘Services’ node in the Docsvault Server Manager dialog on the server side. (Note: If you are connecting the clients over the internet, you will need to use your server’s public IP address to reach it.)



Remote connections are not enabled for your SQL server


Docsvault will enable necessary remote connections if the Docsvault configuration wizard installed the SQL server itself. However if you specified your own SQL server, you will need to ensure that the SQL Browser service is running and the TCP/IP protocols are enabled on your SQL instance. Go to Start > run > type 'services.msc' and hit enter to open the services dialog. Find the SQL Browser service and start it if it’s not running. Make sure you change its start-up type to 'Automatic' from its properties dialog so it runs automatically when your server restarts.


Ensure that TCP/IP are enabled for SQL Server hosting the Docsvault database. To do that go to SQL Server Configuration Manager > Protocols for <your_SQL_server>. On the right panel make sure the TCP/IP status is enabled. If not just double click it to enable it and then restart the sql server service to make this change effective. (see figure 1 for reference)



A firewall is blocking network traffic between the client and the server


Firewalls will block communication between Docsvault Client and Server if not configured properly. Follow the steps below to ensure that proper firewall rules have been created to allow Docsvault traffic to pass through the firewall.


If your firewall is application based (ex: Windows Firewall, Norton, McAfee, etc. )


The following Docsvault executables i.e Docsvault server and client along with the necessary MS SQL Server executables should be added to the exemptions/allowed list of the firewall. Docsvault installer automatically adds the necessary executables to the firewall exception list for the built-in Windows firewall.


Docsvault Client side:


dvClient.exe (by default located at C:\Program Files\Docsvault SB\Client\)


Docsvault Server side:


dvServer.exe (by default located at C:\Program Files\Docsvault SB\Server\)

sqlservr.exe (by default located at
C:\Program Files\Microsoft SQL Server\MSSQL10_50.DOCSVAULT\MSSQL\Binn\

  (Note: Replace MSSQL10_50.DOCSVAULT by your actual SQL instance folder if you used your own    SQL server to host Docsvault db)

sqlbrowser.exe (by default located at "C:\Program Files\Microsoft SQL Server\<90 or 100>\Shared\")



If your firewall is port based or if you require port forwarding from your router to the Docsvault server


If you are using a port based firewall or need to forward the right ports you will need to open/forward the following ports.


TCP Port 3831: To allow connection to the Docsvault Server Service (dvServer.exe)


UDP Port 1434: This SQL Server Browser service listens for incoming connections to a named instance of SQL server hosting Docsvault db and provides the client the TCP port number that corresponds to that named instance.


TCP Port for SQL server instance hosting Docsvault database:The Docsvault's instance of SQL server listens on a dynamic port (between 49152 & 65535) selected randomly by the SQL server. The SQL clients first connect to the browser service (port# 1434) to know the exact port number a named instance of SQL  server is listening to for the requested database.





From the start menu find and run the “SQL Server Configuration Manager”.


Expand SQL Server Network Configuration, expand “Protocols for DOCSVAULT”, and then double-click TCP/IP.


From the TCP/IP dialog that opens up, click on 'IP Address' tab and navigate all the way down to "IP All" section. The number against the ‘TCP Dynamic Ports’ is your dynamic port number. (See the point below to make SQL server run on a static port number).






(Recommended when using a port based firewall & for port forwarding when required)


Although SQL server will normally reuse the same old port number that it listened to upon restart, it’s a good idea to set a static port for the SQL Server instance running the Docsvault database so that it never changes and there are no further connection issues once the firewall is set. Follow the 3 steps in the point above to reach the TCP/IP Properties dialog and navigate to the IP ALL section


Delete the number against "TCP Dynamic Ports" and specify a desired free port number (59059 in example below) against "TCP Port".


Click OK and restart the SQL server service from the 'Services' node in Docsvault Server Manager dialog for the new port to take effect.