Changing local clock affects remote SQL Server database functionality

I'm having an issue with some SQL Server 2008 queries and I think I got it down to differences between the server and the local application. Here's a basic description of my scenario:

I'm using a local application that performs insert statements on a remote database. Everything works fine until I change the clock on the local machine that runs the application (let's say a couple days in the future), since the data doesn't really get inserted on the remote database (or at least, I can't see it).

My question is, to what extent is SQL Server functionality affected by this kind of changes? In my example, do the inse开发者_运维问答rtions not get completed due to integrity matters?

One thing that is affected for sure by time difference is NTLM/Kerberos handshake, as well as SSL, all of which tolerate usually 30 minutes time drift between participants. If you change your clock days forward, you won't be able to successfully open a connection with SQL Server in most cases. I must assume your application is also likely swallowing the connect error silently.

It sounds like the local application is affected. It's not SQL Server. SQL Server would certainly only be using the time on the remote machine.