Crystal Closing without Crash Message in Database Expert when browsing connected database tables

Recently changes were made to allow us to run Crystal against a specific database through eVPN from home.

Prior to the change everything worked perfectly from virtual machines or on site but not through the eVPN.

Post change we can now run reports and even modify them using existing tables from virtual machines, on site, or through the eVPN.

However if we try to use the Database Expert to view new tables to pull into reports Crystal closes without any message from virtual machines, onsite or the eVPN.

Crystal still works properly when connecting to other data sources.

Can anyone tell me what might be causing this behavior difference now?

What does Crystal do differently when browsing with the Databse Expert than connecting to run a report?

What might the connection teams have configured incorrectly when modifying the tunnel connecting us to this database.

I am running Crystal Reports 11.5.8.826