Can not find servers to connect

This page will help you in case you are looking for servers to connect to but no servers have been found.

When searching for servers, auto discovery might return no results:


Verify that the File Processor service is running

It is most likely that the File Processor is not running. Follow the steps to verify this:

  1. Right mouse click Windows Start menu and select [Run]. Or press WINDOWS KEY + R.
  2. In the Run dialog type: services.msc and click [OK].
  3. In the Services dialog find the Winking File Processor service.
  4. Make sure it is running. Double click to change the value.


Try to manually set the connection

When auto-discovery does not find any server, it might be that the auto-discovery service is being blocked.
If we know the server name or the IP address of the server, we could try to establish the connection ourselves.

  1. Start the File Processor client.
  2. Navigate to the [Server] tab in the ribbon.
  3. Select [Connections] to open the Connections options.

You can also access the connection-settings via the Options-button in the ribbon.

  1. Click [Add] to add a new connection.
  2. For the Host enter the name of the server or the IP address.

If you use DHCP and don't have a static/fixed IP address, it is recommended to use the computer- or servername: e.g. MYSERVER01.CONTOSO.LOCAL

  1. Fill in the port. (default: 8100).
  2. Click the Connect button.

Windows Firewall

If the steps above do not work, verify the Windows Firewall or any other anti-virus, firewall or security software.

  1. Temporary turn off the Windows Firewall on client and server.
  2. Verify if you can establish a connection and see if you can establish a connection.
  3. Turn on the Windows Firewall on the server, and verify again that you can establish a connection.
    Turn on the Windows Firewall on the client and verify.
    If you notice that you cannot establish a connection after turning on a firewall, then you have found that you need to allow a program through the firewall. You could add a new Inbound rule.