The other issue was the ticket size - we combined ad forests, and too many groups causes an issue. This for the most part increased stability as it forces acknowledgment of the packet.

I know on the windows side, I had policy pushed out to force Kerberos to use tcp ip rather than UDP. Mac has the ability to check Kerberos tickets.

This topic was modified 2 years, 10 months ago by christoph.kauflin.Somehow Excel does not give us the solution to use the user login and password to connect to the SQL-Server.Ĭan you tell me what we can do on SQL-Server or in VBA - Excel, so that Mac Users can refresh their data from SQL-Server without having to define permissions additionally? Now with office 2019, at least VBA seems to be (almost) the same, so it would be nice, if they could start the procedure directly from Excel on mac. 'OLEDB Provider=SQLOLEDB.1 Integrated Security=SSPI Persist Security Info=True Initial Catalog=ASAP_be Data Source=SERVERNAME Use Procedure for Prepare=1 Auto Translate=True Packet Size=4096 Workstation ID=M99999 Use Encryption for Data=False Tag with column collation when possible=False' Trusted_Connection=yes')īut for mac users, they have (had?) to logon to a citrix client and then start the Workbook, which runs on a windows users.Provider=SQLOLEDB Data Source=SERVERNAME Initial Catalog=ASAP_be.We have different user groups defined, which we also use to access network shares, where specific users are entered, and this users are given specific permissions on the serves via a database role. If they work on a Windows netbook, they logon on their computer to our company domain when they start up, such identifying themselves (windows authentification?).

(Please forgive me if I am using the wrong terms in the next few lines, I am neither IT nor native speaker): We have a financial reporting tool, which gets data from SQL server via stored procedure and works fine on Windows computers.

Mac os excel vba