Description

Why do this test?

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

• 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

1. Install Telnet Client
   
2. Telnet to the FileBridge port
   

• 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 
  

• 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.