Testing connectivity to FileBridge

How to test connectivity for FileBridge using Telnet

Description

Test FileBridge connectivity

Why do this test?

In order to connect to FileBridge drive, your Firewall and antivirus program shall allow communication to the FileBridge URL.

When do you need to run this test?

When one of the below is true:
  1. If you are a new client and have not connected to FileBridge before
  2. If you have recently installed a new Firewall, IPS, IDS or an Antivirus program
  3. Recent change in ISP or Firewall rules

Process to test the connectivity

Using Powershell

If you are using Windows 8.1 or newer (Powershell v4), do the following: 
  • Start Powershell prompt 
  • Type the following: Test-NetConnection <FileBridge URL> -port <port> 
    • Where:
      • <FileBridge URL>: is the URL provided to you for filebridge: i.e: abcdrive.gotomyerp.com
      • <port>: is the designed port provided to you. for filebridge: i.e: 8443

Using Telnet

There are two steps to check the connectivity.
  1. Install Telnet Client
  2. Telnet to the FileBridge port

Install Telnet Client

  • Start -> Control Panel -> Programs and Features -> Click on "Turn Windows Feature On or Off" as per the below image

 
 
 
  • Click to select "Telnet Client" as per below image 

Telnet to FileBridge Port

  • Go to start -> command prompt
  • Type the FileBridge URL and port number provided by gotomyerp. For this example we are using a demo FileBridge URL abcdrive.gotomyerp.com and a demo port 1234. Please type the following without quotes "telnet abcdrive.gotomyerp.com 1234"and hit enter as per the below image.

  • After hitting enter in the above window if you get a blank window with a cursor blinking it means that your
    connectivity to FileBridge is fine, however, if you get the below screen, it means there is something wrong with your connectivity        

Resolution

  • If you are unable to connect to FileBridge port you will need your IT to open the FileBridge port to the
    FileBridge provided by gotomyerp, and if there are IPS/IDS rules they would need to exclude the FileBridge URL from it.
  • OR If you are able to telnet and still not able to Map FileBridge drive then one of the information you entered while setting up FileBridge is incorrect.
 
    • Related Articles

    • Cleanup FileBridge Configuration

      Summary: In some instances, the FileBridge client needs to be reinstalled. Performing a simple uninstall from the "Programs and Features" window only removes the FileBridge client, but does not cleanup any associated files and/or configurations. One ...
    • Cannot login to FileBridge after changing password

      Problem: You change your password for one of the following reasons: You decided to change it yourself You received a notification of password expiration, and reset it as a result Your password expired, and you reset it using SSRPM or by contacting ...
    • Why do I keep getting disconnected from my session?

      Problem: At random times, the session seems to get disconnected. When you log back in, in most cases, the application is where you left off.   Reason: There are a few reasons why you may get disconnected from your application. Having the same user ...
    • Having trouble mapping FileBridge

      Problem: When trying to map FileBridge, you receive the "Failed" message. Reason: There are many reasons this could happen. Here are a few you can check: Have you recently changed your password? The old password may still be cached in your system. ...
    • Receiving credential prompt when opening files on FileBridge

      Problem: When trying to open a file directly from the FileBridge drive, the user can sometimes receive a credential prompt upon attempting to open the file. (This mostly happens with Office documents and PDF documents).  Clicking cancel on this ...