I have combed all the archives and not found any answers so here we go. I have a very custom Access application that we upgraded to Access 2013 with much ado because they removed the lovely .adp functionality. Now the database connects through a file ODBC connection (Native Client 10.0) to SQL Server 2012. All queries (hundreds of them) have been converted to pass-through queries using the same ODBC connection. It was working fine.
And then...upgrade to Windows Server 2012 r2. Now the front ends (each user has their own copy on their RDP session) are intermittently crashing with the message "Your network access was interrupted. To continue, close the database, then open it again.". Many times the user has to use task manager to close it.
We checked on the possibility of SMB causing the issues and it has been ruled out. https://www.petri.com/how-to-disable-smb-2-on-windows-vista-or-server-2008
So I'm focusing on the ODBC driver. It is a massive undertaking to upgrade the SQL Native Client driver from 10.0 to the latest 11.0. I don't want to go to all the trouble if it is not going to fix the problem. So the big question is "Can the use of an older Native Client driver cause connection drops on on my Access Database? ".