top of page

LITIGATION SUPPORT TIP OF THE NIGHT

The views expressed in this blog are those of the owner and do not reflect the views or opinions of the owner’s employer. All content provided on this blog is for informational purposes only. The owner of this blog makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site. The owner will not be liable for any errors or omissions in this information nor for the availability of this information. The owner will not be liable for any losses, injuries, or damages from the display or use of this information. This policy is subject to change at any time. The owner is not an attorney, and nothing posted on this site should be construed as legal advice. Litigation Support Tip of the Night does not provide confirmation that any e-discovery technique or conduct is compliant with legal, regulatory, contractual or ethical requirements.

See my post on Running Regex Searches With a Grep Utility on the ILTA litigation support blog.

New tips for paralegals and litigation support profesionals are posted to this site each week. Click on the blog headings for better detail.

See How-To Videos on my YouTube channel.

Checking FASP Connection for RelativityOne

Jan 2, 2021

In order for RelativityOne to transfer data from a user's computer to Relativity server, it must be able to use multiple UDP ports to transfer data via the Fast Adaptive and Secure Protocol (FASP), which uses Port 33001. In order to see if a network is configured to transmit data to a fully qualified domain name via the FASP port run this PowerShell script:

Test-NetConnection -ComputerName [FQDN] -Port 33001

. . . FQDN being the fully qualified domain name. If a domain can be reached the value listed for the 'PingSucceeded' value will be true. If the specified port can be accessed then TcpTestSucceeded will also be true.

bottom of page