Hi @Aldren18 and team. I have discovered that this issue is not related to ip address vs. fqdn but it is directly related to the multi user setting on the database server. If multi user hosting is turned off from the client installed on the database server, then banking reconciliation works normally from a workstation client over a mapped drive. If I turn multi user hosting back on, the problem persists.
Can you escalate this to a team that could help me and my IT/network team understand how/where this bottleneck is happening with the banking reconciliation process while multi user hosting is on? Again worth noting, when hosting is enabled, the process completes but it takes many times longer. Like, 2 hours versus 2 minutes.
