Support Center

Could Not Connect To Arbiter

Last Updated: Aug 30, 2018 07:21AM PDT


After adding a TMG Source in Settings | Sources, you receive the issue 'Could not connect to Arbiter'.


The Fastvue TMG Reporter service running on the Fastvue server cannot communicate with the Fastvue Arbiter service running on your TMG Server on port 49361.


1. Add the Fastvue Access Rule to TMG 

Make sure you have added an Access Rule to Forefront TMG that allows TCP port 49361 from the Fastvue server to the TMG Server (localhost) for all users.

There is more information on how to do this in our Getting Started Video, or you can read the exact steps here: (See Step 6).

2. Test the Access Rule is not being overridden by another deny rule

If you have added the Access Rule, ensure there is no other rule that may be denying the traffic first. The best way to check is by running a query in the Logs and Reports view in the TMG Management console:
  1. Open the TMG Management Console and go to Logs and Reports
  2. Click Edit Query and select the Following query:
    • Log Record Type Equals Firewall or Web Proxy Filter
    • Log Time Live
    • Destination Port Equals 49361
  3. Click Start Query
You will start to see any allowed or denied connections on port 49361. If they are denied (red), go to the Rules column and see the Firewall Rule that is denying the traffic. You can then make the necessary adjustments to Rule order. 

3. Make sure the Fastvue Arbiter service is running.

Check Fastvue Arbiter Service status.
1.  Right-click the Start button | Click Run and type in services.msc
2.  Scroll down to Fastvue Arbiter and check the status is Running.
3.  If the service is not running or stopped click the Start service or Restart service button.

If you receive the error:
Fastvue Arbiter service is unable to start. You receive the error message: The Fastvue Arbiter service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

Go to C:\Programdata\Fastvue\Arbiter and delete the Arbiter.xml file.  Then start the service.

4. Ensure there are no devices, firewalls, AV software etc interrupting communication

If you have added the Fastvue Access Rule to your TMG Server, yet you still get the connection issue, there may be other network devices or software preventing the communication.

The best way to check that the Fastvue TMG Reporter server can access the Fastvue Arbiter on your TMG Server is to open a Telnet session from the Fastvue Server to the TMG Server on port 49361.
To do this:
  1. Install Telnet if it isn't already. Go to Programs and Features | Turn Windows Feature on or off | Check 'Telnet Client' and click OK.
  2. Open a command prompt (Start | Run | cmd) and type Telnet
  3. Then type:
    open <ip address of TMG Server> 49361
    open 49361
If the connection is unsuccessful, check that there are no other devices, firewalls, anti-virus software etc between the two servers that may be blocking the connection. Also, check other access rules in TMG itself to ensure none are conflicting. 

If the connection is successful, you should start seeing records being imported in Settings | Sources. If not, try restarting the Fastvue TMG Reporter service on the Fastvue server, and the Fastvue Arbiter service on your TMG Server. If you're still having issues, please contact Fastvue Support.

Contact Us

  • Post a Public Question
  • Email Us
  • Chat with us

    Call Us @ 888.885.6711
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found