The Fastvue Reporter for SonicWALL Getting Started Guide recommends not to install Fastvue Reporter on your SonicWALL Analyzer or GMS server as both applications install a web server and compete for port 80 and 443.

Fastvue Reporter and SonicWALL Analyzer/GMS also listen for syslog messages on port 514, so installing both on the same server with default settings will result in port conflicts and one or both applications not functioning correctly.

However, it is possible to have both applications installed and running side-by-side on the same server with a little customization.

All you need to do is change the port that Fastvue Reporter for SonicWALL is available on from 80/443 to something else, and use a port other than 514 for sending and receiving syslog messages between the SonicWALL device and Fastvue Reporter.

Changing Fastvue Reporter for SonicWALL’s Web Interface Port

The web interface for Fastvue Reporter for SonicWALL runs on Microsoft IIS, which is the web server that comes with Microsoft Windows Servers.

SonicWALL Analyzer and GMS install and run a different web server called Apache Tomcat.

When you install SonicWALL Analyzer/GMS, you are asked which ports you would like to use, with the defaults being 80 and 443 (the typical ports used for http and https).

When you install Fastvue Reporter for SonicWALL, it installs Microsoft IIS, which simply uses port 80 by default.

After installing Fastvue Reporter for SonicWALL on a Windows Server that already has GMS or Analyzer running on port 80 and 443, the SonicWALL Analyzer or GMS interface will be displayed instead of the Fastvue web interface.

To access both web interfaces, you need to change the port that IIS is using to display the Fastvue Reporter web interface.

To do this:

  1. Open the Internet Information Services (IIS) Manager. The easiest way to do this is simply doing a Windows Search for ‘IIS’.
  2. On the left hand side, expand your server, expand Sites, and select Default Web Site. This is most likely the website you installed Fastvue Reporter into, especially if IIS was not installed before installing Fastvue Reporter.
  3. On the right hand side, click Bindings…
  4. Here you should see a binding for type http using port 80. Select the row and click Edit…
  5. Change the port to something other than port 80, such as 81. Be sure that the port you specify is not already in use by any other application. Tip: At the command line, run netstat -ano | findstr “81” to find the ID of any other process using the port (replace 81 with the port you want to use). Use Task Manager to find the process by ID (you may need to show the PID column)
  6. Click OK and Close to save the changes.
  7. Start IIS if it is not already running by selecting your server on the left hand side, and clicking Start on the right hand side.
  8. Start your Default Web Site, if it is not already running by selecting Default Web Site on the left hand side and clicking Start on the right hand side.
Changing IIS Default Website Bindings

 

You should now be able to browse to your server with the port specified, for example http://yourservername:81, and it should return either the IIS start page or the Fastvue Reporter web interface. If it returns the IIS start page, this means you specified a virtual directory for Fastvue Reporter when installing. In that case browse to http://yourservername:81/yourfastvuedirectory – for example http://10.1.1.100:81/fastvue

You should be able to access your SonicWALL Analyzer/GMS interface as normal using http://yourservername

Edit the Site Settings in Fastvue Reporter for SonicWALL

Now that the Fastvue Reporter web interface is running on a different port, ensure this port is specified in Fastvue Reporter by going to Settings | Site Settings. Enter the URL of Fastvue Reporter (for example http://yourservername:81). This ensures that Fastvue Reporter use the correct URL when sharing reports via email.

Changing the Syslog Port Between SonicWALL and Fastvue Reporter

Now that the web interface for both Fastvue and Analyzer/GMS are functioning correctly, the next step is to add a new syslog server on your SonicWALL device that uses a different port to your Analyzer/GMS server (514 by default).

To do this:

  1. Log into your SonicWALL device and go to Log | Syslog
  2. Under the Syslog Servers section, add your Fastvue/Analyzer/GMS server as a syslog server, but this time specify a port other than 514 (or the port used by Analyzer/GMS) such as 49514.
  3. Click OK to add the server.
  4. In the Fastvue Reporter for SonicWALL web interface, go to Settings | Sources and click Add Source.
  5. Enter the Name or IP address of your SonicWALL device (or select it if it is shown in the dropdown list) and enter the port you specified in step 2 above.
  6. Click OK to add the Source.

You should soon see records importing into the Source, and data displayed on the live dashboards. If you do not see records importing, please see our article on Troubleshooting SonicWALL Data Import Issues.

Now that the web interfaces for Fastvue Reporter and Analyzer/GMS are using separate ports, and syslog messages are being sent/received on unique ports, both applications should be operating on the same server in perfect harmony.

Just make sure the server’s hardware specifications support running both applications at the same time. Fastvue Reporter for SonicWALL’s recommended hardware specifications can be found on our Getting Started page.

If you have any questions or issues, please don’t hesitate to get in touch.